Workstream: Geo Gitlab.com Intercloud Migration

Label: ~"Workstream:GoldenSecondary"

Owner

Production Engineer in Replication Role

Goal

1. Have a full working secondary replicated from the Gitlab.com master running on Azure, to a secondary running on GCP
2. Once the replication is completed, ensure that the secondary stays up-to-date with the master
3. Ensure that the data in the secondary can be used to seed additional environments in GCP

Description

Gitlab Geo is aiming to be able to support Gitlab.com volumes post %10.2 or %10.3. This means that, at the earliest, we'll be able to start the Gitlab.com replication in January.

The target environment on the GCP side, the "Golden Secondary", will be a standard Omnibus Gitlab installation, not a GKE install. This will decouple the replication from the delivery of the final helm charts and allow us to start as soon as Geo is ready.

Once the replication is complete, new environments created in GCP will use snapshots from the "Golden Secondary" to seed their data.

Stages

1. Create omnibus-based environment in GCP
2. Start Geo replication to the new environment
3. Estimate total time for replication to complete