Overview of High Availability Architecture

The architecture of the active/active high availability system in Orchestrator is comprised of the two nodes, a shared storage, and a load balancer, which monitors the health of each Orchestrator node and redirects traffic accordingly.



When the load balancer detects that an Orchestrator node is unreachable, it automatically stops redirecting traffic to the unavailable node, and redirects all traffic to the remaining healthy nodes, balancing the load among them. Once the faulty node can be reached, the load balancer automatically detects the presence of the new healthy node and includes it in the traffic-sharing function.

The load balancer is provisioned with a virtual IP address (VIP) for user access; which it uses to manage all traffic related to the Orchestrator service. A fully qualified domain name (FQDN) ―typically orchestrator.mydomain.com―is used to access the Orchestrator service and points to the VIP of the load balancer.

Both Orchestrator nodes can use private IP addresses. Only the VIP needs to be a public IP address, because it will be used by the clients to connect to the Orchestrator service components.

For additional information, see Storage Requirements, Services Stack for the Orchestrator Nodes, and Load Balancer Behavior.