HP Insight Control for Linux 6.2 User Guide

3. Copy the contents of each installation disk into its own directory. For example, copy the
contents of the first CD into the CD1 directory, and so on.
4. 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.
On the SLES media, the kernel and RAM disk files are located in an architecture-specific
subdirectory named boot/i386/loader or boot/x86_64/loader on the first SLES
installation disc.
5.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 56).
• 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.
5.3.5 Copying a custom OS into the repository
The Insight Control for Linux installation tools enable the installation of almost any OS that
supports either the PXE boot protocol or virtual media and provides kernel and RAM disk files
that contain the drivers for 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 custom OS registration process supplied to you.
5.3.6 Automating a custom OS installation
HP recognizes that different versions of Linux have different installation configuration files (for
example RHEL distributions have Kickstart files while SLES distributions have AutoYaST files)
and that different Linux distributions accept different kernel parameters in the boot loader
configuration file. You can now control this content by using special scripts; Insight Control for
Linux calls these scripts at various points when your custom OS installation runs. You can find
example scripts for CentOS and Debian installations under the /opt/repository/
instconfig/custom/examples directory.
NOTE:
If you want to perform an automated custom OS installation (for a custom OS that was registered
with the repository in a version of Insight Control for Linux before V6.0), you must create the
/opt/repository/instconfig/custom/OS_Name directory manually.
Insight Control for Linux automatically creates this directory when a custom OS is registered
with the repository. However, in versions of Insight Control for Linux before V6.0, automated
custom OS installations were not supported; that directory would not exist.
For full information on custom OS installations using Insight Control for Linux, see the white
paper titled Installing a Custom Operating System with HP Insight Control for Linux.
5.3 Copying software to the Insight Control for Linux repository 59