Ability to run scripts throughout patching
We can run pre/post scripts, but that is not useful when patching a web farm, cluster, or complex application that needs careful handling. It would be great to have the ability to run scripts throughout patching; pre patching a node, pre/post reboot, post patching a node... this way I can start/restart services, validate functionality after patching a node, or even manage cluster nodes myself throughout a patch cycle.
With pre/post scripts I cannot suspend/resume cluster nodes as I patch through them in a group, nor can I ensure my services are stopped/started as required by my app owners. There is much functionality to be unlocked with this feature alone!
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
Rudolf Dvořák commented
Hello, I already implemented this myself. Using pre-run/post-run scripts.
We have Hyper-V Cluster Managed by System Center Virtual Machine Manager.
I needed to put host to maintenance before upgrading (migrate VMs to other hosts).
So I created runbook, which runs on SCVMM servers and move out all VMs before and after it disable the maintenance on node. If this operations fails, updates do not start. Just a bit of PowerShell.
Justen Hansen commented
I second this - without this functionality, our customers have no choice but to patch manually, and not use Update Management.
I've worked on similar functionality with another solutions, and am happy to discuss this at length. Would be great to have this baked right into Azure as native-functionality.