2022-10-17: Oncall schedule shift 1 hour ahead for Oct11-17

Production Change

Change Summary

Applies for all 3 timezones, after coordinating and getting everyone's agreement, PD schedules were shifted to the following times.

New values:

- APAC: 22:00 - 06:00
- EMEA: 06:00 - 14:00
- AMER: 14:00 - 22:00

With the exception that on Tuesday Oct 11, APAC made 23:00-06:00 (7hrs shift), and on Monday Oct 17, APAC might do 22:00-07:00 (9hrs shift).

Previous values:

- APAC: 23:00 - 07:00
- EMEA: 07:00 - 15:00
- AMER: 15:00 - 23:00

Change Details

1. Services Impacted - ServiceOncall-Tooling
2. Change Technician - @rehab
3. Change Reviewer - @rehab
4. Time tracking - 10 minutes
5. Downtime Component - none

Detailed steps for the change

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - 5m

• For each of the first line escalation schedules in https://gitlab.pagerduty.com/escalation_policies#P7IG7DS (except for Shadow schedules):
  • Edit this schedule
  • Edit under Restrict on-call shifts to specific times
  • Enter the values under New values.
• Create an override as needed for the last/first hour of the day of the change.
• Update the handover report schedule to schedule: 1 5,13,21 * * *.

    ❯ glsh kube use-cluster ops
    ❯ kubectl get cronjobs -n woodhouse
    ❯ kubectl edit cronjob/woodhouse-handover  -n woodhouse

• Merge gitlab-com/gl-infra/k8s-workloads/tanka-deployments!570 (merged).

Rollback

Rollback steps - steps to be taken in the event of a need to rollback this change

Estimated Time to Complete (mins) - 5m

• For each of the first line escalation schedules in https://gitlab.pagerduty.com/escalation_policies#P7IG7DS (except for Shadow schedules):
  • Edit this schedule
  • Edit under Restrict on-call shifts to specific times
  • Enter the values under Previous values.
• Revert gitlab-com/gl-infra/k8s-workloads/tanka-deployments!570 (merged)
  • Merge gitlab-com/gl-infra/k8s-workloads/tanka-deployments!580 (merged).
• Update the handover report schedule to schedule: 1 6,14,22 * * *.

    ❯ glsh kube use-cluster ops
    ❯ kubectl get cronjobs -n woodhouse
    ❯ kubectl edit cronjob/woodhouse-handover  -n woodhouse

Change Reviewer checklist

C4 C3 C2 C1:

• Check if the following applies:
  • The scheduled day and time of execution of the change is appropriate.
  • The change plan is technically accurate.
  • The change plan includes estimated timing values based on previous testing.
  • The change plan includes a viable rollback plan.
  • The specified metrics/monitoring dashboards provide sufficient visibility for the change.

C2 C1:

• Check if the following applies:
  • The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details).
  • The change plan includes success measures for all steps/milestones during the execution.
  • The change adequately minimizes risk within the environment/service.
  • The performance implications of executing the change are well-understood and documented.
  • The specified metrics/monitoring dashboards provide sufficient visibility for the change.
    • If not, is it possible (or necessary) to make changes to observability platforms for added visibility?
  • The change has a primary and secondary SRE with knowledge of the details available during the change window.
  • The labels blocks deployments and/or blocks feature-flags are applied as necessary

Change Technician checklist

• Check if all items below are complete:
  • The change plan is technically accurate.
  • This Change Issue is linked to the appropriate Issue and/or Epic
  • Change has been tested in staging and results noted in a comment on this issue.
  • A dry-run has been conducted and results noted in a comment on this issue.
  • The change execution window respects the Production Change Lock periods.
  • For C1 and C2 change issues, the change event is added to the GitLab Production calendar.
  • For C1 and C2 change issues, the SRE on-call has been informed prior to change being rolled out. (In #production channel, mention @sre-oncall and this issue and await their acknowledgement.)
  • For C1 and C2 change issues, the SRE on-call provided approval with the eoc_approved label on the issue.
  • For C1 and C2 change issues, the Infrastructure Manager provided approval with the manager_approved label on the issue.
  • Release managers have been informed (If needed! Cases include DB change) prior to change being rolled out. (In #production channel, mention @release-managers and this issue and await their acknowledgment.)
  • There are currently no active incidents that are severity1 or severity2
  • If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change.