Bug 1290154 - [RFE] Allow yum/dnf to handle distributed download links with torrent:// urls
[RFE] Allow yum/dnf to handle distributed download links with torrent:// urls
Status: NEW
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: packaging-team-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-12-09 13:49 EST by Justin Garrison
Modified: 2017-01-11 11:19 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Justin Garrison 2015-12-09 13:49:43 EST
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?

Note You need to log in before you can comment on or make changes to this bug.