This tour of vRealize Automation Cloud Assembly shows you what the Quickstart configured and deployed. It is designed to guide your through the user interface and help you understand some of the tasks you might later perform on your own.

When you log in to vRealize Automation, you might see the Identity and Access Management and Branding tab. These tabs are not covered as part of the tour. You use them as you add users and manage your organizations.

For more about identity management and branding, see Administering vRealize Automation



  1. As a cloud administrator, log in to vRealize Automation.
    Cards in the console
  2. Click Cloud Assembly.
    vRealize Automation Cloud Assembly opens with the Deployments tab active.

    The deployments in vRealize Automation Cloud Assembly are the blueprints that are provisioned on your cloud account platforms. A successfully deployed blueprint represents your final goal as an administrator or blueprint designer. Because this tour is to help you understand your workflow, we start with connecting to cloud accounts first and return to deployments later.

  3. To learn how the QuickStart configured vRealize Automation Cloud Assembly to support the deployment, begin by selecting Infrastructure > Connections > Cloud Accounts.
    Cloud accounts created by the QuickStart

    Cloud accounts provide the credentials that are used to connect to your target systems. Using the provided credentials, vRealize Automation Cloud Assembly can monitor the status, collect information, and deploy workloads to those systems. In this example, you can see the NSX and vSphere instances that you provided in the QuickStart.

    Each time you run the QuickStart, a new cloud zone is added.

    1. Click the vSphere cloud account name.
      Example of vSphere cloud account details

      Notice that the account name is based on the vCenter Server FQDN and that the NSX endpoint matches the NSX instance that you provided.

      If you look at the NSX cloud account, you see same relationships regarding name and vSphere endpoint. The endpoint, in this user interface, is the cloud account.

  4. Let's look at the cloud zones that were created from the cloud accounts. Select Infrastructure > Configure > Cloud Zones
    Cloud Zones created by the QuickStart

    Cloud zones are the account regions or data centers that are associated with your cloud account. If your cloud account includes more than one region, then multiple cloud zones might be created from that cloud account. For example, you might have more than one data center or region, and each one becomes a cloud zone. Cloud zones are then associated with projects, allowing you to grant users permission to deploy to a specific set of cloud resources.

  5. To see the network you configured, select Infrastructure > Configure > Network Profiles.
    Network profile created by the QuickStart

    A network profile defines a group of networks and network settings that are available for a cloud account in a particular region or data center.

    If you run the QuickStart more than once, a network profile is added each time you run it.

  6. To see the storage you configured, select Infrastructure > Configure > Storage Profiles.
    Storage profile created by the QuickStart

    Storage profiles are organized under cloud-specific regions. One cloud account might have multiple regions, with multiple storage profiles under each region.

    If you run the QuickStart wizard more than once, a storage profile is added to the associated datacenter each time you run the wizard.

  7. To see the project that was created, even though you provided no specific values, select Infrastructure > Configure > Projects.
    Project created by the QuickStart

    Projects link users and resources so that users can only deploy to the cloud zones that you specify. You might later create other projects to support different development teams.

    1. Click the project name, and then click the Users tab.
      This tab is where you can add more users to a project.
    2. Click the Provisioning tab.
      This tab is where you add or remove the cloud zones. Notice that you have the Quickstart cloud zone.
    3. Scroll down the provisioning page and locate Custom Naming.
      Notice that the custom naming template has the machine name prefix format that you selected in the policies section in the QuickStart. The custom naming is associated with projects.
  8. To see the blueprints that were created, click the Blueprints tab.
    List of blueprints created by the QuickStart

    As part of the QuickStart, you have three blueprints. The machine blueprint was deployed, the NSX-T network and load balancer blueprints are provided as examples and were not deployed.

    If you run the QuickStart wizard more than once, you will have blueprints that are created for each wizard configuration.

    1. In the Project column, notice that blueprints are associated with the Quickstart project.
    2. In the Released Versions column, notice that each blueprint is released.
    3. To see the blueprint canvas and where you release the blueprints, click the name of the blueprint that you selected in the QuickStart. In this example, the blueprint name begins with ubuntu.
      Blueprint design canvas for blueprint created by the QuickStart.
    4. In the center is the canvas where you drag components and connect them.
    5. On the right is the blueprint-as-code YAML editor where you can refine all the details for a blueprint.
      The YAML defines the blueprint components.
    6. On the left is the searchable list of components that you can add to the blueprint.
    7. To version the blueprint, click Version and notice that there is already a released version of the blueprint.
      You can deploy blueprints in vRealize Automation Cloud Assembly that are released or unreleased. To make blueprints available in vRealize Automation Service Broker, they must be released.
  9. Click the Deployments tab.
    Deployment created by the QuickStart
    If you ran the QuickStart wizard more than once, you will have deployments as validation for each wizard configuration.
    1. Review the information that is provided on the deployment card.
      • Deployment name is Quickstart deployment.
      • Project is Quickstart project.
      • Requestor is Fritz. In your environment, it is the user account that you used to run the QuickStart.
      • Resource name is fritz-001. This name is based on the custom naming that you defined in the Quickstart. If you deploy another resource using this naming convention, the name is likely to be fritz-002.
      • Power status indicates that the resource is On.
      • Expires in the month is the starting lease period. The value will count down to the expiration date.
      • Actions are the deployment level changes you can make, including power off or destroy.
    2. Click the deployment name in the deployments list so that you can see the deployment details and review the available information.

      Deployment details
      • Name of the blueprint that was used to create the deployment. In this example, it is the template that you selected in the QuickStart.
      • The Topology tab provides a visualization of the relationship between the deployed components. This example is a simple machine. If the deployment had multiple machines, networking, and storage, you can see a more robust topology.
      • Tabs for History and Monitor. History as the log of the deployment and any changes that you make using the actions. Monitor is relevant if you integrate with vRealize Operations Manager.
      • Account regions where the resource was deployed.
      • Actions that you can run on the selected resource.
  10. To understand how the deployment was provisioned, select Infrastructure > Activity > Requests, and click the deployment name.
    Request details for the deployment machine allocation process

    The Request Details provide a graphical view of how the deployment request is processed and provisioned. You can look at the project, the machine, and the network allocation and provisioning to see where the workload was placed.

    As you create your infrastructure and blueprints, the request details provide insights that you can use to troubleshoot unexpected behavior or deployment failures.

What to do next

Continue your tour in vRealize Automation Service Broker.