Add vCenter Endpoint - vRealize Automation Series Part 8

With administrative users setup so we can actually configure various options in vRealize Automation / vCloud Automation Center - its now time to add some compute resource, so we can actually deploy things!  Endpoints in vRealize Automation / vCloud Automation Center can be several things:

  • Hypervisor management platforms such as vCenter, vCenter Orchestrator, and SCVMM
  • Cloud providers such as vCloud Air (formerly vCloud Hybrid Service), vCloud Director providers including vCloud Air, OpenStack using RHEV 3.1
  • Physical hardware from Cisco, HP, and Dell

If you recall from the IaaS installation post, one of the options asked us to name the vCenter endpoint, now we are going to log in and configure our vCenter server as an endpoint so we can use it to deploy virtual machines through the catalog.

  • Log into your vRealize Automation / vCloud Automation Center appliance (in my case https://vxprt-vcac01.vxprt.local/vcac) as.... do you recall from the last post who to log in as?  That's right iaasadmin as that user was assigned the infrastructure administrator role which can manage endpoints
  • Once logged in, click on the infrastructure tab >> Monitoring >> Log
  • Notice here the errors related to the VRM agent occurring every minute, that is because we have not added our vCenter server yet
  • Click Back to infrastructure, then click on Endpoints >> Endpoints
  • Hover over New Endpoint >> Virtual and click on vSphere (vCenter)

  • We will need to name the endpoint, the URL to the vCenter SDK and credentials.  Since we have not already, I would create a user account in AD called svc_vra_vcbind and add it to the vcAdmins group (assuming you followed along on the home lab build, or give it admin permission directly to your vCenter)
  • Fill in the following information:
    • Name:  vCenter (Do you recall why we are naming it vCenter?)
    • Address:  vcenterurl/sdk (in my case https://vxprt-vc01.vxprt.local/sdk)
    • Credentials:  Click the ellipse, then New Credentials and add a user account with permission to vCenter and click the green circle with the checkmark
  • With all the information filled in, click the OK button
  • Once vCenter has been added, return to the log view, you should notice that the VRM Agent errors are no longer occurring

Now you’ve added resources vRealize Automation / vCloud Automation Center can use to fulfill requests, however we still need to assign those compute resources to a fabric group, which will be next in my vRealize series!

Related Posts