Draft: Starting language for DB switchover events
Why is this change being made?
Related to current work going on for the Patroni clusters, we have 2 events to clarify communications and maintenance window needs. The first bullet point added is meant to clarify that we should communicate internally about no/little interruption maintenance events.
Example 1: with the PG Hardware upgrades, we need to switch the primary DB Example 2: The upgrade to PG14 is planned to take zero downtime, but is a significant Criticality 1 change.
In both cases, the team is looking for guidance if they should follow the communicating a change guide or if we should adapt it.
This MR proposes that we should still communicate internally, but not post a maintenance window.
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.