[PRE] Remove old NFS environments
Production Change
The old NFS environments are not in use and we would like to clean up as per this issue
Change Summary
Provide a high-level summary of the change and its purpose.
Change Details
- Services Impacted - ServicePraefect ServiceGitaly
- Change Technician - @swainaina
- Change Reviewer - DRI for the review of this change
- Time tracking - 1 hour
- Downtime Component - Yes
Set Maintenance Mode in GitLab
If your change involves scheduled maintenance, add a step to set and unset maintenance mode per our runbooks. This will make sure SLA calculations adjust for the maintenance period.
Detailed steps for the change
Change Steps - steps to take to execute the change
Estimated Time to Complete (mins) - 45 mins
-
Set label changein-progress /label ~change::in-progress
-
Shutdown Gitaly/Praefect services -
Shutdown Gitaly 1: ssh gitaly-01-sv-pre.c.gitlab-pre.internal sudo gitlab-ctl stop gitaly
-
Shutdown Gitaly 2: ssh gitaly-02-sv-pre.c.gitlab-pre.internal sudo gitlab-ctl stop gitaly
-
Shutdown Gitaly 3: ssh gitaly-03-sv-pre.c.gitlab-pre.internal sudo gitlab-ctl stop gitaly
-
Shutdown Praefect ssh praefect-01-stor-pre.c.gitlab-pre.internal sudo gitlab-ctl stop praefect
-
-
Copy the Gitaly data from the current /mnt/storage/git-data/*
to/var/opt/gitlab/git-data
and do this for each of the Gitlay nodes 01,02,03. Ensure that the directory existsmkdir /var/opt/gitlab/git-data cp -r /mnt/storage/ /var/opt/gitlab/
-
Copy the praefect data from the current praefect-01:/mnt/storage/git-data/
to/var/opt/gitlab/git-data-praefect
. Ensure that the directory existsmkdir /var/opt/gitlab/git-data-praefect cp -r /mnt/storage/ /var/opt/gitlab/git-data-praefect
-
Merge this MR to update the Gitaly storage to the new data directory 👉 https://gitlab.com/gitlab-com/gl-infra/chef-repo/-/merge_requests/4786 -
Startup Gitaly/Praefect services -
Startup Gitaly 1: ssh gitaly-01-sv-pre.c.gitlab-pre.internal sudo gitlab-ctl start praefect
-
Startup Gitaly 2: ssh gitaly-02-sv-pre.c.gitlab-pre.internal sudo gitlab-ctl start gitaly
-
Startup Gitaly 3: ssh gitaly-03-sv-pre.c.gitlab-pre.internal sudo gitlab-ctl start gitaly
-
Startup Praefect ssh praefect-01-stor-pre.c.gitlab-pre.internal sudo gitlab-ctl start praefect
-
-
Merge this MR to remove the gitlab-nfs-cluster
from chef role👉 https://gitlab.com/gitlab-com/gl-infra/chef-repo/-/merge_requests/4787 -
Validate all is well by checking the logs -
Check service status
sudo gitlab-ctl status
-
Check the logs to confirm there are no errors
-
-
Finally, remove the storage from GCP -
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 (mins) - Estimated Time to Complete in Minutes
-
Stop the Gitaly instances and Praefect instances and revert this MR 👉 https://gitlab.com/gitlab-com/gl-infra/chef-repo/-/merge_requests/4786 -
Once that is complete revert the NFS mount 👉 https://gitlab.com/gitlab-com/gl-infra/chef-repo/-/merge_requests/4787 -
Set label changeaborted /label ~change::aborted
Monitoring
Key metrics to observe
- Metric: Metric Name
- Location: Thanos Link
- What changes to this metric should prompt a rollback:
- After removal they should not be listed
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 change window has been agreed with Release Managers in advance of the change. If the change is planned for APAC hours, this issue has an agreed pre-change approval.
- 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 prior to any C1, C2, or blocks deployments 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.