This design uses NSX logical switches to abstract the vRealize Automation application and its supporting services. This abstraction allows the application to be hosted in any given region regardless of the underlying physical infrastructure such as network subnets, compute hardware, or storage types.

Table 1. vRealize Automation Topology Design Decisions

Decision ID

Design Decision

Design Justification

Design Implication

CSDDC-CMP-001

Use a single vRealize Automation installation to manage deployments to the consolidated cluster.

You can use the single vRealize Automation instance for future expansion to the full SDDC design.

Relies on vSphere HA for application availability.

CSDDC-CMP-002

Deploy vRealize Automation in Enterprise Installation mode with no high availability.

  • This design allows for a fully functional cloud management portal with an embedded vRealize Orchestrator while satisfying the minimal footprint requirements of the consolidated cluster.

  • The design ensures that future expansion to a dual-region design is viable.

Using an NSX load balancer simplifies vRealize Automation deployment, and any subsequent scale out and integration.

Relies on vSphere HA for application availability.

Table 2. vRealize Automation IaaS Active Directory Requirements

Decision ID

Design Decision

Design Justification

Design Implication

CSDDC-CMP-003

Join vRealize Automation IaaS VMs to Active Directory.

Active Directory access is a hard requirement for vRealize Automation.

Active Directory access must be provided using dedicated service accounts .