On the VMware blog I have explained how vRealize Automation Anything as a Service (XaaS) work with Orchestrator and how a vRO plug-in works. In this tutorial I will walk you through how I managed to implement Microsoft DNS as a service I used for the screenshot examples on that blog including: The Microsoft DNS dynamic types plug-in DNS record as a service in vRA DNS record as a blueprint component This is the first public tutorial on how to create a Dynamic Types plug-in from scratch and the overall methodology used applies to other integrations.
In a previous article, I taught you How to retrieve a script Resource from vRO via curl. That can be helpful to some people, but how about updating that script? Easy! Read on… This is a super short post since all the tough details were already outlined in the article linked above. So, assuming you already know the ID and name of the script you wish to update, all you need to do is run the following curl command:
I recently spent time with a customer doing a vRO workshop with them. During the course of the workshop, I was asked how you could retrieve a script that had been stored as a resource element on a vRO server using curl. Well, I had never done that before so I set out to figure it out and was able to provide the solution before I left! Throughout this article, I will be using a vRA 7.
I recently came across a thread asking about how to disable Storage I/O Statistics Collection using PowerCLI. The thread referenced this article by Michael Webster: Disable SIOC IO Metrics Collection For Auto Tiering Storage Systems. In one of the comments, someone asked about using PowerCLI.. Unfortunately there was no answer there so I thought - I might be able to figure this out! With regards to checking that box, I can’t say whether it’s a good idea or not, my purpose here was just to illustrate how to do it via PowerCLI and vRO.
Two years ago, I wrote a similar article around vCAC’s embedded vCO but a lot has changed since then so those older steps no longer apply. This brief article will quickly walk you through the steps required to allow vRealize Automation 7.0/7.1/7.2’s embedded vRealize Orchestrator to allow Active Directory Domain accounts login to the vRO Client. Pre-Requisites This article assumes the following: vRealize Automation 7.0-7.2 is installed and configured (NOTE: This has not been tested with 7.
Each time vRealize Orchestrator (vRO) runs a workflow, a token (workflow execution) is added beneath the workflow in the vRO client. By default vRO will keep up to 100 of these tokens! This may be a slight annoyance to people who are only interested in the last 5-20 runs. This article will shed some light on the configuration options you have available to you. Tired of seeing too many workflow tokens?
I am working on a project where I need to apply live, permanent networking configuration changes to Linux VMs that may not even have a network configured in the first place. To do so I am leveraging: vSphere guest operations allowing to run commands in the guest OS even if it is not networked yet. NetworkManager / nmcli which provides a command line way to get and set a broad set of network configurations that can be applied immediately and permanently .
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.
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.
Recently I saw a pair of articles by @RoeyAzroel on vRO XML & JSON Gotcha! - Part 1 and Part 2. This reminded me that I had some sample code that I refer to when working with json as well so figured I would share here. Be sure you know about the JSON object and its .parse and .stringify methods since they do not appear anywhere in the Orchestrator’s API explorer or documentation.