You can map a deployment environment to a vCloud Automation Center reservation policy before you deploy applications to that cloud environment. If you do not select a reservation policy, vCloud Automation Center picks any suitable reservation policy at deployment time.

A vCloud Automation Center business group can have several reservations mapped to reservation policies. A reservation has a pool of resources such as memory, storage, and networking to build machines. Based on the reservation settings, you can save a virtual machine in a designated storage space and determine the network it can connect to. You use reservation policies to group similar resources to create defined service levels or to make a specific type of resource available for a particular purpose.

You can add a reservation policy with a reservation to a vCloud Automation Center blueprint. When you request a machine from this blueprint, the virtual machine is saved in a designated storage space and assigned to a network that is already defined in the reservation. If you do not map a reservation policy to a blueprint, vCloud Automation Center assigns a reservation depending on the resource requirements of the virtual machine in the vCloud Automation Center blueprint.

Log in to Application Services as an application cloud administrator.

Verify that vCloud Automation Center 6.1 or later is installed and configured.

Verify that the vCloud Automation Center business group that you plan to use with Application Services is created and configured.

Verify that you have tenant administrator privileges to access the business groups.

Users with tenant administrator privileges create and maintain business groups. For more information about business groups, see IaaS Configuration for Virtual Platforms.

Verify that you are a business group manager for the business group.

Verify that a reservation policy is created and configured in the vCloud Automation Center. The Application Services deployment environment is equivalent to the reservation policy in vCloud Automation Center.

Verify that one vCloud Automation Center cloud provider is registered in Application Services. See Register the vCloud Automation Center Cloud Provider and Template.


On the Application Services title bar, click the drop-down menu and select Clouds > Deployment Environments.


Click New.


Complete the deployment environment information.



Deployment Environment name and Description

Include the reservation policy name in either of these text boxes. The text from these text boxes appears in the Deployment Profile wizard under the Deployment Environment column.

Cloud Provider

If the cloud provider does not appear in the list, cancel the dialog box and select Clouds > Cloud Providers to add the vCloud Automation Center cloud provider.

Reservation Policy

Click Select to select from a list of reservation policies that the cloud provider you selected provides.

Reservation policies in vCloud Automation Center that include auto in the name do not appear in the reservation policy list. Rename the reservation policy so that it appears in the reservation policy list.

If you select No reservation policy, vCloud Automation Center assigns a reservation based on availability of resources.


Select a reservation policy and click OK.

A vCloud Automation Center reservation policy is mapped to the Application Services deployment environment name.


Click Save.


(Optional) To change the existing information for a vCloud Automation Center deployment environment, click Edit in the toolbar and make your changes.

For certain deployments, you can also edit the properties of the proxy settings. Changing these proxy settings lets you access external data. Click Show to edit the following properties:





If you do not edit the proxy setting properties, then the global proxy settings are considered.

When you create a deployment profile, you can select this deployment environment to deploy applications to vSphere.

You can map an external service instance, create a policy instance, or register a solution instance with the deployment environment. See Map an External Service Instance, Create a Policy Instance or Create a Puppet Solution Instance.