You can 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 Application Services to override the vRealize Automation blueprint custom properties, mapping predefined disks to storage, or add to the existing properties.

About this task

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, Application Services 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, Application Services 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 Application Services 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.

You can connect to external cloud networks by mapping a cloud template. To connect to external cloud network:

  • Ensure that the network profiles should be of external type.

  • Ensure that you assign it to the network path or create reservations.

Select the cloud network name from the drop-down list and choose a network map to the NICs defined in the nodes or clusters. Click the icon next to the cloud network name to view the network details.

You can optionally define a vRealize Automation blueprint to contain individual custom properties or collections of custom properties grouped as build profiles. These custom properties are applied to a virtual machine when it is created. Application Services lets you override the vRealize Automation blueprint custom properties or add to the existing properties. For example, to override the existing vRealize Automation 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.

For related information about defining and using custom properties on blueprints, see Custom Properties Reference.

Note:

Do not use the Application Services reserved and internal properties as your custom properties.

See Application Services Reserved and Internal Properties.

Note:

While the Extra Configuration option remains available, it is recommended that you add custom properties to the machine blueprint in vRealize Automation, rather than add them using the Extra Configuration option. Custom properties that you add to the machine blueprint in vRealize Automation are visible as node properties when you request application provisioning from the vRealize Automation catalog. However, you can use the Extra Configuration option to add additional custom properties that are not present as part of the machine blueprint, including custom properties that are not part of the blueprint's associated build profiles or business group.

Prerequisites

Procedure

  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 Application Services. You can also ask your cloud administrator to register a cloud template for you.

    For vRealize Automation, 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 vRealize Automation 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.

    Do not use Application Services reserved and internal properties.

    1. 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.

    2. 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.
    3. 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.
    4. 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 vRealize Automation 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.

Results

The Application Properties tab appears.

What to do next

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