[gprd] CirepoM trial runs: Archived repositories

Staging Change - Criticality 3 C3

Change Objective	Describe the objective of the change
Change Type	Operation
Services Impacted	ServiceGitaly
Change Team Members	@glopezfernandez
Change Criticality	C3
Change Reviewer or tested in staging	Tested in staging per #2089 (closed)
Dry-run output	There is no dry-run mode for the tool
Due Date	Monday, May 18, 2020 - unknown
Time tracking	-

Detailed steps for the change

1. Load reposets for gprd archived repositories in production
   1. In order to conservatively approach these trial runs in production, we're going to serialize migrations against a single storage node.
   2. In reviewing Gitaly Node dashboards, we have selected file-27-stor-gprd.c.gitlab-production.internal
   3. Query: SELECT id, path, repository_read_only, repository_storage FROM projects WHERE archived = TRUE AND storage_repository = 'nfs-file27'
      • This query generated 4650 rows
2. Repositories are moving to file-hdd-01
3. Execute scheduled pipelines against the reposets: https://ops.gitlab.net/gitlab-com/gl-infra/infra-bots/cirepom-bot/pipeline_schedules
4. Track pipeline runs thought the jobs console

Rollback steps

1. If any issues are detected, it is safe to stop scheduled runs: https://ops.gitlab.net/gitlab-com/gl-infra/infra-bots/cirepom-bot/pipeline_schedules

Changes checklist

• Detailed steps and rollback steps have been filled prior to commencing work
• SRE on-call has been informed prior to change being rolled out
• There are currently no open issues labeled as ServiceMonitoring with severities of ~S1 or ~S2