Geo: Verification of uploads, job artifacts and LFS objects should be automatic
Problem to solve
Uploads, job artifacts and LFS objects should be verified automatically. This ensures that verifications will be run without a user intervention. This follows implementation of the following issues:
- https://gitlab.com/gitlab-org/gitlab-ee/issues/7184
- https://gitlab.com/gitlab-org/gitlab-ee/issues/7257
- https://gitlab.com/gitlab-org/gitlab-ee/issues/8922
- https://gitlab.com/gitlab-org/gitlab-ee/issues/8923
The current state of replication for these data types is:
Data Type | Replicated | Verified |
---|---|---|
Uploads | Yes | Yes, only on transfer, or manually (1) |
LFS Objects | Yes | Yes, only on transfer, or manually (1) |
CI Job Artifacts (other than traces) | Yes | No, only manually (1) |
Archived Traces | Yes | Yes, only on transfer, or manually (1) |
Intended users
Further details
Automation of verification is beneficial for DR related use-cases because it ensures that these steps are run. We don't depend on a user to trigger them manually.
Proposal
After the verification is implemented for different data types, the automation steps should be similar.
Documentation
We will need to update https://docs.gitlab.com/ee/administration/geo/disaster_recovery/background_verification.html#current-limitations
Testing
What does success look like, and how can we measure that?
Automatic background verification for uploads, job artifacts and LFS objects is comparable to repository verification
The table should look like this:
Data Type | Replicated | Verified |
---|---|---|
Uploads | Yes | Yes |
LFS Objects | Yes | Yes |
CI Job Artifacts (other than traces) | Yes | Yes |
Archived Traces | Yes | Yes |
What is the type of buyer?
- Ultimate
- Premium
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.