Wednesday Tidbit: Stop failed vRealize Automation software deployments from auto-deleting

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!

“Invalid IP Address input” error when requesting a vRA blueprint via Code Stream

20161114-1The other day I successfully demonstrated the power of Code Stream at the UK North-West VMUG. The Management Pack for IT DevOps (codenamed “Houdini”) migrated blueprints between Development and Production, and at the end of the session I built a pipeline for deploying a WordPress application in development. Even though the audience wouldn’t have Continue reading

Deploying MySQL on CentOS 7 for vRealize Automation blueprints

20161114-1Over the weekend I began preparing a multi-tier application blueprint in vRealize Automation for an upcoming talk at the UK North-West VMUG. Rather than re-invent the wheel (and more importantly because I’m lazy), I decided to re-use a blueprint from the VMware {code} site. The one I’d chosen used MySQL, which for a quick and dirty live demo is ideal.  Continue reading