vRealize Orchestrator : Add new port group to standard virtual switch to all hosts of ESX cluster

There are situations when one need to add a new port group to the existing standard vSwitch in vCenter. This is easily configurable in the vCenter in the host configuration. This can be done manually on the small number of hosts, however on bigger number it can be really annoying. What offers vRO as basis. In the built in workflow list under the “Library->vCenter->Networking->Standard Virtual Switch“, one can find a workflow “Add port group in the standard virtual switch“. It’s good for the start, so let’s see what it needs Continue reading

vRealize Orchestrator : Find network card by MAC

In this post I’ll focus mostly on code for creating simple vRO action to find a virtual machine network card by its MAC address. A use case for me was to set and IP address on VM with multiple network cards or delete a network card with specific MAC address. So instead of creating a new workflow I decided to create an action. Continue reading

VMware vCO – cloning VM, using cluster name instead of host and getting less used datastore of chosen host. – Part 2.

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
GetLessUsedDatastoreOfHost
Continue reading

VMware vCO – cloning VM, using cluster name instead of host and getting less used datastore of chosen host. – Part 1.

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