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‑6. Custom Properties for Linked Clone Blueprints (Continued)
Custom Property Description
VirtualMachine.DiskN.Size
Denes the size in GB of disk N. For example, to give a size
of 150 GB to a disk G, dene the custom property
VirtualMachine.Disk0.Size and enter a value of 150.
Disk numbering must be sequential. By default a machine
has one disk referred to by VirtualMachine.Disk0.Size,
where size is specied by the storage value on the
blueprint from which the machine is provisioned. The
storage value on the blueprint user interface overwrites the
value in the VirtualMachine.Disk0.Size property. The
VirtualMachine.Disk0.Size property is not available as
a custom property because of its relationship with the
storage option on the blueprint. More disks can be added
by specifying VirtualMachine.Disk1.Size,
VirtualMachine.Disk2.Size and so on.
VirtualMachine.Admin.TotalDiskUsage always
represents the total of the .DiskN.Size properties plus the
VMware.Memory.Reservation size allocation.
VirtualMachine.DiskN.Label
Species the label for a machine’s disk N. The disk label
maximum is 32 characters. Disk numbering must be
sequential. When used with a guest agent, species the
label of a machine's disk N inside the guest operating
system.
VirtualMachine.DiskN.Letter
Species the drive leer or mount point of a machine’s disk
N. The default is C. For example, to specify the leer D for
Disk 1, dene the custom property as
VirtualMachine.Disk1.Letter and enter the value D.
Disk numbering must be sequential. When used in
conjunction with a guest agent, this value species the
drive leer or mount point under which an additional disk
N is mounted by the guest agent in the guest operating
system.
MaximumProvisionedMachines
Species the maximum number of linked clones for one
machine snapshot. The default is unlimited.
Linux.ExternalScript.Name
Species the name of an optional customization script, for
example config.sh, that the Linux guest agent runs after
the operating system is installed. This property is available
for Linux machines cloned from templates on which the
Linux agent is installed.
If you specify an external script, you must also dene its
location by using the
Linux.ExternalScript.LocationType and
Linux.ExternalScript.Path properties.
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.
You must also specify the script location using the
Linux.ExternalScript.Path property. If the location
type is nfs, also use the Linux.ExternalScript.Server
property.
Custom Properties Reference
22 VMware, Inc.