Using Geo for Cells 1.0
Background
We are evaluating DR solutions for Cells in the DR for Cells blueprint gitlab-org/gitlab!146189 (merged)
Part of that evaluation will be taking a look at Geo as a way for us to add disaster resilience to the Cells offering. This would give us a multi-region footprint for Cells and a great starting point for data recovery if it is required.
This is mostly a discovery task that when complete will allow us to make a Geo on Cells decision for Cells 1.0 and future releases.
-
A detailed cloud spend estimate for adding a Geo deployment to every Cell -
Summarize the data replication strategy for Geo Cells on GCP (database, redis, object storage) -
Understand how Geo on Cells is impacted by the Global and Routing service
References:
- DR blueprint for Cells gitlab-org/gitlab!146189 (merged)
- Dedicated recovery guide https://gitlab-com.gitlab.io/gl-infra/gitlab-dedicated/team/runbooks/regional-failure-recovery.html
- Dedicated guide for restoring from backups https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/blob/main/runbooks/restore-from-backups.md#full-system-restore
- Benchmark epic for validating RTO/RPO on Dedicated https://gitlab.com/groups/gitlab-com/gl-infra/gitlab-dedicated/-/epics/292
- Geo failover runbook for Dedicated https://gitlab-com.gitlab.io/gl-infra/gitlab-dedicated/team/runbooks/geo.html#failover
- Geo failover firedrills for Dedicated https://gitlab-com.gitlab.io/gl-infra/gitlab-dedicated/team/runbooks/rto-rpo-drill.html
- Cells DR proposal using backups https://docs.google.com/document/d/1N6ow0r2RbtJH5H9L_ND2ErpbwQEovn_qO8A88Yv3eLU/edit#heading=h.rm2ssz9b6jd1
Edited by John Jarvis