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.
Bug 1320232 - [RFE] Lazy sync during idle time
Summary: [RFE] Lazy sync during idle time
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: rhci-common-installer
TreeView+ depends on / blocked
 
Reported: 2016-03-22 15:30 UTC by Thom Carlin
Modified: 2019-09-26 13:58 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-10 17:29:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Thom Carlin 2016-03-22 15:30:37 UTC 
Description of enhancement:

Enhance lazy sync to:
1) Synchronize while the system is idle
2) Prioritize latest versions of package.  Alternatively, have option to restrict the repository to only contain the latest version.

Version-Release number of selected component (if applicable):

6.1.7

Additional info:

Would help with QCI
Comment 1 David Davis 2016-03-22 15:38:42 UTC 
I think this would be either a new download policy or some configuration on the background download policy that would check to make sure that the system is idle before attempting to download packages.
Comment 2 Bryan Kearney 2016-07-26 19:01:15 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 4 Michael Hrivnak 2016-10-05 15:16:40 UTC 
For RPMs, pulp already has the ability to restrict sync to the most recent versions of each package. You can specify how many old versions of a package you want to have in the repository via an importer setting. I think that will accommodate your prioritization request.

For scheduling of background download during system idle time, can you elaborate on your goal for this? The task does not use much for system resources except to generate network traffic and a limited amount of disk IO. If those are your concerns, an easy option would be to limit the bandwidth for those downloads, which is a setting on the repository's importer. If you have something else in mind, please let us know.
Comment 5 Thom Carlin 2016-10-05 15:28:27 UTC 
Please elaborate on how to restrict the sync to a certain number of old versions of a package.

For the scheduling, we are trying to reduce the content sync to a minimum.  For the QCI use case, the latest version of each package is sufficient for our needs.  However, the total elapsed time is of great concern to us.
Comment 6 Thom Carlin 2016-10-05 15:30:55 UTC 
I also reached out to QCI devs as they would better be able to speak to these issues.
Comment 7 Michael Hrivnak 2017-01-09 21:42:43 UTC 
See the "retain_old_count" setting here: http://docs.pulpproject.org/plugins/pulp_rpm/tech-reference/yum-plugins.html#yum-importer

You may need katello to expose that if you want to set it per-repo, but you can always add it to the yum plugin config in /etc/pulp/server/plugins.conf.d/

Bandwidth limiting is also documented there under the name "max_speed".
Comment 8 Michael Hrivnak 2017-01-09 22:07:17 UTC 
John, are you able to elaborate on this RFE, or point us at the right person? What is the user experience goal?
Comment 9 John Matthews 2017-01-09 22:29:24 UTC 
Thom,

Do you see this RFE as still being required for QCI?
If so, would you elaborate on the RFE?
Comment 10 Thom Carlin 2017-01-10 17:29:56 UTC 
Hi Michael,

Thanks for the the information on the retain_old_count and max_speed settings.

bbuckinham mentioned the "mirror on sync" setting (new in 6.2) will also help with this request.

With the information provided, the original RFE intent has been addressed to some measure.  Closing as CURRENTRELEASE.
Note You need to log in before you can comment on or make changes to this bug.