Installing a Custom Operating System with HP Insight Control for Linux

9
The second message is usually sent from the post-script section of the installation configuration file
to let Insight Control for Linux know that the OS was successfully installed and that the task is
complete. For example, your installation configuration file must contain a macro similar to the one
shown below in the post-script section.
%post
%%completion%%
Your auto_config script substitutes the variables contained in the GUID.vars file for the
%%completion%% macro; that macro is shown here:
completion_macro() {
FILE=$1
cmd="wget -O /dev/null
http://${cms_http_ip}:${cms_http_port}/taskservice/autoInstallComplete.js
p\\\\\\?N=${guid}\\\\\\&K=${security_key}"
/bin/sed -i 's!%%completion%%!'"${cmd}"'!g' ${FILE}
}
After the auto_config script runs, the post-script section of your installation configuration file might
resemble the following:
%post
wget -O /dev/null
http://172.0.0.100:60000/taskservice/autoInstallComplete.jsp\?N=000000265
51f557c0000000300000002\&K=423037
Your auto_config script must echo the resulting installation configuration file (after the macros
have been substituted with actual values) to StdOut where Insight Control for Linux captures it.
Insight Control for Linux provides an example auto_config script for CentOS and Debian under the
/opt/repository/instconfig/custom/examples/ directory:
For CentOS5, the file is CentOS5/auto_config
For Debian5, the file is Debian5/auto_config
Use the example
auto_config script as a model for creating your own.
The full path name of this script must be
/opt/repository/instconfig/custom/MyOS/auto_config
Where MyOS is the value you specified in the Name field when you registered your custom OS.
Make sure that the root user has execute permission for the auto_config script.
Constructing the boot stanza for the boot loader
The boot_stanza script constructs a boot stanza that specifies your kernel and RAM disk, which
allows your boot loader to boot your custom OS.
Whether or not you need this script depends on how you want to install the custom OS:
If you are performing an interactive custom OS installation using virtual media, you must create a
boot_stanza script, because you need to specify the target server’s static IP address information
in the kernel parameters.
If you are performing an interactive custom OS installation using PXE, you do not need this script
but, if it exists, it will be run.