Scripts are used to accomplish provisioning tasks in IC server provisioning. To run a script, add it as a step in an OS Build Plan. Multiple scripts can be run as a series of steps within a Build Plan.
IC server provisioning supports a variety of script types, some of which run on target servers and some that run on the appliance.
IC server provisioning includes HP-provided scripts that run with the HP-provided Build Plans. You may also create your own scripts to meet the needs of your facility.
The types of scripts supported by Insight Control server provisioning included the following:
-
UNIX—Bourne shell (sh), C shell (csh), and KornShell (ksh)
-
Windows .BAT—Windows batch file
-
Windows VBScript—Visual Basic scripting
-
Python—Python programming language
-
OGFS—Opsware Global File System (used to control the embedded Server Automation instance)
|
|
|
![[NOTE: ]](images/note.gif) |
NOTE: OGFS scripts execute on the appliance; all other script types execute on target servers. |
|
|
HP provides scripts with IC server provisioning. These scripts are read-only and are identified by the HP-provided field set to Yes on the Scripts screen General panel. In most cases it is not necessary to modify the scripts provided by HP because most customization is done via the OS Build Plans and configuration files. For additional information, see Create scripts.
|
|
|
|
|
NOTE: The library of HP-provided scripts includes some HP Server Automation scripts that are part of its larger library and are not supported by Insight Control server provisioning. The HP-provided scripts used in HP-provided Build Plans or scripts referenced in documentation are supported. For a list, see the HP Insight Control Server Provisioning Build Plans Reference Guide, at http://www.hp.com/go/insightcontrol/docs. |
|
|
To run a script, you must add it to an OS Build Plan as a step. Once you have added the script to an OS Build Plan, you can set parameters on the OS Build Plan Edit screen. See Run scripts.