HP Insight Control for Linux 6.0 User Guide

IMPORTANT:
• HP recommends copying and using the default files as templates to create customized
installation configuration files that are suitable for your environment.
Familiarize yourself with the contents and usage comments in the configuration file templates,
and use them to make versions that are appropriate for your own environment.
• Some default templates specify port 60000, the default web server repository port number,
by that number. If you use a repository web server port that is different from that default
value, ensure that any Kickstart or AutoYaST installation configuration file you create from
these templates has the correct port number for the repository web server port for your
environment.
• Be aware that the default installation configuration files provided for RHEL and SLES
installations are configured such that all existing partitions on all disks of a managed server
are erased. If this is not acceptable behavior, remember to change this behavior when you
create your customized file.
• The default Kickstart and AutoYaST files automatically extract and install the RPMs listed
in Table 9-1 (page 105) from the associated PSP.
• The SLES 10 SP3 virtual host AutoYaST configuration file that Insight Control for Linux
provides is valid only for the x86_64 processor architecture; it includes the kernel-xen
package. For the i386 processor architecture, this must be replaced with the kernel-xenpae
package.
Kickstart and AutoYaST installation configuration files that are read during an unattended OS
installation operation must be located in the Insight Control for Linux repository in the /opt/
repository/instconfig directory and should use the naming conventions described in
Section 7.2.1.
7.2.1 Naming conventions for installation configuration files
The default installation configuration files and their associated directories under /opt/
repository/instconfig follow these naming conventions:
• The files are stored in OS- and version-specific directories that use the following naming
convention:
{abbreviated_os_type}{version}{update_or_servicepack}[-{special}].
The following table provides a few examples:
Directory name in /opt/repository/instconfig
OS version
sl103
SLES Version 10 Service Pack 3
sl102–management-hub
SLES Version 10 Service Pack 2 (for
Management Hubs)
sl102–virt-host
SLES Version 10 Service Pack 2 (for Virtual
Hosts)
sl102–virt-guest
SLES Version 10 Service Pack 2 (for Virtual
Guests)
rh047
RHEL Version 4 Update 7
rh051
RHEL Version 5 Update 1
rh052–management-hub
RHEL Version 5 Update 2 (for Management
Hubs)
rh052–virt-host
RHEL Version 5 Update 2 for Virtual Hosts)
7.2 Using Kickstart or AutoYaST files for unattended installations 83