VRA7

Written by Sam McGeown on 19/12/2016
One of the cool new features released with vRealize Automation 7.2 was the integration of VMware Admiral (container management) into the product, and recently VMware made version 1 of vSphere Integrated Containers generally available (GA), so I thought it was time I started playing around with the two. In this article I’m going to cover deploying VIC to my vSphere environment and then adding that host to the vRA 7.
Written by Sam McGeown on 18/11/2016
Published under Cloud, VMware and vRealize Automation
Recently I’ve been working on some ideas in my lab to leverage the AWS endpoint on vRealize Automation. One of the things I needed to get working was getting Software Components working on my AWS deployed instances. The diagram to the right shows my end-stage network - the instance deployed by vRA into AWS should be in a private subnet in my VPC, and should use my local lab DNS server and be able to access my vRA instance.
Written by Sam McGeown on 30/3/2016
<img class=“alignright size-thumbnail wp-image-6186” src=“/wp-content/uploads/2015/07/vRA-Product-Icon-Mac_0-150x150.png” alt=“vRA” width=“150” height=“150” - a properties object. I wanted to create a workflow that I could enable to log all of the keys, values and types of the properties object for each stage of the vRA7 MachineProvisioning workflows, and create a reference for myself on the payload for each stage. To do this I created a new workflow “debugProperties” and added an input variable called “payload”, type Properties.
Written by Sam McGeown on 9/3/2016
The new Event Broker service in vRA7 is one of the most exciting features of this latest release, the possibilities for extensibility are huge. At this point it time you can still use the old method of using workflow stubs to customise machine lifecycle events, but at some point in the future this will be deprecated and the Event Broker will be the only way to extend. With this in mind, I wanted to use the Event Broker to do something that I am asked on almost every customer engagement - custom hostnames beyond what the Machine Prefixes mechanism can do.