The links below provide detailed information on best practices for OS Build Plans.
HP supplies Build Plans with the Insight Control server provisioning product. These Build Plans work out of the box but were designed to be easily used as templates. See the Insight Control Server Provisioning Build Plans Reference Guide for details about all of the HP-provided Build Plans.
Build Plans supplied by Insight Control server provisioning are read only and may not be edited, but you can save a copy to work from. See Copy (Save as) HP-provided Build Plans to allow modifications for information.
|
|
|
![[NOTE: ]](images/note.gif) |
NOTE: With ESXi 5.1 and later, the ESXi name changed to vSphere, however IC server provisioning OS Build Plans, scripts and configuration files may continue to state ESXi. |
|
|
Good names are important for understanding what a Build Plan does and for helping you find the Build Plan you are looking for. HP uses the following naming convention for the Build Plans supplied with Insight Control server provisioning.
|
|
|
|
|
NOTE: The driver packages shipped from 7.2/7.2.1 do not conform to this new driver package naming convention and these driver packages are based on SPP 2013.02. |
|
|
The table below shows how to use HP's naming convention for Build Plans.
ProLiant<Job code>–<OS & version or Job type><Action><Modifiers>
| Description | Examples | Notes | ||||||
|---|---|---|---|---|---|---|---|---|
| “ProLiant” | All Build Plans will work on HP ProLiant servers; all Insight Control server provisioning Build Pans begin with the text “ProLiant”. | |||||||
| Job code | Designation that keeps job types together when sorting. |
|
||||||
| OS & version |
The operating system to be deployed, with major and minor version numbers, plus architecture. |
|
Specifying an OS implies an OS installation type of Build Plan. The OS edition such as “Enterprise” and “Basic” is not included. |
|||||
|
||||||||
| Job type | What this Build Plan does if it does not deploy an operating system. |
|
||||||
| Action | The action performed by this Build Plan, preceded by a modifier where applicable. |
|
||||||
| Modifiers | Anything else that might assist in describing this Build Plan. |
|
||||||
For example HP-provided Build Plan names seeList of HP-provided Build Plans
The following is a sample list of HP-provided Build Plans, check the IC server provisioning OS Build Plans view for a complete list. See the Insight Control Server Provisioning Build Plans Reference Guide for details about all of the HP-provided Build Plans.
Sample list of HP-provided Build Plans:
-
ProLiant OS - Windows 2008 R2 SP1 Standard x64 Scripted Install
-
ProLiant OS - Windows 2008 R2 SP1 Standard x64 Image Capture
-
ProLiant OS - Windows 2008 R2 SP1 Standard x64 Image Install
-
ProLiant OS - Windows 2008 SP2 Standard x64 Scripted Install
-
ProLiant HW - System ROM Enable Boot from SAN on Bladeserver
|
|
|
|
|
NOTE: With ESXi 5.1 and later, the ESXi name changed to vSphere, however IC server provisioning OS Build Plans, scripts and configuration files may continue to state ESXi. |
|
|
HP designs its firmware, drivers, and agents to work together at specific revision levels. The HP-Supplied Build plans always reference the latest versions; see the HP Insight Management Support Matrix at http://www.hp.com/go/insightmanagement/docs for details. For best results, you should keep your system firmware at this same revision. Failure to do so might cause deployment problems. See Deploy a Support Pack for ProLiant (SPP) for instructions.
|
|
|
|
|
NOTE: Build plans for Insight Control server provisioning version 7.2.2 and later will use the following format for Windows, RHEL and SLES: “ProLiant Drivers for <OS><SPP>”. This convention will permit maintenance of multiple versions of driver packages on the same appliance. Note that after an upgrade, all HP provided Build Plans will always use the latest version of the driver package and customized Build Plans will continue to point to older versions of the driver package. If a customized Build Plan needs to be updated to point to the latest version of a driver packages, see Change the version of drivers used in a Build Plan for instructions. |
|
|
Installing VMware ESXi to target servers requires HP-supplied VMware ESXi distribution files that include the appropriate ProLiant drivers and certain firmware recipes. For information, see http://vibsdepot.hp.com/hpq/recipes/. You might need to update firmware on the target server to a minimum version in order to deploy VMware ESXi to a target server.