Installing a Custom Operating System with HP Insight Control for Linux

7
Variable Name
Description
os
The OS name you specified when you registered the custom OS with the
repository.
For example, CentOS5.4-x64
password_encrypted
This value is true if you chose to encrypt the root password when you
performed an unattended custom OS installation.
Otherwise it is set to false.
path_via_http
Path to the OS distribution when using HTTP.
For example, /custom/CentOS5.4-x64
ramdisk
The RAM disk you specified when you registered the custom OS with the
repository.
root_password
The root password you specified when you performed an unattended
custom OS installation.
security_key
A randomly-generated security key used when sending a message to the
CMS to ensure that the message is valid.
template_file
A copy of the installation configuration file you registered with the
repository (see Registering your installation configuration file).
For example,
/opt/repository/instconfig/custom/tmp/GUID.template
Use this file to perform macro substitutions; it is created every time you
perform an unattended custom OS installation.
tmp_dir
The directory that Insight Control for Linux uses to store temporary files
that your scripts will need to perform the unattended installation.
Its value is /opt/repository/instconfig/custom/tmp.
unattended_install
This value is true when you run the Deploy→Operating
System→Custom OS or Other (Unattended) task
It is false when you run the Deploy→Operating
System→Custom OS or Other (Interactive) task.
Using auto_config to prepare the installation configuration
file
The auto_config script is required for unattended OS installations. It runs during the Configure
Unattended Installation File operation of the Deploy→Operating System→Custom OS or
Other (Unattended) task. Insight Control for Linux uses this script to create the final installation
configuration file, with actual values substituted for the macros.
Insight Control for Linux passes the GUID.vars file name as an argument when Insight Control for
Linux starts the auto_config script. The auto_config script must then source in the GUID.vars
file to access to the variables contained in the file. For an example of a bash script that sources the
GUID.vars file, see
Sourcing in the GUID.vars file.