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

vCO Plug-in

How to use the REST API to Start a Workflow

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

It seems everyday the interest in vCenter Orchestrator (vCO) is growing. I love this because it brings more and more use cases to our attention. One such use case is the need to call vCO workflows via its REST API. In order to keep this article generic, but useful, I will work with the free RESTClient plug-in/add-on for Firefox as the client. The general process here will be similar to what you may need to do from your software or portal to integrate with vCO's REST API.

How to use the SOAPInterceptor to see the SOAP Header and Body

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

On a recent project, I was having trouble figuring out why invoking a SOAP operation kept failing with the vCO SOAP plug-in. The inputs I was providing appeared to be correct and worked just fine with soapUI. This short tutorial will teach you how to use the SOAPInterceptor to display the Header and Body that the SOAP plug-in is sending.

Making vCO Workflow Wrappers

User Rating: 4 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Inactive

A vCO workflow wrapper is a set of workflow tasks that are added at the beginning of a workflow in order to take string values and look up a more complex data type or pre-defining inputs using attributes. You may have done these in the past already in vCO. Some examples would be finding a virtual machine by name or finding an Active Directory user by email address.

If you're running the vCO workflow from within the vCO client or vSphere web client, you probably don't need to worry about this as both of those tools understand the complex data types that come with plugins. On the other hand, if you're calling the vCO workflow from a tool like vCAC, it becomes extremely important to make it so that the vCO workflows only require strings as inputs--meaning that you need to add a vCO workflow wrapper to convert these string values to their more complex data types.

How to run a Perl Script from a vCenter Orchestrator Workflow

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

Read more ...The goal of this tutorial is to create a simple workflow with a single string input that will be passed to a locally hosted Perl script for execution. The results of the script will be returned to vCO and stored in the workflow output. This could come in handy if you have existing systems that already have Perl based management scripts and you wish to incorporate their automation into your Orchestration policies.

Get Supported Hardware Versions from Cluster

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

Read more ...Quite some time ago I had the need to retrieve the supported HW versions for an environment.. I don't remember what the project was, but it wasn't terribly important so I didn't bother digging deeper to figure things out - I just worked around the issue. Last month William Lam posted an article on how to do this with PERL.

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 ;)