- Published: Friday, 20 June 2014 19:08
- Written by Burke Azbill
One of the relatively new 5.x features of vCenter Orchestrator (vCO) is the ability to Enable a workflow to resume on failure. Essentially, this means that a workflow could fail 1/2 or 3/4 the way through and you could go and tell vCO to resume that workflow, perhaps after fixing whatever issue caused it to fail in the first place, rather than start a fresh instance of the workflow.
vCO has again been extended with a new plug-in an updates of existing plug-ins.
You may have noticed that the vCO 5.5.1 release notes are listing a new feature called "Dynamic Types"
"Workflow developers are now able to explore the new Dynamic Types which currently is being shipped with Beta quality. They can easily extend vCenter Orchestrator plug-ins by adding their custom types accessible from the scripting API. New types become available in the inventory right after creation and they could be directly leveraged from the vCAC ASD context as part of the cloud provisioning process and XaaS definition."
This article explores how the Dynamic Types can be leveraged to create your own mini vCO plug-ins without having any Java development skills.
NOTE: Article updated Jan 26, 2015