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

37
This is a sample build plan that can be modified to set any System ROM settings on any ProLiant server. Just replace the
configuration file with one that specifies the settings you want and that is appropriate for that particular server.
In this particular case, boot from SAN is enabled by setting the fibre channel first in the boot order and disabling any
embedded storage controller.
Requirements: HP ProLiant BladeSystem with iLO and fibre channel controller
Custom Attributes: None
ProLiant OS - ESXi 5.0 U1 Scripted Install
ProLiant OS - ESXi 5.0 U2 Scripted Install
ProLiant OS - ESXi 5.0 U3 Scripted Install
ProLiant OS - ESXi 5.1 Scripted Install
ProLiant OS - ESXi 5.1 U1 Scripted Install
ProLiant OS - ESXi 5.1 U2 Scripted Install
ProLiant OS - ESXi 5.5 Scripted Install
Performs a scripted install of the selected VMware ESXi version using a generic kickstart file.
NOTE: For ESXi 5.1 and later, ESXi naming has changed to vSphere; however, OSBPs, scripts and configuration files may
continue to state ESXi.
Requirements:
 HP ProLiant server with iLO
 IC server provisioning Media Server must contain the OS distribution
Optional Custom Attributes:
 ProductKey_ESXiZZ corresponding to the selected version of ESXi where ZZ is the version number
 encrypted_root_password – root password in encrypted form. Refer to the HP Insight Control Server
Provisioning online help on how to create an encrypted password.
 boot_disk – disk on which vSphere is installed, for example sda, hdc, cciss/c0d1
 kernel_arguments – additional kernel arguments for the installed vSphere kernel
ProLiant OS - RHEL 5.9 x64 Scripted Install
ProLiant OS - RHEL 5.10 x64 Scripted Install
ProLiant OS - RHEL 6.3 x64 Scripted Install
ProLiant OS - RHEL 6.4 x64 Scripted Install
ProLiant OS - RHEL 6.4 x64 KVM Scripted Install
ProLiant OS - RHEL 6.5 x64 Scripted Install
ProLiant OS - RHEL 6.5 x64 KVM Scripted Install
Performs a scripted install of the selected Red Hat Enterprise Linux version using a generic kickstart file.
The KVM scripted install build plan installs a RHEL6.x x64 Kernel Virtual Machine (KVM) hypervisor on a target server,
known as the KVM host. Once the KVM hypervisor is installed, libvirt utilities such as virsh or virt-manager may be used
to add KVM guests on the KVM host.
Additionally, virtualization must be enabled in the BIOS. Virtualization is enabled by default; however, If it has been
disabled on the target server, it can be enabled in the RBSU under the System Options -> Processor Options menu, or
create a build plan using the ProLiant HW - System ROM Enable Boot from SAN on Bladeserver build plan, replacing the
configuration file with the System ROM Configuration – Enable Virtualization configuration file.
Requirements:
 HP ProLiant server with iLO
 IC server provisioning Media Server must contain the OS distribution
Optional Custom Attributes: