Description of problem: In large environments there is often a lot of stress put on a repository published via http(s). While there are ways to load balance the http endpoint it still becomes a single point of failure when a distributed downloading solution can be implemented. Other options are distributed file systems and using file:// repos but they are not always available in some environments or have more management overhead that is not desirable. Expected results: There should be a way to join machines to a torrent pool and then have package update files distributed throughout the pool instead of downloading from a single source. Additional info: There obviously still needs to be a seed server but that would have relatively low overhead once 10+ systems can download the packages. This type of distribution can be very helpful when environments grow into the 1000s of machines as package updates can easily saturate a 1Gb and possibly even a 10Gb network interface. If this is possible via a yum/dnf plugin please let me know. I only briefly looked at the plugin documentation. Outside of setting up a mirrorlist url are there any other best practices for distributing package updates at large scale?
yum and related packages are no longer actively developed. They are being replaced with dnf, dnf-utils, etc. I'm closing this bug because it's most likely never going to be fixed. If you still consider your bug report important, reopen it, please.