Sunday, September 18, 2016

vRealize Automation 7.1 - Configuration Setup difference from vRA 7.0


You must be aware of the new vRA 7.1 release by now.
Most of you would have deployed it already in your production setup or lab at least.

For readers who are still yet to try the setup of vRA 7.1, there is a fantastic blog from my learned friend - Sajal Debnath @ vtechguru.com

Has has a series of posts describing step by step procedure of deploying and doing initial configuration of vRealize Automation 7.0. While most of it remains the same for vRealize Automation 7.1 besides a small change which i would want to highlight in this post below.

If you go through his article on http://vtechguru.com/2015/12/part-iii-vrealize-automation-70.html

Check out the screenshot in the above link named "Endpoint Details". The configuration wizard in the vRA 7.0 setup used to ask for the following inputs

1) Endpoint Name: Name specified for the endpoint during vSphere Proxy agent installation (while vRA appliance/IaaS is been installed and configured)

2) Endpoint host: FQDN of the host where endpoint agent has been installed. Generally the IaaS server FQDN

3) Endpoint Compute Resource: The Endpoint FQDN itself, which needs to be managed by IaaS (i.e. vCenter FQDN in case of vSphere env.)


However there is a slight change here in vRA 7.1 configuration wizard...
The above listed options have been tweaked and below details are been asked for

1) Endpoint Name: This remains same as above

2) Endpoint FQDN: Its the endpoint FQDN itself, which needs to be managed by IaaS (i.e. vCenter FQDN in case of vSphere env.)

3) Endpoint Resource: Resource you want to manage in your endpoint (like a Cluster in vCenter). This can be later appended or modified in the "Infrastructure-> Fabric Group" section.


I spent some 15 mins extra figuring out this change by checking through the logs and vRO service designer. Hope you find this post useful and like the new vRA release.

No comments:

Post a Comment