In the Part1 I have created a vCO workflow to get an ESX host from provided ESX Cluster name to pass it to the cloneVM action in vCO.
So now is time to get less used datastore of this host as another parameter for the cloneVM action. My workflow looks like this
Like I wrote in one of my previous host I’m currently playing with VMware Orchestrator. We’re working on full automated VM deployment, where one of the actions is cloneVM task.Some of the input values for this action are host and datastore. One can define this values as fixed ones in vCO, but what going on when in ones environment there is more than one cluster in vCenter. What I did, I created few simple workflows to find the ESX host of provided vCenter cluster name and then a workflow which finds less used datastore of this cluster. I was lucky, because I had an Orchestrator product consultant who showed me how to do this properly (according to the best practices). Continue reading