Patch Window Rollout Waves
Run approved changes as pilot and broad waves across the fleet, with a pause threshold and a live link to each change record.
These images are illustrations of the concept, not screenshots of the actual product.
Overview
Patch Window Rollout Waves is a VibeControls concept for IT operations teams and managed service providers who patch hundreds of Linux servers inside a fixed change window. Approved changes are split into ordered waves, pilot, early and broad, and each wave is designed to run a pre-approved Vibe Deck action or a Vibe Calendar scheduled task on servers where a VibeControls agent is installed.
In IT and managed services, a patch night is judged the next morning by the change record, and the record rarely matches what happened. Servers fail and are rolled back, a few are skipped because someone changed them by hand, and the notes are rebuilt from chat. For an MSP the problem multiplies, because every client has its own change request and its own approvers.
The desktop illustration shows an MSP operations view across nine sample client workspaces. The header gives the window, the time remaining and a changes-approved pill, with Pause wave, Resume and Write results to changes buttons. A stepper tracks three waves: a verified pilot, an early wave in progress and a queued broad wave. A pause rule card states that the next wave stops once failures pass a set percentage, with a gauge showing the current rate. The server table gives each server's client, the deck action it runs, a status such as verified, rebooting, failed and rolled back, excluded for drift or queued, and its reboot state and duration. The phone illustration carries the same window in compact form, so the next wave can be approved or held away from a desk.
Two other Burdenoff products sit on either side of the run. A card links the window to AssetHandler change requests, one per client with its own approvals, and wave results are designed to flow back to each record so it matches what actually happened. Servers with open AdapterCloud drift records are designed to be flagged before the window so they can be excluded; in the sample, a note on an excluded server explains that a firewall rule was changed by hand. Every command is meant to land in the VibeControls audit log.
What this concept shows
- Ordered pilot, early and broad waves with server counts and verified, in-progress and queued states
- A window header with the time remaining and a changes-approved status
- A pause rule that holds the next wave when failures pass a set percentage, with a gauge of the current failure rate
- Per-server status from queued and rebooting to verified, failed and rolled back, or excluded for drift
- A linked card counting the AssetHandler change requests behind the window and how many are approved
- AdapterCloud drift flagged on a server before it is patched, with the reason shown on its row
- Pause wave, Resume and Write results to changes controls for the operator
- A phone view to approve or hold the next wave, with exceptions listed beneath
How it works
- Open the patch window once each client's linked AssetHandler change request is approved.
- Review servers flagged with AdapterCloud drift and exclude them instead of patching them mid-drift.
- Run the pilot wave with its pre-approved deck action and confirm every server is verified.
- Watch the early wave's per-server status while the pause rule compares failures with its threshold.
- Approve or hold the broad wave from a phone after checking the listed exceptions.
- Write the wave results back to each client's change record so it matches what was done.
Who it's for
- IT operations and infrastructure engineers
- Managed service provider operations leads
- Change managers and change approvers
- Site reliability engineers
- On-call engineers approving work away from a desk
Illustrations
2 illustrations of this concept. Select one to view it full size.
Patch Waves Across Client Servers
This illustration shows a patch window for a critical advisory in an MSP operations view spanning nine sample client workspaces. Under the title sit the window hours, the time remaining and a changes-approved pill, with Pause wave, Resume and a highlighted Write results to changes button on the right. A card links the window to AssetHandler changes, one per client and all approved in the sample, with an Open changes button. A Pause rule card states that the next wave pauses once failures pass a threshold, beside a gauge of the current rate. A stepper shows a verified pilot wave, an early wave in progress and a queued broad wave. The table lists servers with their client, a deck action that applies a patch set, a status badge for verified, rebooting, failed and rolled back, excluded for drift or queued, the reboot state and a duration. A note on the excluded server attributes it to AdapterCloud drift from a firewall rule changed by hand.
Approving the Next Wave on a Phone
This illustration shows the patch window on a phone, under the VibeControls Home tab. The header gives the number of linked changes and the time left, with a changes-approved pill. A large progress ring counts the servers finished in the running second wave. Three stacked cards follow: the pilot wave fully verified with a check mark, the early wave in progress with a progress bar and its failure rate against the limit, and the broad wave waiting for approval. A highlighted Needs you card asks the viewer to approve the third wave across a sample set of servers and clients, with Approve wave and Hold buttons. An Exceptions list names one server that failed and was rolled back and one excluded for drift, each marked with a colored dot. A chip notes that results sync to each AssetHandler change record, above a tab bar with Home, Project, AI and Settings.
Topics
- staged patch rollout
- patch management waves
- change window automation
- MSP patch management
- Linux server patching
- pilot and broad deployment rings
- patch failure threshold
- change request results
- configuration drift before patching
- mobile change approval
- fleet patch orchestration
Related concepts
Actions and One-Click Ops Decks
Turn commands, scripts and webhooks into reusable actions, then pin them to one-click decks your team and on-call rotation can run.
3 illustrations
Scheduled Jobs and Calendar
See every scheduled job across your agents on one calendar, then open any job to check its schedule, run history and logs.
2 illustrations
Usage Analytics and Audit Trail
Count what the fleet did over any period, then drill into a searchable record of who did what, where and with what result.
2 illustrations
Agent Fleet and Agent Detail
Browse every agent in the workspace as filterable cards, then open one to inspect its connectivity, plugins, sessions and logs.
2 illustrations
Part of an industry solution
This concept appears in a cross-product solution on burdenoff.com — see how it works alongside other Burdenoff products to solve a problem in that industry.
