Delete the production gemnasium Cloud SQL database instance
Production Change
Change Summary
Delete the production gemnasium Cloud SQL database instance.
Part of: https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/16323
Change Details
- Services Impacted - ServiceGemnasium
- Change Technician - @nnelson
- Change Reviewer - @bshah11
-
Time tracking -
5 minutes -
Downtime Component -
No downtime
Detailed steps for the change
Change Steps - steps to take to execute the change
Estimated Time to Complete - 5 minutes
-
Set label changein-progress /label ~change::in-progress -
In a web browser, navigate to: https://console.cloud.google.com/sql/instances?project=gemnasium-production -
Confirm there are no existing connections or other activity: https://console.cloud.google.com/sql/instances/db/system-insights?project=gemnasium-production -
Using the "Actions" sub-menu at the very right-end of the dbCloud SQL instance row entry, select theDeletemenu-item, and complete any remaining confirmation steps. -
Verify that the Cloud SQL instance was deleted. -
Set label changecomplete /label ~change::complete
Rollback
Rollback steps - steps to be taken in the event of a need to rollback this change
Estimated Time to Complete - 0 minutes
This won't be getting undone. A new instance would have to be created and its contents restored the last backup export.
Monitoring
Key metrics to observe
The service is deleted, so this is not necessary.
Change Reviewer checklist
-
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.
-
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-oncalland 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-managersand 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.
Edited by Nels Nelson