In this step, you drag a vCenter machine resource onto the design canvas and add settings for a VMware Cloud on AWS deployment in vRealize Automation Cloud.

Note: This procedure is not necessary if you created your VMware Cloud on AWS cloud account by using the procedure described in Create a VMware Cloud on AWS cloud account in vRealize Automation Cloud for an SDDC within a US region. That procedure creates a cloud template and catalog entry for you.

Create a cloud template design that you can deploy to available VMware Cloud on AWS resources.

Unless otherwise indicated, the step values that you enter in this procedure are for this example workflow only.

Prerequisites

Procedure

  1. Click the Design tab and then click New.
    Setting Sample Value
    Name vmc-bp_abz
    Description 1
    Project VMC_proj-1_abz

    This is the project that you created earlier, which supports the cloud zone that you also created earlier. The project is now associated with the cloud zone, which in turn is associated with the VMware Cloud on AWS cloud account/region that you created earlier.

  2. Slide a vSphere machine resource onto the canvas.
  3. Edit the following (bold) cloud template resource code in the machine resource.
    formatVersion: 1
    inputs: {}
    resources:
      Cloud_vSphere_Machine_1:
        type: Cloud.vSphere.Machine
        properties:
          image: ubuntu-1604
          cpuCount: 1
          totalMemoryMB: 1024
          folderName: Workloads
    

    The image can be any value that is appropriate to your deployment needs.

    You must add the folderName: Workloads statement to the cloud template design code to support VMware Cloud on AWS deployment. The folderName: Workloads setting supports the CloudAdmin credentials in the VMware Cloud on AWS SDDC environment and is required.

    Note: While the folderName: Workloads setting shown in the above code sample is required, you can add it directly in the cloud template code as shown above or you can add it in the associated cloud zone or project. If the setting is specified in more than one of these three places, the precedence is as follows:
    • The project setting overrides the cloud template setting and the cloud zone setting.
    • The cloud template setting overrides the cloud zone setting.

    Note: You can optionally replace the cpuCount and totalMemoryMB settings with a flavor (sizing) entry, as shown below:

    formatVersion: 1
    inputs: {}
    resources:
      Cloud_vSphere_Machine_1:
        type: Cloud.vSphere.Machine
        properties:
          image: ubuntu-1604
          flavor: small
          folderName: Workloads
    

    If the cloud zone has the folder value set to Workloads, you do not need to set the folderName property in the cloud template, unless you want to override the cloud zone folder value.

What to do next

Expand on this basic VMware Cloud on AWS workflow by adding network isolation. See Configure an isolated network in VMware Cloud on AWS workflow in vRealize Automation Cloud.