Description of problem:
This RFE requests the ability to have pulp throttle the network speed of its synchronization tasks, as well as exposing that capability to the user via the UI/API/CLI. Optimally, this capability would be configurable either per-repo, per-product (possibly?), or globally for the satellite instance.
Having this capability will allow the user to throttle synchronization tasks to not monopolize network bandwidth or to stay within their SLA contraints.
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Pulp offers this now. There are improvements we'd like to make to how we expose download configuration items in general, but this feature is at least available and documented. It can be set in the same places that proxy settings go, if you're familiar with that.
See "max_speed" here: https://pulp-rpm.readthedocs.org/en/latest/tech-reference/yum-plugins.html#configuration-parameters
The important thing to know is that the limit is per sync task. If you run a bunch of syncs at the same time on a bunch of different workers, each one will use up to its full limit without considering the others. We've toyed with the idea of having one global limit, but that would be very difficult to coordinate in a distributed architecture. That sort of aggregate limiting might be better done in a proxy.
(In reply to Michael Hrivnak from comment #6)
> See "max_speed" here:
Thank you, Michael.
> The important thing to know is that the limit is per sync task.
Yes, yum's "throttle" value in /etc/yum.conf works the same way.
Should we recommend to customers who are wanting a global limit to use iptables or firewalld to limit the rate of traffic from the these IP addresses (obtained from KCS Solution 1362093)?
Will work to get docs for 6.2 to detail how to configure Satellite 6 to use the Pulp configiruation
Per 6.3 planning, moving out non acked bugs to the backlog
https://access.redhat.com/articles/2387381 covers how to set this up in satellite 6.1 and 6.2 until there is support in the installer (either to set the config, or to preserve it)
*** Bug 1113237 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 1348572 ***