VRA

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 16/3/2016
VMware KB2140539 where requesting an XaaS (vRealize Orchestrator) blueprint fails with: Failed to retrieve form from provider The KB describes it occuring when “more than one VMware vRealize Orchestrator instance is configured for different tenants”. The issue I faced is not the same - in my case, I had the system default tenant configured to use the embedded vRO, and the customer tenant configured to use the system default (which would be the embedded vRO!
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.
Written by Sam McGeown on 10/11/2015
Published under Community, VMware and vRealize Automation
I use mind maps quite a lot for study, I find the visual representation of info makes it a lot easier for me to remember! Below is a mind map I created for learning the roles in vRealize Automation, which I used during my presentation for #vBrownBag on VCP6-CMA objective 2. You can download a PDF version here: vRealize Automation Roles Mind Map
Written by Sam McGeown on 14/10/2015
Published under VMware and vRealize Automation
@vaficionado) – if that list of names doesn’t fill you with confidence for vRA.Next, then I suggest you follow them on twitter and trust me that it’s a crack team!   So, my highlights: Completely automated deployment…almost. The deployment of appliances and installation of IaaS components and pre-requisites will be wizard driven, the Window Servers will need to exist and have an agent installed, and the MSSQL server will also need to be installed.
Written by Sam McGeown on 29/9/2015
Published under VMware, vRealize Automation and vSphere
As a vExpert, I am blessed to get 1000 CPU hours access to Ravello’s awesome platform and recently I’ve been playing with the AutoLab deployments tailored for Ravello. If you’re unfamiliar with Ravello’s offering (where have you been?!) then it’s basically a custom hypervisor (HVX) running on either AWS or Google Cloud that allows you to run nested environments on those platforms. I did say it’s awesome. As an avid home-lab enthusiast Ravello initially felt weird, but having used it for a while I can definitely see the potential to augment, and in some cases completely replace the home lab.
Written by Simon Eady on 21/9/2015
Published under vRealize Automation
Recently the team I am working with came across an interesting bug/issue with actions missing from deployed VMs. We had checked and double checked the entitlements yet the actions that should be available to the end-user/customer were not listed. Everything appeared to point to a permissions issue until one of the team members noticed something with regards to blueprints in the catalog. Before I continue with what we observed and how we “fixed” it please bear in mind the blueprints were created programmatically.
Written by Sam McGeown on 19/8/2015
[<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” . Out-of-the-box monitors allow us to detect if the port we are load balancing is open, but don’t determine whether the service on that port is functioning correctly. Important: None of these monitors should be created until vRealize has been fully installed - doing these as you go along will result in installation failures. For example, if you create the monitor on the IaaS web service before the DEM roles are installed, the web service will always be down because it’s waiting for a DEM role.
Written by Sam McGeown on 14/8/2015
Published under VMware and vRealize Automation
Now that the prerequisites for the IaaS layer have been completed, it’s time to move on to the actual installation of the IaaS components, starting with the database. We then move onto the first Web server, which also imports the ModelManagerData configuration to the database, populating the database with all of the info the IaaS layer needs out of the box. We then install the second Web server before moving on to the active Manager server.
Written by Sam McGeown on 14/8/2015
Published under VMware and vRealize Automation
One of the trickiest parts of deploying vRealize Automation is the IaaS layer - people sometimes look at me like I’m a crazy person when I say that, normally because they’ve deployed a PoC or small deployment with just a single IaaS server. Add in 5 more servers, some load balancers, certificates, a distributed setup and MSDTC to the mix and you have a huge potential for pain! If you’ve followed my previous posts, you’ll see know that I’ve got a HA Platform Services Controller configured, and a HA vRealize Appliance cluster configured with Postgres replication - all good so far.