Geo supports replication for new blobs
Geo supports replication for new blobs
Introduction
The Geo team is currently building a self-service framework to make it incredibly easy to add new Resources to Geo. The first iteration of the self-service framework will cover blobs (essentially files) to be replicated and verified with minimal effort. This epic tracks the work to be performed so that Geo replicates and verifies all currently (as of April 2020) blobs produced by GitLab
Problem to solve
Adding verification and replication for new Resources was hard. We still don't support replication and verification for a large number of features that rely on blobs.
The current list of what is and is not replicated/verified is availabe in https://docs.gitlab.com/ee/administration/geo/replication/datatypes.html#limitations-on-replicationverification
Intended users
Further details
In case a Geo customer needs to failover the more data is replicated and verified the better. This means no additional steps need to be performed.
Proposal
- Add verification and replication for all remaining blob Resources.
- The first Resource will be mainly implemented by the Geo team
- Other ones should be done in collaboration with the teams owning the feature
- For LFS files, Job artifacts and Uploads the Geo team will perform the refactoring.
Documentation
We need to update https://docs.gitlab.com/ee/administration/geo/replication/datatypes.html#limitations-on-replicationverification
Testing
The testing needs should be covered mainly by the self-service framework.
What does success look like, and how can we measure that?
- Percentage of replicated and verified blob data types (currently seven data types. 3 replicated, non verified)
- If fully implented the overall percentages will be 60% → 77% replication; 22% → 68% verification
What is the type of buyer?
- Premium
- Ultimate
Links / references
- Show closed items
- View on a roadmap
- Show labels
- Show closed items