You use the deployment environment tab to retrieve the list of cloud templates and networks available in the deployment environment and map them to logical templates and logical networks. You can also configure custom properties in vCloud Application Director to override the vCloud Automation Center blueprint custom properties, mapping pre-defined disks to storage, or add to the existing properties.

The nodes listed in the VM Templates section correspond to the components of the application, as shown in the application blueprint. If the application includes custom external services that require scripts to run, the VM template is mapped to the temporary virtual machine.

The Networking section lists the logical networks defined in the blueprint. The network you select and map depends on the deployment environment. The deployment profile also contains a network list of vCloud Director and Amazon EC2 networks. For vCloud Director, vCloud Application Director supports external networks and vCloud routed networks with or without DHCP. If the network list is empty, contact your vCloud Director administrator. For Amazon EC2, vCloud Application Director supports the NAT-routed, public, and private networks. NAT-routed and public networks can access the Internet. A private network that is not NAT-routed can access only the vCloud Application Director appliance. To deploy to Amazon EC2, you must carefully determine the virtual machine you put on an external network. Every NIC on an external network gets an Elastic IP address, which puts that interface on the Internet. Put a NIC on an external network only when it is absolutely required.

Note

For vCloud Automation Center, the networking information is not available. vCloud Automation Center uses the network connection specified in the vCenter Server template.

vCloud Automation Center blueprint has custom properties that are defined in the build profiles. These custom properties are applied to a virtual machine when it is created. vCloud Application Director lets you override the vCloud Automation Center blueprint custom properties or add to the existing properties. For example, to override the existing vCloud Automation Center network information you can specify network or static IP addresses in the custom properties for a specific node in the application blueprint. This defined custom property is applied whenever a virtual machine is created.

Custom properties are key-value pairs. You can define these properties as key=value.

Note

Do not use the vCloud Application Director reserved and internal properties as your custom properties. If you use these properties, you receive an error message.

See vCloud Application Director Reserved and Internal Properties.

Verify that your user account has the ROLE_DEPLOYER deployer role assigned to it.

Verify that at least one cloud template is mapped to each logical template used in the blueprint. See Add a Logical Template to the Catalog.

Verify that at least one application is created in vCloud Application Director. See Creating Applications.

Depending on your cloud environment, you must have at least one vCloud Director or Amazon EC2 network available for the deployment environment. See Create a vCloud Director Deployment Environment or Create an Amazon EC2 Deployment Environment.

Note

For vCloud Automation Center, the networking information is not available. vCloud Automation Center uses the network connection specified in the vCenter Server template.

Register your cloud template to a vCloud Application Director cloud provider. See Register the vCloud Director Cloud Provider and Template, Register the vCloud Automation Center Cloud Provider and Template and Register the Amazon EC2 Cloud Provider and Template.

Familiarize yourself with custom properties for vCloud Automation Center deployments and reserved custom properties. See vCloud Automation Center Operating Guide.

Verify that a deployment profile is created. See Create a Deployment Profile.

1

Select a deployment environment from the list and click Map Details.

You can view the corresponding list for the Deployment Environment section, click the title bar and select Clouds > Deployment Environments from the drop-down menu.

2

In the External Services section, map an external service to an external service instance in the deployment environment.

If the list of external service instance is empty, the existing instance was not registered in the deployment environment. If you have access, register at least one external service instance or ask your cloud administrator to register an instance for you.

Associated external service instances appear in the drop-down menu.

3

In the VM Templates section, map a logical template to a cloud template in the cloud environment.

If the list of cloud templates is empty, the existing cloud templates do not belong to your group or a cloud template was not registered. If you have access, log in to the group that has existing cloud templates, or register at least one cloud template in vCloud Application Director. You can also ask your cloud administrator to register a cloud template for you.

For vCloud Automation Center, the cloud templates that have the same reservation policy as the deployment environment appear in the drop-down menu.

Cloud templates that belong to the same group as the user appear in the drop-down menu.

4

(Optional) For vCloud Automation Center deployments, click the Extra Configuration icon (Add custom properties to each vCloud Automation Center node) to add custom properties to each node in the application blueprint.

The custom properties should not be vCloud Application Director reserved and internal properties. If you use these properties, you receive an error message.

a

Define custom properties to map the Management Network to a vCenter Server direct network and the Service Network to a vCenter Server routed network for the sample Clustered Dukes Bank application.

The vCenter Server direct network is network1 and the vCenter Server routed network is network2.

b

In the appserver node row, click the Extra Configuration icon (Add custom properties to each vCloud Automation Center node), type virtualmachine.network0.name=network2 in the Extra Configuration Information for appserver dialog box, and click Save.

c

In the database node row, click the Extra Configuration icon (Add custom properties to each vCloud Automation Center node), type virtualmachine.network0.name=network2 in the Extra Configuration Information for database dialog box, and click Save.

d

In the load_balancer node row, click the Extra Configuration icon (Add custom properties to each vCloud Automation Center node), type virtualmachine.network0.name=network1 virtualmachine.network1.name=network2 in the Extra Configuration Information for load_balancer dialog box, and click Save.

5

For vCloud Director and Amazon EC2 deployments, in the Networking section select a supported cloud network for each logical network in the catalog.

For example, for a load balancer, if you are deploying the application to a test environment, you might select an internal network for both load balancer network NICs. When you create a deployment profile for the production environment, you might select an internal network for one load balancer NIC and an external network for the other load balancer NIC.

6

In the Disks section, map each individual disk to a specific storage.

The Disks section might be empty in the following scenarios:

The corresponding application blueprint might not define additional disks. In such a scenario, leave the section empty and continue the deployment.

A non-vCloud Automation Center deployment environment is selected. In such a scenario, you can safely ignore the warning message, Selected Deployment Environment does not allow customization of disks in the VM. Disks defined in the blueprint will not be provisioned. The deployment might fail if the action scripts depend on customized disk settings in the blueprint. and continue with the deployment.

Flexible disk layout lets you place the disks in specific datastores to gain maximum performance and minimum cost.

For example, create the operating system disk on a fast datastore to gain better performance and create an archive disk on a slow datastore to reduce the cost.

7

When you finish making your selections, click Next.

The Application Properties tab appears.

Define the applicable property values for the node, service, and application components. See Configure the Application Properties Tab.