Ability to configure repo size/file size limits for each type of object storage individually
Problem
Configuring repo size limits on projects/groups/globally is global for all objects (files, lfs files, artifacts). Each one of these may be stored in a dedicated space with different cost, requirements, etc.
Proposal
Configure limits for instance/group/project for:
- Repo size limit (active-repo-files)
- Repo size limit (LFS files)
- Repo size limit (Artifacts)
Use cases
- We are a video game company, we have massive files in LFS and don't really want to set limits for our users, however, we do want to set limits for repo files for purposes of speed and backup
- We want to increase backup speed considerably by skipping both artifacts and LFS objects, but want to know the limits of the repo size will be respected (irrespective of LFS and artifacts).
- As a user I come to create a project with 500MB of large files. Reading the documentation I see LFS is an option and enable it on my project. I attempt to import my large files and receive a warning that repository size is capped to 300MB despite all my large files being stored in LFS and the size of my non-LFS files being under 100MB. I ask the instance administrators to increase the limit for my repository to 700MB but they refuse because it isn't possible to set separate limits for LFS and non-LFS storage. If they increase the size limit for my project then it would allow the project to use LFS but it would also allow it to exceed current guidelines for the use of non-LFS storage.
- We build containers 5GB in size & sometimes 1Tb / day. Currently, we host in-house but are evaluating .com. With this limitation, we cannot use GitLab's current solution.
Customers
Edited by Marie-Christine Babin