Hello again everyone and sorry that the posts are coming far and between.  Been deep in the trenches at work getting lots of details ironed out at work around our self-service/IaaS initiative.  That along with studying pretty heavily for the vCAP-DCD, which I am giving a go at real soon have been pretty consuming.  So is the life of an IT geek, but that is what I love about my job, working with new technologies, digging into the details, and spreading the word about them to others.  Ok, enough ranting for now and on to the details.  In this post I am following up on an earlier post I had on vCAC Endpoints.  In vCAC there are two things that need to be configured in order to scan and pull in the info from your vCenter .  One, Endpoints that basically hold the credential /connection info and the proxy agents that use the Endpoints information to scan the vCenter .  Below is a step by step on how to deploy and configure a vCenter Agent in vCAC.  A vCAC server can have multiple vCenter agents associated with it and there are serveral other types of Proxy Agents that can be used for other purposes.

Download and run the DCAC-Agent-Setup.exe from the server that will be the proxy agent. In many cases this can and will be the vCloud Automation Center

Click install on the following screen and then next

vcac agent 1

I also wanted to cover an interesting error I ran into while deploying the agent.  I understand that’s it’s probably because I tried to do something out of the norm, but it would be great if the error where a little more informative.   On the following screen you are asked to provide the FQDN with port for the vCloud Automation Center and Model Manager Web Service.  In the lab environment these roles where the same server and I created a CNAME for this the server in DNS.  When I attempted to use the CNAME I got a very generic error.

On the following screen I provided a username/password for the vCloud Automation Center Agent service and clicked next.

vcac agent 2

Then I provided a username/password that had access to the model manager  service and clicked next.

vcac agent 3

 

As you can see I got an access denied error relating to the Model Manager Web Service.  I believe this stems from the fact that it is looking for the actual machines FQDN that was used during the install of the service.  I just doesn’t like the CNAME.

vcac agent error

One thing to note is in my lab I am installing the proxy agent on the box also, so if I  used “localhost:80” or the FQDN that of where these services are run from i.e. FQDN.unm.edu:80.  When I used either of these it worked just fine.  You will notice in the lab environment I am using HTTP:80 and in production this would be done over HTTPS:443.  Input this info along with and agent name then click next.

vcac agent 4

vcac agent 13

You will then be asked to provide name for a “vSphere Generic Endpoint”.  In here you can enter the name you would like for the endpoint.  I would like to note that this endpoint could have been pre-configured via the vCloud Automation Center and if it was you would want to provide the name you used for the Endpoint when you created it.

vcac agent 5

 

 

Click next and then install.

vcac agent 6

 

Click finish.  Now when you look in services on you will see a service for the agent you created.

vcac agent 7

 

If you already have your Proxy Agent assigned to an Endpoint you do the following to make the Compute Resources from the vCenter available.  The cool thing here is as you’re doing this you can bring existing machines in and assign them to provisioning groups.

Browse to https://vCACPortalURL/dcac and click on Discovery off the menu to the left.

vcac agent 8

You will then be presented with the “Infrastructure Organizer”  wizard, click next.

vcac agent 9

 

There will be new compute resources listed that represent the available clusters within your vCenter.  Select the ones that you would like to use with vCloud Automation Center and click next.

vcac agent 10

 

Click on the edit icon(a pencil) and assign any additional Enterprise Groups or a Cost Profile to the Compute Resource.  Click the green check mark when you and done and then next.

vcac agent 11

Assign any existing VMs to a Provisioning Group by clicking on the edit icon(a pencil) and selecting the appropriate group.  Click the green check mark when you are done, click next,  finish, and then ok.

vcac agent 12