HP Insight Control for Linux 6.0 User Guide

# printf "/SLES9/CD1\t/SLES9/CD1\n" >> yast/order
# printf "/CORE9/CD1\t/CORE9/CD1\n" >> yast/order
6. Copy the kernel and RAM disk boot files to the related boot target directory. The kernel file
name is linux and the RAM disk file name is initrd.
# cp SVRP3/CD1/boot/loader/linux /opt/repository/boot/SLES-9-SP3-i386Boot/
# cp SVRP3/CD1/boot/loader/initrd /opt/repository/boot/SLES-9-SP3-i386Boot/
7. SLES Version 9 does not support specifying an installation interface by its MAC address,
something that Insight Control for Linux needs to perform an automated installation. To
work around this issue, HP provided an additional boot target that runs with the standard
SLES Version 9 initrd RAM disk file to provide this functionality.
However, this additional boot target must be in a cpio format. Enter the following commands
in the boot target directory to put the appropriately formatted files in the boot directory:
# cp /opt/repository/boot/sles9fix/hp-xdevice-cpio-gz /opt/repository/boot/SLES-9-SP3-i386Boot/
# cd /opt/repository/boot/SLES-9-SP3-i396Boot
# find initrd | cpio -o -H newc | gzip > initrd-cpio-gz
6.3.4 Copying virtual machine OS into the repository
The procedure for copying virtual machine OS into the repository depends on the virtual machine
software:
• For VMware ESX, the process is identical to copying a RHEL operating system to the
repository. For more information, see “Copying software to the Insight Control for Linux
repository” (page 69).
• For VMware ESXi, copy the contents of the media to the
/opt/repository/boot/vm_nameBoot directory, where vm_name is the name of the
directory for the VMware ESXi virtual machine OS.For example, for ESXi version 4.0, the
directory would be /opt/repository/boot/ESXi4.0Boot.
Data for VMware ESXi is not transferred through HTTP; instead, it is loaded from the
/opt/repository/boot/vm_nameBoot directory using PXE or virtual media.
• For Xen, no additional action is required because the RHEL or SLES distribution accounts
for it.
6.3.5 Copying a custom OS into the repository
The HP Insight Control for Linux installation tools enable the installation of almost any OS that
supports the PXE boot protocol and provides kernel and RAM disk files that contain the drivers
appropriate to the target managed system installed.
Similar to the process for copying the vendor-supplied installation files for a supported OS, you
copy the installation sources to the Path on disk and copy the kernel and RAM disk files to the
Boot target path on disk that were supplied to you by the custom OS registration process.
6.3.6 Automating a custom OS installation
You can create your own automated installation script (for example, a Kickstart or AutoYaST file)
to facilitate an unattended installation. The use of the automated installation script is optional;
if it is not present for the OS you are installing, the installation proceeds as an interactive
installation.
The custom file must be named as follows:
/opt/repository/instconfig/custom/OS_Name/install_config
Where OS_Name is the name of the custom OS.
When you perform a custom OS installation, Insight Control for Linux creates a file named
/opt/repository/instconfig/custom/OS_Name/GUID.vars, where GUID is the globally
6.3 Copying software to the Insight Control for Linux repository 77