Critical path, go/no-go times, rollback and live tracking for a change window
List the steps of a change, how long each takes and what each waits for. It works out whether the plan fits your window, which steps decide the finish time, and the go/no-go time for each step: the latest it can be done and still leave time to roll back. During the window, live mode tracks what's done and re-forecasts.
RUNS ENTIRELY IN YOUR BROWSER · YOUR PLAN NEVER LEAVES IT
The window
"Rollback takes" is the fixed part of backing out, such as restoring snapshots and restarting the old services, including checking the rollback worked. Steps that need their own undo (switching DNS back, say) add their undo minutes from the moment they start, since a half-done step needs undoing too. "Plan around people" makes a step wait until the people it needs are free: each name under Who does one step at a time, and no more than the people available work at once. If the end is earlier than the start, the window runs past midnight. With a date and time zone, clock changes inside the window are counted.
The steps
#
Step
Minutes
Waits for
With help (min)
Undo (min)
Who
"Waits for" takes step numbers or names, separated by commas (e.g. 2, 3). "With help" is how long the step would take with a second person. Each name under Who is one person (use Ops 1, Ops 2 for a team), and several names separated by commas means all of them. ⋯ opens the command to run, the check to expect, how many people a step needs (0 for one that's just waiting, like DNS spreading) and whether it can't be undone (dropping a table, say): once that starts, the only way out is forward. Your plan is kept in this browser only.
Does it fit?
+0%
Fit it in the window
Timeline
sets the finish time (critical path)has spare timespare timefinish bywindow endspoint of no returnwaiting for peoplenow · done
Runbook
#
Start
Finish
Step
Who
Spare
Go/no-go by
Actual
Go/no-go by: if a step isn't finished and checked by this time, roll back. After it, either the rest of the plan won't fit or the rollback won't. "5 min short" means the plan as written finishes that step 5 minutes after its go/no-go time, so that time has to be made up by then.
Log
Starts, finishes, failed checks, changed times and every change in the live status are written here as they happen. Add decisions and anything else worth remembering. Like the plan, it's kept in this browser and goes with the saved plan file; anyone with this browser can change it.
Plan versus actual
#
Step
Planned
Actual
Took
Finished
Go/no-go
Planned is the plan as it stood when live mode was started. A failed check counts as the step's finish.