As part of this design, we configure the load balancer for allowing the design to scale to the full SDDC. Session persistence of a load balancer allows the same server to serve all requests after a session is established with that server. The session persistence is enabled on the load balancer to direct subsequent requests from each unique session to the same vRealize Automation server in the load balancer pool. The load balancer also handles failover for the vRealize Automation Server (Manager Service) because only one Manager Service is active at any one time. Session persistence is not enabled because it is not a required component for the Manager Service.

Table 1. Load Balancer Design Decisions

Decision ID

Design Decision

Design Justification

Design Implication

CSDDC-CMP-008

Set up an NSX edge device for load balancing the vRealize Automation services.

Enabling this design with a load balancer allows for a future expansion of the CMP with application-level HA.

Additional configuration is required to configure the load balancers

CSDDC-CMP-009

Configure the load balancer for vRealize Automation Server Appliance, Remote Console Proxy, and IaaS Web to use Round-Robin algorithm with Source-IP based persistence with a 1800 second timeout.

  • Round-robin provides a good balance of clients between both appliances, while the Source-IP ensures that individual clients remain connected to the same appliance.

  • 1800-second timeout aligns with the vRealize Automation Appliance Server sessions timeout value. Sessions that transfer to a different vRealize Automation Appliance might result in a poor user experience.

None

CSDDC-CMP-010

Configure the load balancer for vRealize IaaS Manager Service to use Round-Robin algorithm without persistence.

The Manager Service does not need session persistence.

None

Consider the following load balancer characteristics for vRealize Automation.

Table 2. Load Balancer Application Profile Characteristics

Server Role

Type

Enable SSL Pass-through

Persistence

Expires in (Seconds)

vRealize Automation - Persistence

HTTPS (443)

Enabled

Source IP

1800

vRealize Automation

HTTPS (443)

Enabled

Table 3. Load Balancer Service Monitoring Characteristics

Monitor

Interval

Timeout

Max Retries

Type

Expected

Method

URL

Receive

vRealize Automation Appliance

3

10

3

HTTPS

204

GET

/vcac/services/api/health

vRealize Automation IaaS Web

3

10

3

HTTPS

GET

/wapi/api/status/web

REGISTERED

vRealize Automation IaaS Manager

3

10

3

HTTPS

GET

/VMPSProvision

ProvisionService

vRealize Orchestrator

3

10

3

HTTPS

GET

/vco-controlcenter/docs

Table 4. Load Balancer Pool Characteristics

Server Role

Algorithm

Monitor

Members

Port

Monitor Port

vRealize Automation Appliance

Round Robin

vRealize Automation Appliance monitor

vRealize Automation Appliance nodes

443

vRealize Automation Remote Console Proxy

Round Robin

vRealize Automation Appliance monitor

vRealize Automation Appliance nodes

8444

443

vRealize Automation IaaS Web

Round Robin

vRealize Automation IaaS Web monitor

IaaS web nodes

443

vRealize Automation IaaS Manager

Round Robin

vRealize Automation IaaS Manager monitor

IaaS Manager nodes

443

vRealize Automation Appliance

Round Robin

Embedded vRealize Automation Orchestrator Control Center monitor

vRealize Automation Appliance nodes

8283

Table 5. Virtual Server Characteristics

Protocol

Port

Default Pool

Application Profile

HTTPS

443

vRealize Automation Appliance Pool

vRealize Automation - Persistence Profile

HTTPS

443

vRealize Automation IaaS Web Pool

vRealize Automation - Persistence Profile

HTTPS

443

vRealize Automation IaaS Manager Pool

vRealize Automation Profile

HTTPS

8283

Embedded vRealize Orchestrator Control Center Pool

vRealize Automation - Persistence Profile

HTTPS

8444

vRealize Automation Remote Console Proxy Pool

vRealize Automation - Persistence Profile