VCLOUD AUTOMATION CENTER

This is the second part of the 3rd article in a series about how to build-out a simple vCAC 6 installation to a distributed model. By the end of this part, we will not have modified the vCAC deployment in any way, we’ll just have 3 configured load balanced URLs vCAC Simple Install with vPostgres deployed and load balancers prepared An overview of the steps required are below:

This is the second article in a series about how to build-out a simple vCAC 6 installation to a distributed model. The diagram below shows the deployment at the end of this part, with vPostgres deployed and the vCAC Appliance running from the remote database. vCAC deploymnent with vPostgres deployed An overview of the steps required are below: Issue and install certificates Deploy an external vPostgres appliance and migrate the vCAC database Configure load balancing Deploy a second vCAC appliance and configure clustering Install and configure additional IaaS server Deploy vCenter Orchestrator Appliance cluster Create the required DNS records First of all, create DNS records for your vPostgres database server – you need both an A and PTR record.

This is the first article in a series about how to build-out a simple vCAC 6 installation to a distributed model. Simple vCAC deployment In a simple installation you have the Identity Appliance, the vCAC appliance (which includes a vPostgres DB and vCenter Orchestrator instance) and an IaaS server. The distributed model still has a single Identity Appliance but clusters 2 or more vCAC appliances behind a load balancer, backed by a separate vPostgres database appliance.