This guide will show you how t configure and use vCO to extend the out of the box vCAC provisioning work flows. All this without ever using vCAC design center. This enables you to do things like call out to other systems that may need to be updated as part of the provisioning process, run scripts in the guest VM, open firewall ports or configure a load balancer.
For this guide you will need the following:
- vCAC 6 installed and configured to provision to vSphere See the guide here
- A Linux or windows based Blueprint Published to the vCAC catalog
- vCAC configured to connect to the embedded vCO client See my guide here
- vCAC Plugin for vCO configured and connected to vCAC See my guide here
- vCenter Plugin for vCO configured to connect to the vCenter that hosts your vCAC reservations and blueprints.
The following diagram shows what this will enable. We are basically going to modify the vCAC workflow stubs to call a vCO workflow instead of using the Visual Studio based design center to extend vCAC provisioning workflows.
The first thing we need to do is verify that the vCenter plug-in and vCAC plug-ins are installed and working properly. Login to the vCO client from the vCAC appliance web page
Login as firstname.lastname@example.org and the password you set during the vCAC ID appliance installation
Change to Administer view and browse the vCAC plugin to verify you are talking to your IaaS server.
Now let’s check the vCenter Plugin, make sure you can see the datacenter and clusters that you are provisioning Blueprints to.
Now let’s install the vCAC extensibility to modify the vCAC workflow stubs to run vCO workflows at machine states. Change the view to Run, then change to the workflows tab, then browse to the Install vCO customization workfow. Right click on it and select start workflow
Please Note: The following steps will modify your vCAC workflow stubs. If you have done work in design center already those workflows will no longer run. If you would like to continue to use workflow stubs you will need to manually modify the stubs in design center and add the vCO customization manually.
Now that we got that out of the way, let’s proceed. Select you vCAC host from the list.
Now select the Worflow stubs you want to modify and click next
You can make the Number of Menu Operations 1.0 and click submit. We actually don’t use this anymore as of vCAC 6
Now when you look at the stubs in vCAC Design Center they should look like this:
You are now ready to move on to Part 2. In the next guide we will pass custom properties to vCO to run a hello world script in the guest VM during the vCAC provisioning process.