VCAC can connect to a number of Endpoints. In this article we will go through how you can connect VCAC to vCenter and use resources discovered there.
I should point out that this procedure can be used for your first vCenter or adding resources from additional vCenters.
Adding a vCenter requires a couple of things be done in a very specific manner, highlighted here.
- Each vCenter that you would like to use resources from, requires a vSphere Proxy Agent be installed for that resource. One vCenter requires 1 agent, 3 vCenters require 3 Agents. These agents can be installed on the same machine.
- When installed each agent Endpoint name much match exactly, including capitalization.
These points will become more clear later in this article.
This article will cover connecting VCAC with a vSphere endpoint you can then assign these resources to a fabric group inside VCAC so tasks can be performed against that resource
- Log into your VCAC web Console as a tenant administrator. Navigate to the infrastructure tab and choose Endpoints, then Endpoints
- From here you will choose “new endpoint”.
- On the “New Endpoint – vSphere (vCenter) page you are required to fill out several fields. Copy whatever you put into the “Name” field. This will be used when you install the agent.
- Log into the machine you have chosen to put the vSphere proxy agent on. The user that you will use to access vCenter must be given the “Allow log on locally” and the “Log on as a service” permission within Local Security Policy. Failure to do this will cause the install to fail.
- Open a browser and navigate to the URL of your VCAC appliance https://machinename_or_ipaddress. From here you will choose the “vCloud Automation Center IaaS installation page” link as seen in the image below.
- Once the file is downloaded, double-click to kick off the install. Choose next through the first screen and the second screen, after accepting the user agreement. On the screen where it is asking for a login, this should have the name of your VCAC server populated. The user name Should be root. The password should be the root password that is set for your VCAC server. Then choose next.
- On the installation Type page, choose Custom Install and the Proxy Agents Radial Button. You can also choose to change the install directory if you so choose. Then choose next.
- On the next screen you should see a form like in the image below, Local server should be populated with the name of the machine you are installing this on, username should be the user that has access to the vCenter you are connecting to. If you have not added the permissions for this user from step 1 the install will throw an error saying the user does not have correct permissions. Click next
- On the “Install Proxy Agent” screen there are several fields that are very important, as seen in the image below. First, “Agent type:” should be set to vSphere in our case, the next field “Agent name:” is what you will see in various places within VCAC, I would advice that you make it the same as the name of the endpoint this agent will be used to connect to. The third field “Manager Service Host name:” is the name of the server that hosts the Manager service, (often your IAAS server) FQDN or IP works for this. The next field is for the Model Manager Web Service machine, this is also often on the IAAS box. The last field listed as Endpoint: is the most important. This field MUST match EXACTLY what was entered as the endpoint name including capitalization in our case SuPerCool.
- On the last page click Install. Once the box closes the agent should start. The agent should query the endpoint collecting all the resources. After a few minutes you should can go into your Fabric group and see the resources that were queried from this new end point.
Configure the vSphere Agent: http://pubs.vmware.com/vCAC-60/index.jsp#com.vmware.vcac.install.doc/GUID-0D0FDCFE-DF26-4168-A8DD-E29D058C066C.html