7.3
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Updated Information
- Custom Properties and the Property Dictionary
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for 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 and Property Groups for Containers
- 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 (_)
- Custom Properties A
- Custom Properties B
- Custom Properties C
- Custom Properties E
- Custom Properties H
- Custom Properties I
- Custom Properties L
- Custom Properties M
- Custom Properties N
- Custom Properties O
- Custom Properties P
- Custom Properties R
- Custom Properties S
- Custom Properties V
- Custom Properties X
- Using the Property Dictionary
- Using Property Definitions
- Using Property Groups
- Defining Component Profile Settings
Network assignments are performed during machine allocation. vRealize Automation retrieves network
information from the blueprint. If you want to assign more than one network, use the
VirtualMachine.NetworkN.Name custom property on your machine blueprint. If you do not provide
custom properties, allocation only assigns one network which is picked using a round robin method in
conjunction with the selected reservation.
Note With the exception of the following properties, the properties in the table do not apply to Amazon
Web Services:
n
agent.download.url
n
software.agent.service.url
n
software.ebs.url
For machine components that do not have a Network or Security tab, you can add network and security
custom properties, such as VirtualMachine.Network0.Name, to their Properties tab in the design
canvas. NSX network, security, and load balancer properties are only applicable to vSphere machines.
Note Network-specific custom properties that point to on-demand networks are not supported. For
example, you cannot use network custom properties, such as
VirtualMachine.Network0.NetworkProfileName, for on-demand NAT and on-demand routed network
components.
By default, a machine has one network device configured with the VirtualMachine.Network0.Name
property. You can configure additional network devices by using the VirtualMachine.NetworkN.Name
custom property, where N is the network number.
The numbering of network properties must be sequential, starting with 0. For example, if you specify
custom properties for only VirtualMachine.Network0 and VirtualMachine.Network2, the properties
for VirtualMachine.Network2 are ignored, because the preceding network,
VirtualMachine.Network1, was not specified.
Although general support for vCloud Networking and Security 5.5.x (vCNS) has ended, the VCNS custom
properties continue to be valid for NSX purposes. See the VMware Knowledge Base article End of
Availability and End of General Support for VMware vCloud Networking and Security 5.5.x (2144733) at
http://kb.vmware.com/kb/2144733 for more information.
Custom Properties Reference
VMware, Inc. 38