vRealize Automation 7.2 - Distributed Deployment
I guess this is most of us are trying to build with robust vRA 7.2 highly available deployment as compared with vRA 6.x version. This vRA 7.2 utilized HAProxy for their internal components Load Balancing which includes Postgresql, VRA & VRO.
vRealize Automation Install - Distributed Deployment:
My Lab vRA Distributed Deployment is little bit different from the recommended deployment because of the resource crunch in the cluster.
Following is the choice of Distributed Server Sizing
Role
|
Server Name
|
LB Endpoint
|
vRA Appliance
|
vra01.automations.local
vra02.automatons.local
|
vralb.automations.local
|
IaaS Node
|
Iaas01.automations.local
|
Iaaslb.automations.local
|
Few of the basic Requirement which should be considered.
Even if the Load balancers are configured with the nodes attached (if you have one, I had it created beforehand), do not configure any Monitors.
Do not open the wizard on any of the other nodes other than Node 1.
Do not browse the Node via Load Balancer URL, always try to browse using the Node 1 direct URL.
Do not install any Windows components of the IaaS node, this is being taken care by Pre-requisite checker.
Procedure
VMware has provided the very descriptive explanation of the each role which can be applied to the different IaaS server in the distributed deployment, however in my case I am not using more than one node of IaaS, so I will assign all roles to the same server.
Since this is distrusted deployment (as we all know by now), do not put the FQDN of the node, rather, enter the Load Balanced FQDN which is created earlier.
Provide DEM details, Keep in mind, DEM Orchestrator by default is being installed along the Model Manager role. So below is the details required for the DEM Worker. You can choose to deploy multiple DEM Workers.