So far all gitlab* machines have been virtual.
Now we just got the first dedicated hardware, physical servers for gitlab.
There is one ticket for codfw and one for eqiad, both include gitlab* and gitlab-runner* machines.
codfw - T301183
eqiad - T301177
Both are now ready for us to take over.
GitLab Runner migration
gitlab-runner hosts can be integrated independently from GitLab migration. So the following machines need role(gitlab_runner):
- gitlab-runner1002.eqiad.wmnet (paused)
- gitlab-runner1003.eqiad.wmnet (paused)
- gitlab-runner1004.eqiad.wmnet (paused)
- gitlab-runner2002.codfw.wmnet (paused)
- gitlab-runner2003.codfw.wmnet (paused)
- gitlab-runner2004.codfw.wmnet (paused)
If the above Runners are configured and ready, ganeti VMs gitlab-runner1001.eqiad.wmnet and gitlab-runner2001.codfw.wmnet can be unregistered and destroyed.
- decommission gitlab-runner1001.eqiad.wmnet
- decommission gitlab-runner2001.codfw.wmnet
GitLab migration
GitLab migration needs some additional preparation.
- register second service IPs for gitlab1003
- validate puppet code and GitLab configuration with a physical replica on gitlab1003 (also bullseye)
-
evaluate additional configuration changes for potential HA setupsT323201 - create custom partman config for GitLab 793534
- bigger / root volume
- dedicated /srv volume (and move backups back to this folder instead of /mnt)
dedicated Docker volumenot needed- dedicated Registry volume (see gitlab_rails['registry_path'])
See checklist for replica migration: T307142#7969993
See checklist for production migration: T307142#7971192
Tasks after downtime:
- switch bacula fileset for gitlab from /mnt to /srv 800357
- increase TTL for DNS records
- check bacula backups for new host next day
- migrate additional hosts
- decommission old hosts
- gitlab2001.wikimedia.org
- gitlab1001.wikimedia.org
- remove dns entries
- remove hosts from hiera