Remove deprecated Digital Ocean instance of design.gitlab.com
C4
Production Change - Criticality 4This is the production change to implement https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/8707
Change Objective | Describe the objective of the change |
---|---|
Change Type | Shut Down |
Services Impacted | design.GitLab.com |
Change Team Members | @devin |
Change Severity | C4 |
Change Reviewer or tested in staging | A colleague who will review the change or evidence the change was tested on staging environment |
Dry-run output | N/A |
Due Date | 2020-03-10 and 2020-03-16 |
Time tracking | To estimate and record times associated with changes ( including a possible rollback ) |
Detailed steps for the change
- Now that the app has moved to Kubernetes, shut down the obsolete running
design.GitLab.com
instance in DigitalOceanGitLab Prod
console - Wait a few days to validate no ill effects from anything the app may still be pulling from the old instance
- Delete the stopped instance
- Remove the configuration from Chef
Rollback steps
- If anything comes up when the old instance is shut down, we can simply power on the
design.GitLab.com
instance in DigitalOceanGitLab Prod
console
Changes checklist
-
Detailed steps and rollback steps have been filled prior to commencing work -
Person on-call has been informed prior to change being rolled out -
Shut down design.GitLab.com
instance in DigitalOceanGitLab Prod
console -
Verify no immediate alerts -
Verify new site is up and all functionality is there -
Wait at least a week -
Remove the shut down instance -
Remove the chef configuration -
Close out https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/8707
Edited by Devin Sylva