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
Today, let me post my friend’s post, which is I find really amazing/magnificent. If you’re looking for the manual/guide how to replace self-signed certificates in vCenter 5.5 with PKI one, please go to the following link [How to] Replace self-signed certificates on VCSA 5.5.
The only thing I can say : THANK YOU Waldemar for posting that !!!!
And of course NOT thank you VMWARE for NOT posting that. I can imagine that all VMWARE engineers are too busy or too skilled to write such manual to fulfil Customer needs. Or just simply they are NOT skilled enough. Really poor support from vendor!!!!!!!!!!
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
In the post vRealize Orchestrator – Workflow to change DRS setting to default on single VM I presented the workflow to change DRS to manual on single VM. Now it’s the time to change this setting back to the default one, as it was. So to do this it’s quite easy to make a copy of previously create workflow.
And just edit the code of “Scriptable task”, because input parameter and attributes remain the same as in workflow described in previous post. Continue reading
Multiple times in multiple workflows, I needed to have VM not being migrated during the workflow run. Easiest way is to disable DRS on the VM. Well, it seems that DRS setting does not belong to VirtualMachine object, DRS settings is part of the ESX Cluster object. We’re still able to to set setting individually per VM, however it has to be set on ESX Cluster level not on the VM itself. I was pretty sure, that there built-in vRO workflows for such simple setting … However, it’s not. That’s what VMWare offers by default
- Add DRS virtual machine
- Add virtual machines to DRS group
- Create cluster
- Delete cluster
- Disable DRS on cluster
- Disable HA on cluster
- Enable DRS on cluster
- Enable HA on cluster
- Remove virtual machine DRS group from cluster
- Remove virtual machines from DRS group
- Rename cluster
If there is a need and there is no solution – it has to be created.
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
Nowadays I’m playing with VMware vCenter Orchestrator. I have installed the plugin for Infoblox and while trying to connect from orchestrator plugin to Infoblox device I was getting message :
“Make sure you are using proper config settings and/or proper SSL certificate of your IPAM server”
This post is for a lazy administrators. Recently I had to install vCenter and its components. Part of it is opening the proper firewall ports in Windows firewall. The list of required ports for vCenter Server 5.5 can be found on this VMWare site. However it’s just a table containing all the ports required for the specific vCenter Server component. I run a quick google search for windows netsh commands to create the firewall rules for the specific vCenter role/component, but I didn’t find it, so I decided, to save any other lazy admin some time. Below you can find them in the vCenter Server role/component installation order.