Automation, Management, Orchestration is all about Cloud!!!
Dare To geek on it!!!! ;)

Wednesday, 22 February 2017

vRealize Automation 7.2 - Distributed Deployment

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

Choose the Deployment method

Install the Management Agent on the IaaS Node and make sure that they are on the same NTP server. I used Vmware NTP Server "0.vmware.pool.org" but you can choose whichever you want to.

Here add the Second node of the vRA Appliance with the root Username and password supplied.

Accept the Certificate which is prompted to create trust between both nodes.

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.

Run the Prerequisite checker. Choose to Run 'Fix' which will find the dependencies and install & configure them for you within sometime.

I choose to run 'Fix' which will fix everything for me and make IaaS server workable as per recommendations.

Walah!!!! Everything is alset!!! Ready to deploy the content to the 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 Manager Service Role Detail, You may choose to have different server for this role.

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.

Provide the Agent Detail, in my case, I am deploying vSphere agent.

Generate or import the SHA2 certificate for the Appliance.

Generate the Certificate for the Web Certificate

Apply the Same Web Certificate for Manager Service.

Summary for the How the Load Balancers should be configured as this point.

Run the Validate, which will run the validation on all IaaS configuration provided during previous steps.

Validation Executing!!!

And ALL GREEN, we are all set to proceed with the installation.

Wait!!!! You need to take Snapshots for all the components, if in case the installation fails, you can easily revert to the snapshot and fix the issue and re-execute it.

Ready to Hit the Install Button.

Installation takes some time to complete which depends your deployment architecture.