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

11
OS Build Plan Steps
Build plans are made up of a series of build plan steps that execute in order to perform the actions. Four types of steps
are available: Run Script, Deploy Package, Deploy Configuration File, and Capture Configuration File.
Run Script
The run script step is the key component of the product, and represents the vast majority of steps used in build plans.
This step type causes a script to be executed, either on the target server or on the appliance. IC server provisioning
comes with an extensive library of scripts that perform many of the most common tasks you will need when creating
build plans. In addition, you can create your own scripts based on the ones HP provides or entirely from scratch.
IC server provisioning supports the following script types:
OGFS
OGFS scripts control the HP Server Automation engine that is inside the IC server provisioning appliance. These are the
only scripts that execute on the appliance. All other script types run on the target server. Most of the OGFS scripts
shipped with the appliance come from Server Automation, are written in Python, and are not meant to be modified in any
way. They provide vital functions like booting target servers, monitoring tasks, and manipulating data. HP does not
recommend creating OGFS scripts unless you have advanced knowledge of Server Automation.
Python
Python scripts execute on the target server. This is the only script type that can be run on either Windows or Linux
systems.
Unix
These are standard Unix/Linux shell scripts that execute on the target server.
Windows BAT
These are standard Windows batch scripts that execute on the target server.
Windows VBScript
These are standard Windows Visual Basic scripts that execute on the target server.
Powershell
IC server provisioning does not currently support PowerShell as a script type. However, a Windows batch script can be
created
 that dynamically generates the PowerShell script and then runs the script on the target server,
 pipes the PowerShell content into the PowerShell interpreter to run it,
 or copies a PowerShell script from the Media Server to the target server and then runs it.
Deploy Package
In IC server provisioning, packages are zip files stored on the appliance. When the deploy package step is used, the zip
file is transferred to the target server and uncompressed into the specified location. Pre-installation and post-
installation scripts may also be specified with the package that will execute before or after the package is saved to the
target server and the files extracted. All the packages on your appliance are provided by HP. They are typically things
like driver bundles and software libraries needed for installing on ProLiant servers. At this time, there is no option to
allow you to upload your own packages or save and modify copies on the appliance, although that functionality is
planned for a future IC server provisioning release. A package or file may be stored on the Media Server and uploaded to
a target server using simple build plan steps. The HP Insight Control server provisioning Adding Drivers to OS Build Plans
technical white paper uses this method to add drivers to an OS deployment build plan.
Deploy Configuration File
Configuration files are text files stored on the appliance that are used for text-based data such as unattended
installation files or hardware configuration files. The deploy configuration file step takes the specified configuration file
and writes it to a user-specified location on the target server. These steps are often followed by a run script step that
makes use of the configuration file. HP provides many sample configurations. You can use these or create your own.