Yesterday I finished reading one of the Packt books I actually enjoyed (which is only a handful to be honest, usually the standard is not too high).
I had to deal with a deployment issue in vRealize Automation yesterday that also included one issue to be the weirdest corner case I have seen so far.
All deployments for any VMs using no vRealize Orchestrator workflow stubs were successful. But let’s be honest, that is pretty boring and doesn’t cover most customers use cases, which means most customers will be using the provided stubs to actually step into the machine life cycle and modify deployment and destruction of VMs using workflows and scripts.
— Vladan (@vladan) 9. März 2015
This came up on twitter today. While this might result in a fast turnaround time for getting the immediate issue resolved it won’t show you the root cause of the hang/unresponsive VM, and let’s be honest normally that is what we are interested in, right? (There will be exceptions to that, if your mission critical and revenue generating system is in that state you probably want to restart it as fast as possible and then go back to the white board and redesign that single point of failure as soon as possible).