The Quick cloud automation setup for VMware Cloud on AWS activation process creates a set of starter objects in vRealize Automation Cloud, including a catalog item and cloud template. It also creates infrastructure objects such as a project, cloud VMware Cloud on AWS account, cloud zone, flavor/size mappings, a network for deployments, a network profile, and a storage profile.
For example, the storage profile contains a Workload Datastore datastore/cluster that was created in the SDDC as part of the trial activation process. The network profile contains the single network for deployments that was also created as part of the trial activation process. A small, medium, large, and extra large flavor mapping is created to simplify deployment sizings.
When looking at the vRealize Automation Cloud objects that are created as part of the trial activation process, the naming follows a pattern of <SDDC_name>-<unique task ID GUID>. You can manually change these object names in vRealize Automation Cloud.
If you have just activated the trial, you can skip to step 4. If you activated the trial and did not immediately click Open vRealize Automation Cloud on the vRealize Automation Cloud add-on card in the SDDC, start with step 1.
For vRealize Automation Cloud help content, see Learn more about Quick cloud automation setup for VMware Cloud on AWS.
This example shows the various objects that are created as part of the vRealize Automation Cloud trial activation process. It seeks to explain what the objects are, what they do, and how they were derived. This example does not show the exact objects that are created by your unique activation mainly because your source SDDC is not be identical to the one used to generate these objects, but they are similar. The intent is that you use this example as a tool in gaining a working level of vRealize Automation Cloud proficiency.
Complete the trial activation process. See Activate Quick cloud automation setup for VMware Cloud on AWS.
- Log in to your VMware Cloud on AWS console, open the page that lists all of your SDDCs, and select the SDDC that you used as the source for your vRealize Automation Cloud trial.
- On the selected SDDC page, click its Add Ons tab.
- On the SDDC's vRealize Automation Cloud add on card, click Open vRealize Automation Cloud.
- Select the automatically generated catalog item in Service Broker.
If the Service Broker is not automatically visible, select the service selector (shown below) and then select VMware Service Broker to open Service Broker and display the starter catalog item.
- Click Request on the catalog item and enter a deployment name such as test.
Click VM Size to display the flavor sizings that are available for the deployment.
Click VM Template to display all the templates that were data collected from the source SDDC. In this example, the source SDDC contained only one template, thus only one template appears in the list.
- Click Submit on the catalog item to start its deployment and open the Deployments page.
- While the catalog item is being deployed, click Content & Policies and open the starter content source that was created based on your source SDDC.
- Note the starter project that was generated by the trial activation process and click Validate. Before generating a cloud template from the catalog item, click Cancel to examine a few more aspects of catalog item content before you deploy the cloud template.
- Click Cancel.
, examine the generated lease policy, and click
- Examine the cloud template that is created by the activation process by navigating to the Cloud Assembly service.
As a result of vRealize Automation Cloud trial activation, there is one cloud template, with one version that is automatically published to the catalog. This is the cloud template for the catalog item that you just examined in Service Broker.
- Select the cloud template to open it in the design canvas and display it both graphically and as code.
This example shows a simple vSphere machine component with an image reference and a flavor mapping. The
imageRefis set as the
template: enumvalue of
flavorvalue can be any of the
size: enumvalues (small, medium, large, and extra large).
In this example, there was only one template in the source SDDC. Had there been multiple templates in the source SDDC, the cloud template code would contain multiple
What to do next
To learn more about the services that comprise vRealize Automation Cloud, see Learn more about Quick cloud automation setup for VMware Cloud on AWS.