This design deploys vRealize Orchestrator as two servers behind a load balancer. A vRealize Orchestrator appliance is used for each instance required in the SDDC.

vRealize Orchestrator Deployment Decision

Decision ID

Design Decision

Design Justification

Design Implication

SDDC-CMP-VRO-05

Deploy a minimum two-node vRealize Orchestrator external appliances behind a load balancer.

Supports a highly available vRealize Orchestrator environment.

Cluster setup of vRealize Orchestrator is required.

An external shared database is required.

vRealize Orchestrator Anti-Affinity rules

Decision ID

Design Decision

Design Justification

Design Implication

SDDC-CMP-VRO-06

Apply vSphere Distributed Resource Scheduler (DRS) anti-affinity rules to the vRealize Orchestrator components

Using DRS prevents vRealize Automation nodes from residing on the same ESXi host and thereby risking the cluster's high availability capability

Additional configuration is required to set up anti-affinity rules. Only a single ESXi host in the management cluster, of the four ESXi hosts, will be able to be put into maintenance mode at a time.

The vRealize Orchestrator appliance using Linux  comes preconfigured, enabling fast deployment.

The vRealize Orchestrator appliance package is distributed with preinstalled software contains the following software components:

SUSE Linux Enterprise Server 11 SP3 for VMware, 64-bit edition

PostgreSQL

Orchestrator