vRealize Automation Cloud Assembly cloud zones are sections of compute resources that are specific to your cloud account type such as AWS or vSphere.

Cloud zones are specific to a region, you must assign them to a project. There is a many to many relationship between cloud zones and projects. vRealize Automation Cloud Assembly supports deployment to the most popular public clouds including Azure, AWS and GCP as well as to vSphere. See Adding cloud accounts to vRealize Automation Cloud Assembly.

Additional placement controls include placement policy options, capability tags, and compute tags.

  • Placement policy
    Placement policy drives host selection for deployments within the specified cloud zone.
    • default - Distributes compute resources across clusters and hosts randomly. This option works at an individual machine level. For example, all machines in a particular deployment are distributed randomly across the available clusters and hosts that satisfy the requirements.
    • binpack - Places compute resources on the most loaded host that has enough available resources to run the given compute.
    • spread - Provisions compute resources, at a deployment level, to the cluster or host with the least number of virtual machines. For vSphere, Distributed Resource Scheduler (DRS) distributes the virtual machines across the hosts. For example, all requested machines in a deployment are placed on the same cluster, but the next deployment may choose another vSphere cluster depending on the current load.

      For example, let's assume you have the following configuration:

      • DRS cluster 1 with 5 virtual machines
      • DRS cluster 2 with 9 virtual machines
      • DRS cluster 3 with 6 virtual machines

      If you request a cluster of 3 virtual machines and you select a Spread policy, they should all be placed on cluster 1. The updated loads become 8 virtual machines for cluster 1, while the loads for clusters 2 and 3 remain the same at 9 and 6.

      Then, if you request an additional 2 virtual machines, they are placed on DRS cluster 3, which will now have 8 virtual machines. The load for clusters 1 and 3 remain the same at 8 and 9.

    If two cloud zones both match all the criterias needed for provisioning, then the placement logic selects the one with higher priority.

  • Capability tags

    Blueprints contain constraint tags to help determine deployment placement. During deployment, blueprint constraint tags are mapped to matching capability tags in cloud zones to determine which cloud zones are available for compute resource placement.

  • Computes

    You can view and manage the compute resources that are available to provision workloads, such as AWS availability zones and vCenter clusters, to this cloud zone.

    If a vCenter compute cluster is DRS-enabled, the cloud zone only displays the cluster in the list of computes and it does not display the child hosts. If a vCenter compute cluster is not DRS-enabled, the cloud zone only displays standalone ESXi hosts, if present.

    Compute tags help to further control placement. You can use tags to filter available compute resources to only those that match one or more tags, as shown in the following examples.

    • Computes contain no tags and no filtering is used.

      Cloud zone screen where computes contain no tags

    • Two computes contain the same tag but no filtering is used.

      Cloud zone screen where 2 computes contain the same tag

    • Two computes contain the same tag and the tag filter matches the tag used on the two computes.

      Cloud zone screen where the tag filter matches the tag for the 2 computes

  • Projects

    You can view which projects have been configured to support workload provisioning to this cloud zone.

After you create a cloud zone, you can validate its configuration.