| Summary: | Using metalinks instead of mirrorlist | ||
|---|---|---|---|
| Product: | Infrastructure | Reporter: | Nicolas Chauvet <kwizart> |
| Component: | Mirrors | Assignee: | Adrian Reber <adrian> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | kwizart |
| Priority: | P1 | ||
| Version: | NA | ||
| Hardware: | x86_64 | ||
| OS: | GNU/Linux | ||
| namespace: | |||
|
Description
Nicolas Chauvet
2016-09-29 12:24:44 CEST
I only plan to move to metalinks (and https) by f25 for now. This requires code changes. We are using rsync to scan the master mirror and metalink only works if it is a locally mounted file system. It shouldn't be too difficult to download the required files, but it takes some time. So it might be possible to r/o mount the content to the current master mirror with nfs over a vpn. The alternative is to have the master mirror on the same hypervisor where the filesystem lives. How the mirror manager got notified of the package push ? I don't think a mount over that distance is a good idea. Moving MirrorManager is a possibility, but then we should install MM2. I do not think that will happen before F25. Not enough time. MirrorManager runs a scan of the master mirror every few hours over rsync. Adding code to download the repomd.xml via http(s) is probably the best/simplest solution for now. metalinks are now working and can be used for F25 https://mirrors.rpmfusion.org/metalink?repo=free-fedora-rawhide&arch=x86_64 |