Bug 953037

Summary: [RFE] Ability to schedule node sync
Product: [Retired] Pulp Reporter: Ryan Bowlby <rbowlby83>
Component: nodesAssignee: pulp-bugs
Status: CLOSED UPSTREAM QA Contact: Preethi Thomas <pthomas>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: cplummer+bz, jason.dobies, mhrivnak, rbarlow
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-19 01:10:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ryan Bowlby 2013-04-17 08:41:58 UTC
Description of problem:

With the move from 1.1 to 2.1 I am no longer capable of scheduling a repo sync that taks advantage of filtering. The "clone" feature was replaced with unit copy, but no scheduling of unit copy exists in 2.1. Closely related, I am no longer able to schedule repo syncs to "satelites" or pulp-child-nodes. I'm likely going to put both these things in cron and that makes me sad. :(

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


How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Jay Dobies 2013-04-22 19:27:04 UTC
I split off the copy scheduling into a separate bug as it's a separate area of the code. I added the original reporter as a CC.

Comment 2 Christina Plummer 2014-06-05 13:25:29 UTC
+1 to scheduling the node sync.  I'm in the same spot Ryan was in a few months ago and planning to set up cron jobs for now.

Comment 3 Brian Bouterse 2015-02-19 01:10:18 UTC
Moved to https://pulp.plan.io/issues/180