Jeffrey, That’s a great question. We are not in fact planning to support sync schedules in 3.0. We’re encouraging users to use other tools like cron and systemd timers instead. Here’s an overview of what we’re planning for Pulp 3.0:
https://pulp.plan.io/projects/pulp/wiki/Pulp_3_Minimum_Viable_Product David On Thu, Dec 8, 2016 at 9:36 AM, Miller, Jeffrey L <jeff-l-mil...@uiowa.edu> wrote: > David, > > > > Is scheduling syncs also being removed? I see the blog post is using cron > to sync or publish the repository instead of setting a schedule. > > > > -Jeffrey > > > > > > > > *From:* pulp-list-boun...@redhat.com [mailto:pulp-list-boun...@redhat.com] > *On Behalf Of *David Davis > *Sent:* Thursday, December 8, 2016 8:08 AM > *To:* pulp-list@redhat.com > *Subject:* [Pulp-list] Deprecating Pulp Nodes > > > > We wrote a blog post about removing Nodes in Pulp 3.0 but I figured I'd > sent out an email as well in order to increase visibility. Nodes will be > officially deprecated in Pulp 2.12 and then removed in Pulp 3.0. For more > information about why we deprecated Nodes and how you can reproduce their > functionality using a standard install of Pulp, check out the blog post: > > > > http://pulpproject.org/2016/12/07/deprecating-nodes/ > > > > Feel free to respond with any questions or concerns. > > > > David >
_______________________________________________ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
