HP Insight Control Server Provisioning 7.3 Update 1 Build Plans Reference Guide

23
--production --atLeast=3 --atMost=30
Steps 1 and 2 – Early error detection
The first two steps help catch errors that might affect the running of the build plan later on. Refer to Table 1 – ProLiant
OS – Windows 2012 Standard x64 Scripted Install build plan sample and the detailed description in the Steps 1 to 3 –
Early error detection section.
Steps 3 to 5 – Boot the server for provisioning
The next set of steps are used to boot the server into the required service OS and reset the status of the server such that
it can be provisioned. Once these steps are done, the server is in maintenance ready to start the provisioning process.
Refer to Table 1 – ProLiant OS – Windows 2012 Standard x64 Scripted Install sample and the detailed description in the
Steps 4 to 6 – Boot the server for provisioning section. For the Linux build plans, the desired service OS Boot step
parameter is linux64.
Steps 6 to 16 – Stage the installation
These steps perform all the work of setting up for the installation by copying files, putting drivers in place, and
preparing the kickstart file.
 Set Media Source – This is the step that points the build plan to the OS distribution media on the media server.
The parameter for this step is made up of a special custom attribute. This is a hidden custom attribute that
corresponds to the information specified in the Media Server Settings page. At run time, this custom attribute
is substituted and takes this form:
http://media-server-IP/mnt/sharename/media
where /mnt/sharename/media is the mount point and location to the OS distribution media.
 RHEL 6.3 x64 en_us Kickstart – This is a deploy configuration file step. It writes the HP-provided kickstart file to
the target server’s ram drive. It is recommended to replace this step with a customized kickstart file using the
HP-provided configuration files as a template since these template files contain the Custom Attribute syntax.
The path specified by the parameter is where the file is written. Follow on build plan steps expect to find this
file in that location, so it is not recommended that the path be changed.
 Inject Required Kickstart Settings – This is a script that adds required items to the kickstart file to make it work
properly with the appliance. This script is required and always comes right after the step that writes out the
kickstart file.
 Inject Kickstart Personalization Settings – This step is used when static IP addressing information is specified
as part of the installation in the Run OS Build Plan page. Setting network information causes a server-level
custom attribute named, hpsa_netconfig, to be created and assigned to each server being provisioned. The
Inject Kickstart Personalization Settings step checks for the existence of that custom attribute. If it exists, the
network information is read and the unattend file is modified to include the static IP information. This step
should always follow the Inject Required Kickstart Settings step. Note: The hpsa_netconfig custom attribute is
not removed after it is set, so it could be there if another build plan is run against the same target server.
 Create Stub Partition – Creates partition on the local disk to load the Linux build image.
 Copy Boot Media – Copies several files to the stub partition in order to boot the installer environment.
 ProLiant Drivers for RHEL 6.3 x64 – This is a zip file containing the latest ProLiant drivers for this operating
system. They are placed in the directory specified by the parameter, which is where the Linux OS installer is
expecting to find them.
 GRuB Boot Loader x86 – This is a zip file contain the grub boot loader that will land on the stub partition. Even
though the name contains x86, it is still used with x64 Linux deployments.
 Deploy Agent - Copies the zip file containing the agent to the target server. This agent is used to communicate
with the target server during the operating system installation and is not the same agent that is placed on the
production server.
 Embed files initrd – Adds additional files to the new initrd image landed during the GRuB Boot Loader x86 step.
 Install bootloader for RedHat Enterprise Linux Server – Installs the grub bootloader onto the stub partition in
order to enable booting the Red Hat Enterprise Linux Server installation image. It takes the kernel_arguments
optional custom attribute as a parameter to allow for additional kernel arguments to the installation kernel.