Adding Additional vCenter Instances to vRealize Automation

vRealize Automation (vRA), formerly vCloud Automation Center, has the ability to have multiple vCenters as endpoints. This is cool because if you need to do true multi-tenancy and a tenant has security requirements that require them to have their own vCenter instance.

When you initially install vRA you installthe IaaS component, which in turn installs a vSphere Agent responsible for only one vCenter Instance. In order to add an additional vCenter server to vRA you’ll need to install an additional agent on the IaaS server. Every vCenter instance requires its own agent. Below is the process for installing a new agent and configuing a new vCenter instance for that newly installed agent.

  • Log into your IaaS server as an administrator
  • If you don’t already have the IaaS installer downloaded goto the following page: https://:5480/installer
  • Run the installer
  • Click Next > agree to the license agreement > click Next
  • Enter in the username/password for the vRA applaince and click Next
  • Choose the Custom Install option > under Component Selection choose Proxy Agents > click Next

 

Enter in the username/password for the account you want to use to run the Windows service > click Next

  • Select vSphere as the agent type
  • Enter in a name for the agent (this is what you’ll see int he Windows Services list
  • Enter in the name of the server hosting the Manager Service (should be the IaaS server)
  • Enter in the name of the server hosting the Model Manager Web Service (should be the IaaS server)
  • Enter in a name for the Endpoint. THIS IS NOT THE NAME OF THE VCENTER SERVER. This is the name that you’ll use as the endpoint name when adding the new vCenter to vRA. They MUST match.
  • Click the Add button > click Next
  • Click Install

Now that we’ve added the new Proxy Agent to the IaaS server, it’s time to add our new vSphere endpoint to vRA.

  • Log into vRA as a tenant administrator
  • Navigate to the Infrastructure tab > click Endpoints > click Endpoints again
  • Hover over New Endpoint and then hover over Virtual > click vSphere (vCenter)
  • Enter in a Name — THIS MUST BE THE SAME NAME YOU USED FOR THE ENDPOINT NAME WHEN YOU INSTALLED THE PROCY AGENT
  • Enter in the URL for the vCener server in the format of: https:///sdk
  • Click the elipses button and specify credentials for the vCenter server. If they don’t exist, create them

  • Click the OK button
  • Once complete you can navigate to Groups > Fabric Groups and edited an existing Fabric Group (or create a new one) and all clusters that exist on the new vCenter endpoint will show up.

if you don’t see any clusters from the new endpoint check to make sure the endpoint name matches the one you set during the prox agent install. If all looks good then check the monitoring/log information within vRA to see what’s going on

Comments 1

  1. Great post thanks. Conversely how would you configure vRA to share a vCenter instance with non cloud workloads. I need to append vRA to an existing vCenter that already supports production.

Leave a Reply

Your email address will not be published. Required fields are marked *

*