- 1 Summary
- 2 Owner
- 3 Resources
- 4 Current status
- 5 Detailed Description
- 6 Why it would be good for Mageia to use it
- 7 Test case
- 8 Tasks
- 9 Software / Packages Dependencies
- 10 What could disrupt development of this new feature
- 11 Planning
- 12 Contingency
- 13 Release Notes
- 14 Documentation
- 15 Associated Bugs
- 16 Packager comments
Migrate mirror management to MirrorBrain and start generating metalinks for DNF to use for intelligent mirror selection.
- Name: Neal Gompa
- Email: email@example.com
This will require efforts by the Mageia sysadmins to migrate our mirror database into MirrorBrain and convert the existing Yum-style mirrorlist endpoint to a MirrorBrain managed one, as well as introduce a new endpoint for getting the metalink for DNF and PackageKit.
The urpmi and installer developers will need to change the configuration of urpmi to use the MirrorBrain-managed auto-redirector URL, and the packager of mageia-repos will need to change the repo files to use the metalink for DNF and PackageKit to use.
The web team and the sysadmin team will need to migrate the web downloads for ISOs to MirrorBrain as well.
- Targeted release: Mageia 7
- Last updated: 2017/09/16
- Percentage of completion: 0%
Per the MirrorBrain website: "MirrorBrain is an open source framework to run a content delivery network using mirror servers. It solves a challenge that many popular open source projects face - a flood of download requests, often magnitudes more than any single site could practically handle."
This change involves migrating every end point where mirror selection occurs to being managed by MirrorBrain in some fashion (web downloads, the installer, urpmi, PackageKit/DNF) to massively improve the reliability of mirror selection and availability of Mageia content.
Why it would be good for Mageia to use it
Mageia's current mirror infrastructure has been crumbling under pressure for some time now. Among other things, users get a bad experience from bad mirrors randomly downgrading or missing necessary content, causing really unexpected things to occur on their systems.
It's exponentially worse for Cauldron users, where it's a hit-or-miss affair (mostly misses) to get up to date Cauldron content, especially for users in the Americas and Asia, where we have fewer mirrors in general.
MirrorBrain improves this experience by tracking mirrors and automatically filtering the list based on content availability, preventing users from seeing bad mirrors on a regular basis. In addition, the content redirector portion automatically determines a good, up to date mirror to use based on a number of factors about your connection, which ensures that you get a good experience for downloading content directly (through web browsers or through urpmi).
- Adding urpmi distrib media should give you MirrorBrain redirector
- The existing yum-style mirrorlist endpoint should work as-is with MirrorBrain
- The new metalink endpoint for rpm-md repos should work with PackageKit/DNF.
- Deploy and activate MirrorBrain
- Migrate the mirror database from Mirmon to MirrorBrain
- Migrate the Yum style mirrorlist endpoint to MirrorBrain managed mirrorlist
- Migrate the urpmi distrib data to the MirrorBrain redirector URL (download.mageia.org or something similar)
Software / Packages Dependencies
- MirrorBrain has been in Mageia for a while now, and is part of the standard repositories in Mageia 5 (which our infrastructure currently runs on)
What could disrupt development of this new feature
If the MirrorBrain deployment cannot be completed and mirror selector endpoints migrated, then this feature cannot be fully implemented.
Early inclusion into Mageia 7 would allow for good appropriation of administrator resources to roll this out and make sure everything works.
If this fails to be ready for Mageia 7, then we fall back to our current infrastructure.
The release notes should indicate that Mageia now offers enhanced automatic mirror selection powered by MirrorBrain.