Turtini

Write a change plan

Change approvers, owners and admins write plans on **Change Control > Plans**.

1. Select **+ New plan** and name the change.
2. Enter the **job template ID** that makes the change and the **rollback job template ID** that undoes it. A plan cannot be saved without a rollback template.
3. List the **hosts**, one per line, as your inventory names them. Waves are cut in this order.
4. Set the **waves**: a number of servers, a share of the servers, or "the rest", which is cut into waves no larger than your ceiling.
5. Set the **bake window**, the minutes a finished wave runs before it is judged.
6. Add **health checks**: an HTTP check (write {host} where the server's name goes), a port check, Datadog monitors by tag, or a Datadog metric grouped by host.
7. Choose who approves: the start only, or every wave.
8. Select **Save plan**.

In the controller, turn on "prompt on launch" for Limit and Job type in both templates. Change Control limits each job to the wave's servers and runs the rehearsal in check mode; a template that ignores those is refused.

Every save is a new version on the change record.