By using the cloud automation layer, you provide automated workload deployment to tenants by using vRealize Automation.

Figure 1. Logical Design of vRealize Automation


Figure 2. vRealize Automation Usage Model


Table 1. Cloud Automation Design Details

Design Attribute

Description

Deployment model of vRealize Automation

A cluster of three vRealize Automation nodes with a load balancer. The cluster is deployed by using vRealize Suite Lifecycle Manager.

vRealize Automation services

  • Cloud Assembly
  • Service Broker
  • Orchestrator (using the embedded vRealize Orchestrator)

Network segment

Cross-region virtual network segment. See Dynamic Routing and Virtual Network Segments.

Cloud accounts

  • Workload domain vCenter Server

  • Workload domain NSX-T Local Manager

Note:

Deploying workloads on a workload domain by using vRealize Automation requires that you deploy an NSX-T Data Center instance for each domain.

Cloud zones

One cloud zone mapped to one region

Tagging

  • For the shared and workload cluster, apply tagging on the resource pools

  • For workload clusters, apply tagging at the vSphere cluster

Tenants

A single tenant company called Rainpole

Workload placement setup

  • My VMware integration to download and provision blueprints from VMware Marketplace
  • Flavor mappings to define the deployment sizings
  • Image mappings to define target deployment operating system and related configuration settings
  • Network profiles to define the subnet and routing configuration for the provisioned virtual machines
  • Storage profiles to define disk customizations and type of storage for the provisioned workloads
  • Projects to define the users that can provision workloads, the priority and cloud zone of deployments, and the maximum allowed deployment instances.
  • Content sources and catalogs to provide access to blueprints to users.