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 Decision

Decision ID

Design Decision

Design Justification

Design Implication

CSDDC-CMP-001

Use a single vRealize Automation installation to manage the consolidated pod.

You can use the single vRealize Automation instance for future expansion to the two pod design.

CSDDC-CMP-002

Deploy vRealize Automation in Enterprise Installation mode with no HA.

This design allows for a fully functional cloud management portal with an embedded vRealize Orchestrator while satisfying the minimal footprint requirements of the consolidated pod. The design also ensures that future expansion to a two pod 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 AD Requirement

Decision ID

Design Decision

Design Justification

Design Implication

CSDDC-CMP-003

vRealize Automation IaaS VMs are joined to Active Directory.

This is a requirement for use with vRealize Automation.

Active Directory access must be provided using dedicated service accounts.