HP Insight Control Server Provisioning 7.2 Online Help

NOTE: The scripts provided by Insight Control server provisioning are read only, so you may
not edit those scripts. Instead, save the script to a new name by selecting Actions→Save as from
the script Overview screen and then edit that copy.
• Table 33 (page 68)
• Table 34 (page 68)
• Table 35 (page 68)
6.8.1 Information displayed on the Overview screen for scripts
Table 33 General information
The types of scripts supported by Insight Control server provisioning are:Type
• UNIX – Bourne shell (sh), C shell (csh), and KornShell (ksh)
• OGFS – Opsware Global File System
• Windows .BAT – Windows batch file
• Windows VBScript – Visual Basic scripting
• Python – Python programming language
The version number of the script. Scripts supplied by Insight Control server provisioning have
version 1. The script version increments automatically when a script is edited and saved.
Revision
The date and time the script was last changed.Last modified
Indicates whether the script runs with superuser access when executed.Run as superuser
If Yes, this script was created by HP and is read only.HP-provided
Table 34 History
The version number of the script. Scripts supplied by Insight Control server provisioning have
version 1. The script version increments automatically when a script is edited and saved.
Revision
The date and time the script was modified.Date
Table 35 Script
A short, meaningful description of what this script does.Description
The listing of the script code.Source code
6.9 Running scripts
Scripts are run as a step in an OS Build Plan. An OS Build Plan running on a server is called a
job.
To run a script it must first be in the scope of Insight Control server provisioning, where it will
appear in the master pane list of scripts on any Scripts screen.
Defining scripts
• You may use a script that IC server provisioning provides, as-is.
• Existing scripts can be leveraged as described in “Create a new script” (page 31).
Running scripts
To run a script you must add it as a step in an OS Build Plan. Once you've added the script to an
OS Build Plan, you can set script parameters on the OS Build Plan Edit screen.
• Edit an existing Build Plan to add your script as described in “Editing OS Build Plans”
(page 54).
68 Scripts