Geo 17.10 Outlook
This is the current outlook for the 17.10 milestone. The Geo team schedules issues and works in a continuous Kanban manner, while still aligning with milestones. See our process page for more details.
Last Updated: 11th February 2025
Org mover MVC
Cells and Organizations are foundational components of GitLab's next-generation architecture of GitLab.com.
The Cells architecture is horizontally scalable, resilient, and provides a more consistent user experience.
As we approach Cells 1.5, we need a way to migrate organisations from the current GitLab.com infrastructure to Cells. We need to achieve this with minimal disruption to our users on GitLab.com. The org mover will help us achieve this by replicating the organisation's data to a Cell. The org mover will perform the replication in the background while users of the organization continue to use GitLab. Any new changes made by users will also be synced to the Cell.
Once the data between the current GitLab.com infrastructure and the Cell are in sync, we will cut over the organization to the cell. The cutover may initially require some downtime to allow the replication to catch up.
Org Mover Design priority2
Who: Douglas/Mike
We are currently discussing the Org Mover Design, testing/investigating with a POC and also planning to update the design docs and add more documentation on how Org Mover works at a high level.
-
Org Mover: POC to replicate non-PG data in GDK + Cells -
Mike/Douglas -
Org Mover: Design how to handle `shards` and its dependent tables across a move -
Douglas -
Org Mover: Decide how to handle each clusterwid... (gitlab-org/gitlab#514633 - closed) -
Mike/Douglas -
Org Mover: Update design doc with diagrams and more design details -
Mike/Douglas
Begin rollout of checksumming of all data on GitLab.com priority2
Who: Douglas, Scott, Mike, Natanael
A pre-requisite for org mover is to checksum data on the source cell. The first source cell will be the GitLab.com monolith. Based on experience with Geo, we know that we will discover orphaned database records and files that will need resolving prior to being able to successfully move and org. The progressive rollout of checksumming for data types on GitLab.com will allow us to investigate orphaned records and correct them well ahead of any migration. We also will be limiting the checksumming by a selective set of organizations. To fully complete this feature, this has dependencies on sharding work being completed.
-
Org Mover - Move all verification details into separate tables -
Scott -
Partition table ci_job_artifact_states -
Natanael
Geo Improve Observability priority2
Who: Zack/Chloe/Aakriti
In order to support Cells and Org Mover, current Geo functionality for replication and verification especially surfaced in the UI needs improvement and better observability. The goals we want to achieve with this epic are:
-
Why: This will provide immediate visibility into errors for the systems admin without needing to resort to the rails console. Since this is anticipated to be a relatively small effort we will tackle this first.
-
Improve primary verification experience
Why: This will provide immediate visibly into verification errors on the primary site without needing to resort to the rails console. We've noticed an increasing need for this visibility amongst new Geo customers. This will also help improve the first time experience.
-
Level-up available actions to fix problems
Why: This will reduce the need to go to the rails console to apply specific actions to a sub-set of objects. We can build on this foundation to provide mode repair actions in future.
-
Geo: Correlate logs across sites -
Aakriti
-
Geo: Correlate logs across sites -