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

vCO Plug-in

How to use Python to start an Orchestrator Workflow

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

In a previous article, I taught you how to explore and use the REST API to start a Workflow using a generic browser based REST Client. In this article, I will provide a Python based example of running the "Create a Record" workflow that was created in Part 2 of my SQL Plug-in Dynamic Types Simple CMDB for vCAC article. Since I'm not even close to being proficient with Python, this will be a very short article! You may download the script in this article from my vroClientScripts Repository on GitHub. Be sure to check out that repo because my colleague has provided a better written Python module there for calling workflows.

SQL Plug-in + DynamicTypes = Simple CMDB for vCAC - Part 3

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

Welcome back! This is the third article of a multi-part series that steps you through the process of exposing our workflows from the last article to vRealize Automation's (vRA) Advanced Service Designer (ASD).

Introduction

This third article will cover the following topics:

  • How to add the simple CMDB to vRealize Automation's Advanced Service Designer
  • Add a Day 2 operation to delete an Asset from our table

Get Addresses in Range

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive
vRealize Orchestrator (vRO) is frequently used with Network related automation which may involve working with IP Addresses. From an end user perspective, it is nice to specify a range of addresses such as 192.168.1.1-192.168.1.100 rather than having to specify all addresses. I found some simple Javascript in this Converting IP Addresses article that is easily adapted to vRO. You can use the code included in this article to either return an array of addresses in the range specified, or simply it by returning the total number of addresses in the range. Either way, I hope you find this code helpful in your workflows.

SQL Plug-in + DynamicTypes = Simple CMDB for vCAC - Part 2

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

Welcome back! This is the second article of a multi-part series that steps you through the process of mapping a SQL table into vRealize Orchestrator, building out a DynamicTypes plug-in inventory based on that table, then exposing it to vRealize Automation's Advanced Service Designer (ASD). In the first article, we got our database table mapped using the SQL Plug-in and generated some CRUD workflows.

SQL Plug-in + DynamicTypes = Simple CMDB for vCAC - Part 1

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

This multi-part series will step you through the process of mapping a Microsoft SQL Server table into vRealize Orchestrator, building out a DynamicTypes plug-in inventory based on that table (using my workflow package), then exposing it to vRealize Automation's Advanced Service Designer (ASD).

Introduction

vRealize Automation (vRA) features an Advanced Service Designer (ASD) that allows for you to offer nearly anything as a service (XaaS). In order to take advantage of that feature, it requires a vRealize Orchestrator (vRO) Inventory object. This means you must have a plug-in that provides such an inventory. In the past, this meant Java skills to build out a plug-in. This, fortunately, is no longer the case with the Dynamic Types plug-in. We touched on this plug-in in the past with regards to using the HTTP-REST plug-in. This article will take a different approach in that we will use the SQL Plug-in to provide our back-end service - a mini CMDB consisting of Server names and IPs.

Dynamic Input Values Based on other Inputs

User Rating: 3 / 5

Star ActiveStar ActiveStar ActiveStar InactiveStar Inactive

A frequent requirement when performing orchestration tasks is to have input fields interdependent. For example, if I input XYZ into the first input, I want the second input to be relevant to XYZ. In the past, I have frequently done such workflows where you select a Datacenter for the first input, then the second input would present a list of Datastores (or VMs or Clusters or Hosts). In this tutorial, I'm going to do something a little different. The first input of this demo workflow will be a string and the second will be an AD:User object chosen from a list of objects that were found in Active Directory based on the first input.

Extend Automation Center with F5 AFM using vCO + Dynamic Types

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive
My colleague, Chris Slater at defined by software has published an article on how to extend VMware Automation Center (vCAC) with F5 firewall functionality. I usually do not cross post articles but this one is worth mentioning since it is a real world example on how to leverage vCAC + vCO + Dynamic Types + third party API.

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