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.
DescriptionCalvin Hartwell
2016-06-21 13:16:08 UTC
Document URL:
My current customer has an issue where Satellite 6 maxed out their bandwidth during the sync which caused a small outage on multiple customer facing websites.
The requirement on the network bandwidth/speed/load should be clearly noted in the pre-reqs and the max_speed option should be managed by the katello-installer (capsule-installer in 6.2) quite clearly. The customer should be allowed to easily throttle the speed of pulp as required.
Section Number and Name:
Satellite 6.1 installation guide pre-reqs, section 1.4
Describe the issue:
* Customer needs to know there will be a pre-req of high bandwidth utilisation by the satellite 6 server during the initial sync.
* Customer should be able to throttle the bandwidth of the satellite 6 server after/during the install by using the max_speed option on the yum
Suggestions for improvement:
* offer the max_speed speed as an option in the 6.1/6.2 manuals. Clearly state the pre-req on bandwidth utilisation.
Additional information:
*** Also note: the pulp documentation on the max_speed option within pulp is inconsistent. Some sources state that it is just an integer (but not what that integer is), some sources state it is in bytes per second (github repo for pulp) and some sources state it is in kbps (pulp manuals).
This needs to be ironed out and confirmed with the pulp developers before going into the manual.