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.

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
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.

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.

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.

This category of articles will be dedicated to Home Labs :)

General facts about Joomla!