Patch order with dependencies
Create patch groups that can run either parallel or dependent on other patch groups. Ensuring certain servers do no patch at the same time or are being patched in a specified order rather than parallel.
This is similar to cluster-aware updates but slightly different. We will keep an eye on this to gauge interest and prioritize accordingly.
Justin Galbraith commented
I would very much appreciate this feature as it would provide granular control and enable single schedules for complex applications.
Pirmin Felber commented
An ability to model update sequences would help us a lot. Currently we're considering to build this ourselves by either
- Have a dedicated runbook that automatically schedule deployments (schedule update wave 2 after update wave 1 has been completed).
- Or use a Pre-Script that pauses update of wave 2 as long as wave 2 has not been completed.
However both implementations makes it hard to narrow down update windows (espcially if there are three or groups in update sequence).
Rob silver commented
Agree this would be useful, it would be great to control the level of parallelism for applying patches
Justen Hansen commented
This would be useful for web farms, tiered applications, or even apps that arent clusters but require HA or a particular server maintenance order (WEB01 after DB01).