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

26
 ESXi 5.1 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 ESXi 5 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 for ESXi 5 – 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 there causes a
server-level custom attribute named, hpsa_netconfig, to be created and assigned to each server being
provisioned. The Inject Kickstart Personalization Settings for ESXi 5 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 ESXi 5 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.
 ESXi Installation Utilities - A package containing the boot loader and Master Boot Record needed to boot ESXi.
 Deploy Agent - Refer to Table 4 – ProLiant OS – RHEL 6.3 x64 Scripted Install build plan sample and the
detailed description in the Steps 6 to 16 – Stage the installation section.
 Add ESXi Module – Places the file or directory specified as an argument to the “-s” into a compressed tar file so
that it can be loaded as an ESXi module when ESXi is booted. The file or directory will be visible in the file
system when ESXi boots.
 Install bootloader for ESXi – Installs the grub bootloader onto the stub partition in order to enable booting the
ESXi installation image. It takes the kernel_arguments optional custom attribute as a parameter to allow for
additional kernel arguments to the installation kernel.
Steps 18 and 19 – Perform the installation and post-install tasks
These final steps actually perform the OS installation, add the production agent, and perform the final reboot of the
server.
 Reboot – Reboots the target server which on next boot will boot the ESXi 5.1 grub image and begin the ESXi
installation.
 Wait for ESXi Installation – Since there is no SA agent support for ESXi operating system, there is no Wait for
HP SA Agent step here. Instead, this special step is used, and detects when the ESXi installation is complete.
Sample Build Plan: ProLiant Hardware Configuration
Table 6 – ProLiant HW – System ROM Enable Boot from SAN on Bladeserver build plan sample
Step
Number
Step Name
Step Type
Step Parameters
1
Check iLO Service
OGFS
2
Verify Supported Boot Modes
OGFS
--secure=disabled
3
Boot
OGFS
--serviceOS=linux64
4
Wait for HP SA Agent
OGFS