Before anyone gets in a huff, I’m not suggesting that a key part of VMware’s automation, orchestration and cloud functionality be consigned to the bin. This is about the name. It was Q3 / Q4 last year (2014) that VMware announced the changes to its product names. A whole year ago! Of course, it can take time for a change to take effect, particularly when any of the following are a factor: Older projects and environments using older versions of the products that contain original branding Document, diagram and presentation re-use where the older names are used Investment in any other IP or collateral Ingrained habits, especially if you’ve been using these products for years But by now “vCO” should be a thing of the past. That’s not its name anymore. I won’t be removing the tag from my blog […]
Such a minor update (from 5.5.1), why should I bother to write about this? Well, for two reasons really. Complete support of Dynamic Types. I’ve been doing some work with these on a current project and the potential is pretty fantastic. vCenter Server plugin enhancement. The property collector is now used to return vCenter Server object properties instead of the inventory service. If you follow the Orchestrator communities forum, you’ll probably already know that the inventory service cause quite a few people some problems. If you want to know more about Dynamic types, look at this blog post and this example on the vCOTeam blog site. Download vCO 5.5.2 here. Release notes are here.
If you’re starting to get your hands dirty with NSX and want to automate some operations using vCenter Orchestrator (vCO), there’s now a plugin for it that’s been released into the community by Christophe Decanini (who writes on the vCOTeam blog and works for VMware). It’s not a traditional plugin for vCenter Orchestrator in the same way that there are plugins for vCenter / vCAC / Infoblox etc. Instead it’s built on the Dynamic Types plugin that was launched with version 5.5 Update 1 of vCO. The goal of the plugin is to create the ability to offer NSX “as-a-service” operations as catalog items within vCAC. The creation and manipulation of security groups and policies along with the ability to associate VMs with these objects can all be offered as options for users to select within the vCAC catalog using this […]