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

27
--maintenance --atLeast=3 --atMost=20
5
LinuxPE add-on packages
Deploy package
6
ProLiant Scripting Toolkit for Linux x64
Deploy package
7
System ROM Configuration – Enable Boot from SAN
Deploy configuration file
/tmp/sstk/conrep-bfs.xml
8
Manage System Configuration
Unix
-l /tmp/sstk/conrep-bfs.xml
9
Boot
OGFS
--servicesOS=linux64 --force
10
Wait for HP SA Agent
OGFS
--maintenance --atLeast=3 --atMost=20
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 4 – Boot the server for provisioning
The next steps are used to boot the server into the required service OS. Once these steps are done, the server is in
maintenance ready to start performing tasks. Refer to Table 1 – ProLiant OS – Windows 2012 Standard x64 Scripted
Install sample and the detailed description in the Steps 3 to 5 – Boot the server for provisioning section. For the
hardware build plans, the desired service OS Boot step parameter is linux64.
Note that this build plan does not have the Decommission server step. That is because you might choose to use this
build plan on a server in production and would not want to decommission it. However, if you use this build plan as the
first part of a combo build plan, you will want to insert the decommission step between steps 3 and 4.
Steps 5 to 8 – Apply the hardware configuration
These steps perform all the work of setting up for and configuring the target server environment, by landing appropriate
ProLiant Scripting Toolkit files and libraries and configuration file and running the tool to apply the configuration.
 LinuxPE add-on packages – This is a zip file containing additional libraries and utilities required in the LinuxPE
PXE service OS.
 ProLiant Scripting Toolkit for Linux x64 – This is a zip file containing the ProLiant Scripting Toolkit utilities.
 System ROM Configuration – Enable Boot from SAN – This is a deploy configuration file step. It writes the HP-
provided hardware configuration file to the target server’s ram drive. The configuration file format aligns with
the ProLiant Scripting Toolkit utility requirements. 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.
 Manage System Configuration – This step actually runs the appropriate ProLiant Scripting Toolkit utility using
the configuration file as a parameter.
Steps 9 to 10 – Perform the post configuration tasks
These final steps perform the final reboot of the target server to apply the new configuration.
 Boot – Reboots the target server back into the service OS to force the ProLiant Scripting Toolkit utility changes
to be available at next reboot.
 Wait for HP SA Agent – This is the same step as before, waiting for the reboot to complete and the system to
boot back into maintenance. The parameters for these two steps could be modified to boot the server back
into production mode, if that is preferred.