Bug 794547 - Implement "cron_sync" command
Summary: Implement "cron_sync" command
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: PulpDist
Classification: Community
Component: Management CLI
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 0.1.0
Assignee: Nick Coghlan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-17 05:00 UTC by Nick Coghlan
Modified: 2012-04-04 06:02 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-04 06:02:25 UTC


Attachments (Terms of Use)

Description Nick Coghlan 2012-02-17 05:00:49 UTC
This command is a workaround for the lack of scheduling support for plugin-based repositories in the current upstream Pulp releases.

The command will look for a repo.notes.pulpdist.check_hours attribute on each repo with sync enabled in the importer configuration. For every repo where the current hour of the day modulo the "check_hours" attribute is 0, the client will initiate a sync operation.

The command will support a --threads option (defaulting to 8). That is the maximum number of concurrent sync operations the client will initiate.

Comment 1 Nick Coghlan 2012-04-04 06:02:25 UTC
Cron sync has been implemented for 0.0.11.

The relevant notes entry is pulpdist.sync_hours.

Only one cron_sync job can be running on a system at a time, even if it affects a different Pulp host.


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