7.1
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Updated Information
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for Blueprints and Deployments
- Custom Properties for Naming and Analyzing Deployments
- Custom Properties for Openstack Endpoints
- Custom Properties for Clone Blueprints
- Custom Properties for Linked Clone Blueprints
- Custom Properties for FlexClone Blueprints
- Custom Properties for Basic Workflow Blueprints
- Custom Properties for Linux Kickstart Blueprints
- Custom Properties for SCCM Blueprints
- Custom Properties for WIM Blueprints
- Custom Properties for vCloud Air and vCloud Director Blueprints
- Custom Properties for Networking
- Custom Properties for PXE Provisioning
- Custom Properties for vRealize Automation Guest Agent
- Custom Properties for BMC BladeLogic Configuration Manager Integration
- Custom Properties for HP Server Automation Integration
- Custom Properties Grouped by Name
- Custom Properties Underscore (_) Table
- Custom Properties A Table
- Custom Properties B Table
- Custom Properties C Table
- Custom Properties E Table
- Custom Properties H Table
- Custom Properties I Table
- Custom Properties L Table
- Custom Properties M Table
- Custom Properties O Table
- Custom Properties P Table
- Custom Properties R Table
- Custom Properties S Table
- Custom Properties V Table
- Custom Properties X Table
- Using the Property Dictionary
- Using Property Definitions
- Using Property Groups
- Index
Table 2‑26. Required Custom Properties for HP Server Automation Integration (Continued)
Property Definition
Linux.ExternalScript.LocationType
Species the location type of the customization script
named in the Linux.ExternalScript.Name property.
This can be either local or nfs.
Linux.ExternalScript.Path
Species the local path to the Linux customization script or
the export path to the Linux customization on the NFS
server. The value must begin with a forward slash and not
include the le name, for
example /scripts/linux/config.sh.
Optional Custom Properties for HP Server Automation Integration
Certain custom properties are optional for a blueprint to work with HP Server Automation.
Table 2‑27. Optional Custom Properties for HP Server Automation Integration
Property Definition
Opsware.ProvFail.Notify
(Optional) Species the notication email address for HP
Server Automation to use in the event of provisioning
failure, for example provisionfail@lab.local.
Opsware.ProvFail.Notify
(Optional) Species the HP Server Automation user to
whom ownership is assigned if provisioning fails.
Opsware.ProvSuccess.Notify
(Optional) Species the notication email address for HP
Server Automation to use if provisioning is successful.
Opsware.ProvSuccess.Owner
(Optional) Species the HP Server Automation user to
whom ownership is assigned if provisioning is successful.
Custom Properties That Make HP Server Automation Software Jobs Available
Depending on how your fabric administrator congures HP Server Automation jobs for
vRealize Automation integration, you might have a choice between making all software jobs available to
machine requesters to select, or you can specify jobs to apply to all machines provisioned from your
blueprint.
Table 2‑28. Custom Properties to Make Software Jobs Available
Property Definition
LoadSoftware
Set to True to enable software install options.
Vrm.Software.Id
(Optional) Species an HP Server Automation policy to be
applied to all machines provisioned from the blueprint.
NNNN is a number from 1000 to 1999. The rst property
must start with 1000 and increment in numerical order for
each additional property.
Custom Properties Reference
48 VMware, Inc.