Skip to main content

Adding a vCloud Air (PAYG/Gen2) instance to vRealize Orchestrator as a vCloud Director host

 Author
Author
Sam McGeown
Steely-eyed missile man
Warning: This article is now 10 years old! It is highly likely that this information is out of date and the author will have completely forgotten about it. Please take care when following any guidance to ensure you have up-to-date recommendations.

vRABig thanks to Jose Luis Gomez for this solution, his response to my tweet was spot on and invaluable!

I’ve been trying to configure vCloud Air as a vCloud Director host in vRealize Orchestrator in order to create some custom resource actions for Day 2 operations in vRealize Automation. What I found was that there’s *very* little information out there on how to do this, and I ended up writing my own custom resource mapping for the virtual machines to VCAC:VirtualMachine objects - at least that way I could add my resource action. But this still didn’t expose the vCloud Director functionality for those machines. To do this I needed vCloud Air added as a vCloud Director host.

As per Jose’s advice, I duplicated the “com.vmware.library.vCloud.Host/addHost” action, named it “addHost_vCA_G2”:

I then modified the following line to include “/api/compute”:

newHost.url = "https://" + host + ":" + port;

Becomes

newHost.url = "https://" + host + ":" + port + "/api/compute";

I then duplicated the "Add a connection" workflow to create "Add a connection (vCloud Air Gen2)" and swapped the old action for the new action:

2016-04-19_11-00-46

2016-04-19_11-02-31

Now I can add vCloud Air (PAYG/Gen2) as an endpoint in the normal way:

2016-04-19_11-10-02

The out-of-the-box "IaaS vCD VM" Resource Mapping now works in vRA and I can create custom Resource Actions against the vCloud:VM object type.

Once again, big thanks to Jose for this solution!