Currently each translation admin has their own clone of repositories. This has multiple drawbacks:
- Manual setup procedure
- Risk of having outdated repoconfig.yaml
- Increased disk space usage (one full set of repositories currently takes 16G)
- Increased disk IOps usage
- Increased file system cache churn
All of this could be solved by using a single, central location. There a few considerations to take into account:
- File system write permissions [can use same logic as for read-only clones]
- Locking to prevent concurrent access [can be postponed until fully automated exports are implemented]
Status
- This change has been deployed and verified
- Locking is being implemented separately
- Cleanup of now unused export directories has started
Outcome
We now use shared set of repositories for doing translation exports, instead of each committer having to have separate clones. New committers no longer need to do any manual setup and potential errors with that are removed. Server resource use has improved.