Scale out a standalone Automation Orchestrator deployment

You can increase the availability and scalability of your configured Automation Orchestrator deployment by scaling it out.

Prerequisites

• Download, deploy, and configure an Automation Orchestrator instance. Go to Download and Deploy the Automation Orchestrator Appliance and Configuring a Standalone Automation Orchestrator Server.
• Download and deploy two additional Automation Orchestrator instances. Go to Download and Deploy the Automation Orchestrator Appliance.
• Configure a load balancer server. Go to Load Balancing Guide.

Procedure

1. Configure the primary node.
   1. Log in to the Control Center of your configured Automation Orchestrator deployment as root.
   2. Select Configure Authentication Provider and unregister your authentication provider.
   3. Select Host Settings and enter the host name of the load balancer server.
   4. Select Configure Authentication Provider and register your authentication provider again.
   5. Log in to the Automation Orchestrator Appliance command line of the configured instance as root.
   6. To stop all the services of the Automation Orchestrator instance, run the /opt/scripts/deploy.sh --onlyClean command.
   7. To set the load balancer, run vracli load-balancer set load_balancer_FQDN.
   8. (Optional) If your Automation Orchestrator instance uses a custom certificate, run the vracli certificate ingress --set your_cert_file.pem command.
   Note: The file containing the certificate chain must be PEM-encoded.
2. Join secondary nodes to the configured instance.
   1. Log in to the Automation Orchestrator Appliance command line of the secondary node as root.
   2. To join the secondary node to the configured instance, run the vracli cluster join primary_node_hostname_or_IP command.
   3. Repeat for the other secondary node.
3. Finish the scale-out process.
   1. Log in to the Automation Orchestrator Appliance command line of the configured instance as root.
   2. Run /opt/scripts/deploy.sh and wait for the script to finish.

Results

You have scaled out your Automation Orchestrator deployment.

Note: For a deployment with three Automation Orchestrator instances, the scaled out deployment can withstand one instance failing and still function. Two instances failing renders the Automation Orchestrator deployment non-functional.