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

vCO Plug-in

Leveraging vCenter 6 vAPI REST endpoint

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active
vCenter 6 has introduced an important new feature for anyone interested in Automation and integration : a REST based endpoint providing access to some of the recent functionality such as the tagging service, the content library and transfer service : It is called  "VMware vCloud Suite SDK" and codenamed vAPI. In addition to the REST API it provides language bindings for Java, Python, .NET, Perl and Ruby. If you want to know more about vAPI you can read the blog article I wrote on the VMware CTO Ambassadors blog.
The following article is an introduction to using the vAPI REST Endpoint from vRealize Orchestrator REST plug-in. The concepts in this article may be useful even if you plan to consume the REST service with any REST client.

Synchronize Presentation Settings from embedded workflow

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active
VMware's vRealize Orchestrator (vRO) is all about modular, reusable components. Many times you wish to call an existing workflow from your own custom workflow but don't want to manually re-create all the different presentation settings. It's not such a big task if there are only one or two workflows, but how about when there are 10+ ? Good news is that you don't have to! This quick little video demonstrates how to Synchronize the Presentation of an embedded workflow to your own.

Postman + vRO = HTTP-REST Plug-in Operations

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

In a previous article, I stepped through the process of working with vRealize Orchestrator's (vRO) REST API using the RestClient add-on for FireFox. This was before I was introduced to my new favorite REST client: POSTMAN! (@postmanclient) In this article, I'll provide a little detail on an approach you can use to improve your work with REST APIs and consuming them with Orchestrator's REST plug-in. Throughout the article, I will use a FreeNAS 9.3.x Virtual Appliance as my target endpoint since it is freely available, quick to setup, and has nice API documentation. Please note that the technique described here can be used for any API that Postman can access!

Log plug-ins HTTP communications

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active
A lot of the Orchestrator plug-ins use the Apache HTTP client to communicate with the target hosts. You may want to log the HTTP communications for many purposes:
  • Understanding how vCO does the API calls
  • Troubleshoot a problem with a target host
  • Re-engineering an existing call with capturing it, changing it as you like and use it via the REST or SOAP plug-in
  • Brag you have found an "Onyx" like functionality for most Orchestrated products wink

This article will guide you on how to log these calls to a file.

Plug-in Generator v2 advanced techniques

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active
In previous tutorials we created inventory object types, their children objects, workflows to operate these that we packaged for our end users.
In this tutorial we are going to create an orchestrator plug-in to list vCO / vRO workflows ! You may wonder why doing so ?
This is a good use case for leveraging some of the more advanced features of the plug-in generator v2 to handle complex REST APIs and improving performance when needed.

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