Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
Comment 1RHEL Program Management
2014-07-17 20:34:17 UTC
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:
> https://pulp-rpm.readthedocs.org/en/latest/tech-reference/yum-plugins.
> html#configuration-parameters
===
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)?
download.rhn.redhat.com 209.132.183.193
satellite.rhn.redhat.com 209.132.183.191
xmlrpc.rhn.redhat.com 209.132.183.192
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)