VMware vCenter Orchestrator (vCO) Click Below for Plug-ins:

vCO Plug-in

How to use the REST API to Resume a Failed Workflow

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

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.

Dynamic Types tutorial : Implement your own Twitter plug-in without any scripting

User Rating: 4 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Inactive
In a previous article I have explained how the vCO dynamic Types allow to simplify the development of vCO plug-ins and how these are leveraged by VMware vCloud Automation Center XaaS. It is now time to experiment with creating a plugin with leveraging the Dynamic Types plug-in generator package.

Warning : You can do it without Java development experience and without having to write a single line of scripting !

Enabling VMware vCloud Automation Center XaaS with vCO dynamic types

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

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.

How To Configure vCAC's Embedded vCO To Allow Domain Account Login

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

If you're reading this article, it may be because you have installed vCloud Automation Center (vCAC) and are interested in using an account other than This email address is being protected from spambots. You need JavaScript enabled to view it. to login to the embedded vCenter Orchestrator (vCO) server. By default, the vCO Server uses a "vcoadmins" group in the "vsphere.local" domain provided by the SSO server that vCAC was configured to use. This short tutorial will step you through a pretty basic configuration where I have just deployed a vCAC 6.x appliance and wish to use my domain account for vCO login.
NOTE: Article updated Jan 26, 2015

VMware released vCenter Orchestrator 5.5.1

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active
This week VMware released vCenter Orchestrator 5.5.1. While this is not a major new release it contains a lot of new features focusing on making vCO content development easier. Also important is a list of deprecated features.

How to allow the vCO Appliance to write files to a Windows CIFS share

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active
A frequent question around vCenter Orchestrator is: Can I read/write to shared folders? The answer is always yes, but the documentation may be difficult to find - especially when you are referring to a Windows share - aka CIFS in samba and *nix mounting terminology. Read on to learn EXACTLY what you need to do to allow your vCO server to read/write to a Windows Share!

NUC Lab Kit

Below are my thoughts for a vSAN nuc lab. Since I already have cables, not including them here. I ordered (and received by Nov 30, 2016)
3 x nuc, 3 x 32GB Crucial mem, 3 x Toshiba NVMe drive, 3 x Startech USB to GB NIC, and 3 x Crucial 1TB SSD. I've also been very happy with my Cisco SG300-10 so I bought one more since my existing one only has one port available. Each of the items listed here are linked below - all were purchased using the provided links below.
single NIC (See this post for details on using the USB -> GB NIC item listed below

I stayed with the i5 for the power consumption and form factor vs. the i7 Skull Canyon ;)