In this design, the core vRealize Automation application and its supporting services are in the hub. The same instance of the application manages workloads in all regions and ROBO locations.
Table 1. Design Decisions on the vRealize Automation Topology

Decision ID

Design Decision

Design Justification

Design Implication

ROBO-CMP-001

In each ROBO site, deploy vRealize Automation IaaS Proxy Agents that connect to a single vRealize Automation installation in the hub.

  • Provides localized communication with vSphere for each ROBO infrastructure from the vRealize Automation cluster in the hub.

  • You can use a single consumption portal regardless of the region or ROBO location.

  • Because of the abstraction over virtual networking, the vRealize Automation application is independent from physical site location or hardware.

You must size vRealize Automation for multi-region and ROBO deployments. vRealize Automation supports up to ten connected vCenter Server instances.

Table 2. Design Decisions on Anti-Affinity Rules for vRealize Automation

Decision ID

Design Decision

Design Justification

Design Implication

ROBO-CMP-002

Apply vSphere Distributed Resource Scheduler (DRS) anti-affinity rules to all vRealize Automation components in the ROBO site.

Using vSphere DRS prevents vRealize Automation nodes from residing on the same ESXi host and risking the high availability of the cluster.

You must perform additional configuration to set up an anti-affinity rule.