I’ve decided that whilst it’s great to provision a Kubernetes blueprint with a standard network overlay to the vRealize Automation catalog, offering one that leverages NSX-T is even better. So a few days ago I started creating Continue reading
A few months ago a client asked me to create an NSX application load-balancer programmatically, and then make it available to their vRealize Automation consumers in through the self-service catalog. In building-block fashion, they requested that this wasn’t a composite blueprint, but rather through XaaS. While the former would definitely take less time, the latter was not that difficult either once I got started. Continue reading
Really short post, but this might stop you from going bat**** crazy…
Recently I needed to create some NSX Distributed Firewall Rules in vRealize Orchestrator for a complex micro-segmentation project. The layer 3 section already existed in NSX, I just needed to create the rules on the fly using the REST API. Continue reading
Recently, Microsot announced the GA release of their Public Cloud Kubernetes offering – Azure Kubernetes Service (AKS). Now DevOps practioners have the ability to stand-up k8s clusters in the cloud and integrate workloads with their existing CI/CD pipelines, without having to go to another provider. Continue reading
vRealize Automation brings a raft of benefits to an organisation. The biggest of these is the ability to enable users to consume complex services without having to rely on the corporate IT department. An example of this is the ability to provision a Docker endpoint, in the form of a vSphere Integrated Containers Virtual Container Host, for developers to deploy containers against. Continue reading
This will quite possibly be the shortest, but yet most useful, posts on vRealize Automation you’ve ever read…
If you regularly develop software components for vRA, you’ve undoubtedly discovered that if for some reason a deployment fails, the machine is automatically deleted within a couple of minutes. This is frustrating as it gives you no time to debug why it failed, as all evidence is deleted with the machine.
Thankfully, Sam McGeown shared the answer a couple of weeks back:
So there you have it. One custom property attached to your blueprint will enable you to see why your deployment failed.
This is one of those things I wished I’da known ages ago!
Occasionally you come across an issue which bugs the hell out of you. Despite
wanting needing to resolve it badly, you know it’s going to be a case of trial and error, and it’s going to consume a lot of your time. The other day I came across one these issues, and just as I suspected, the majority of an evening would be spent trying to resolve it. Continue reading
Earlier this week I had an issue in vRealize Automation where logged-on usernames were being displayed incorrectly. At first I hoped it was just a cosmetic issue, but as I delved deeper it appeared to be a little more than that, and could be an issue for both users and developers.
On 20 June 2017 VMware released the latest version of Horizon View – 7.2. Whilst this release contained a number of product features and enhancements, one of the ones most helpful to teams supporting VDI implementations in the new Helpdesk Tool Continue reading