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 Future article will cover the following topic:

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 simplify it by returning the total number of addresses in the range.

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. Introduction Let’s build a simple Dynamic Types plug-in around our SQL Table that we created in our previous article.

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.

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.

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. The first part of the article explains the different options available to automate F5 including the F5 plug-in for vCO, PowerShell, the big IP CLI, the SOAP and REST APIs and give an overview of the solution.

Hello all you end user compute admins! If you've been waiting for a vCO plug-in for your Horizon environment, your wait is over. Join Aaron Black in this "Getting Started with vCenter Orchestrator Horizon Plug In" video. In order to get the plug-in, you must be licensed for Horizon 6.0 Enterprise. For a quick link to the download (login required at VMware's site), click Links -> Plug Ins, then scroll down to the "

Last year I have created an extensibility package to simplify and automate the steps necessary to extend the vCAC IaaS lifecycle process with calling out vCO workflows. While this was mainly aimed at accelerating Proof of Concepts it has been since then broadly adopted in production environments. Since vCAC 6.0 it is part of the product and available for vCAC 5.2 as a separate download. Since this is now becoming a very hot topic I am including here a very useful extensibility introduction video that was released by my colleagues from tech marketing almost three months ago.

As noted in a previous article, this page shows how many workflows and actions become available on a vCO 5.5.1 server after installing only the officially released Plug-ins, Flings, and Packages (Note that there are hundreds of packages containing thousands of workflows onvarious blogs and in the Orchestrator Communities.) The target vCO 5.5.1 (5.5.1.1617127) Server has: 1083 Workflows and 2069 Actions. Workflows (1083) categoryNamenameversiondescription Addresses Allocate Address 0.0.1 Acquires an Elastic IP address.

This page was generated using a workflow to access the REST API of a freshly deployed VMware vCenter Orchestrator (vCO) 5.5.1 GA Virtual Appliance. The results indicate a total of: 394 Workflows and 388 Actions. Please note that for each Plug-in you install, additional Library Workflows and Actions will be available. I've provided ahandy link page for the plug-ins that I'm aware of here on this blog.. as noted on that page, the official repository where VMware and Partners should be submitting their plug-ins is the VMware Solution Exchange.