7 downloading and copying psps into the repository – HP Insight Control Software for Linux User Manual
Page 78
unique identifier for the server you are installing the OS on. This file contains a list of variables
in name=value format.
The following is an example of the file contents:
hostname="host_name"
mac="MAC_address"
ip="IP_address"
netmask="255.255.240.0"
gateway="gateway_IP_address"
nameservers="name_servers_IP_addresses"
domains="domain_names"
boot_method=pxe
kernel="vmlinuz"
ramdisk="/CentOS5Boot/initrd.img"
guid="GUID_value"
cms_http_ip="IP_address_of_CMS"
cms_http_port="60000"
os="CentOS5"
distro_url="http://IP_address_of_CMS:60000/custom/CentOS5"
config_url="http://IP_address_of_CMS:60000/instconfig/GUID_value"
config_file="/opt/repository/instconfig/GUID_value"
kernel_params_file="/opt/repository/instconfig/custom/CentOS5/GUID_value.kp"
Your /opt/repository/instconfig/custom/OS_Name/install_config script will be
called and passed the name of the
/opt/repository/instconfig/custom/OS_Name/GUID.vars
file as its first argument.
Your script can then read in the file to gain access to the variables within the file. Your script
must actually create the automated installation file for your Custom OS using the variables
provided in the GUID.vars file. Your install_config script must create the automated
installation file with the name /opt/repository/instconfig/GUID The server’s GUID can
be found in the guid variable contained within the GUID.vars file, along with other useful
variables.
HP provides a sample script named /opt/repository/instconfig/custom/
install_config.sample
that creates a CentOS Kickstart file. You can use this file as a template
for your own automated installation script. Remember to:
•
Rename the copy as
/opt/repository/instconfig/custom/OS_Name/install_config
.
•
Change this file's permissions to make it executable.
You can also specify kernel parameters in your automated installation configuration script. These
kernel parameters indicate where the kernel will locate the automated installation configuration
script you created. Kernel parameters must be written to a separate file named
/opt/repository/instconfig/custom/OS_Name/GUID.kp
.
Refer to the install_config.sample file for an example on how to create the automated
installation configuration script as well as to understand the necessary kernel parameters. Keep
in mind that the sample file is for a CentOS Operating System and the format of your auto
installation file and the kernel parameters may differ for the OS you are installing; you will need
to make the necessary modifications for your specific custom OS.
6.3.7 Downloading and copying PSPs into the repository
To download a PSP to the CMS, follow these steps. The last step in the procedure describes how
to save the PSP to the appropriate location in the Insight Control for Linux repository.
1.
Open a web browser to the ProLiant Support Pack — Overview and Features website:
2.
Select Download software under the Support section.
3.
Select the OS type and version.
78
Managing the Insight Control for Linux repository