I've built up and tore down my vRealize Automation lab several times in the past month in order to familiarize myself with some of the pitfalls. As a result, I've run into some installation gotchas that I noted down, and decided to post them here.
VMware vRealize Automation makes it easy for us to provide our end users with the ability to request and manage their own virtual machines using a “self-service” portal. With very little configuration required, we can add vSphere virtual machine templates to a vRA service catalog for users to consume. vRA can then handle the request management for new virtual machines and when approved by the appropriate approvers, even provision the new VMs by cloning the template.
Since moving to Lincolnshire in August 2014 and whist still working on customer sites in London the majority of the time, I found myself doing a lot of train journeys to and from London. I also started to realise that due to the workload I’ve been facing this year, sometimes juggling up to 5 customer engagements at once, that I very rarely have a few minutes during the day to actually read up on product documentation or anything else that is not directly related to the task at hand.
As we all know, things are moving very rapidly in our industry, more so now than ever before and the hypervisor and features that were once regarded as “awesome” back in the VMware ESX 3 or even 4 days now pale into insignificance when compared to the cast number of features and capabilities that lies simply within the ESXi 5.5 hypervisor. Then, when considering the entire vCloud suite of products and how they interact with each other and the hypervisor, it doesn’t take much to work out that things are becoming more and more complex with every release.