<div dir="ltr">Correct on both points. The normal sync+publish doesn’t have full feature parity with Nodes. In fact, another feature that comes to mind besides syncing of user metadata on repositories is that the strategies that were supported for syncing content across Nodes is going away.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br></div><div>David<br></div></div></div></div></div></div></div></div> <br><div class="gmail_quote">On Fri, Dec 9, 2016 at 9:58 AM, Mihai Ibanescu <span dir="ltr"><<a href="mailto:mihai.ibanescu@gmail.com" target="_blank">mihai.ibanescu@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Two things that come to mind:<div><br></div><div>* if nodes was indeed replicating the pulp user metadata (of which I am unsure), then you will have to make it clear that going with repo syncs is not quite equivalent</div><div>* sync runs are asynchronous calls. If a call runs for too long, there may be more than one sync task scheduled. An in-app scheduler could potentially notice that there is already a pending sync and not schedule another one. cron/systemd would have a harder time peeking into the task list.</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 9, 2016 at 9:38 AM, David Davis <span dir="ltr"><<a href="mailto:daviddavis@redhat.com" target="_blank">daviddavis@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Kodiak,<div><br></div><div>I think Katello is using sync schedules but they have some other solution lined up for when we drop them in 3.0. I am not sure of the exact details.</div><div><br></div><div>The main reason for dropping sync schedules was to keep the 3.0 MVP as small as possible and we felt like we could offload the functionality onto other tools like cron which are much more specialized and better able to deal with scheduling. If enough users want scheduled syncs back though, we may take a look at adding it in a 3.x release.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Hope that answers your question.<span class="m_-8117093144351452307HOEnZb"><font color="#888888"><br clear="all"><div><div class="m_-8117093144351452307m_-5461314167612999549m_-6905887484913322292gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br></div><div>David<br></div></div></div></div></div></div></div></div></font></span><div><div class="m_-8117093144351452307h5"> <br><div class="gmail_quote">On Thu, Dec 8, 2016 at 2:36 PM, Kodiak Firesmith <span dir="ltr"><<a href="mailto:kfiresmith@gmail.com" target="_blank">kfiresmith@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I'm good with this mostly just because Pulp 2.x schedules left a lot to be desired. It would have been nice if they were more like roles where you could create a schedule once, eg: DAILY-0030, and associate multiple repos w/ it. <div><br></div><div>I'm guessing you are dropping scheduling because Katello handles scheduling on it's own?</div><div><br></div><div> - Kodiak</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_-8117093144351452307m_-5461314167612999549m_-6905887484913322292h5">On Thu, Dec 8, 2016 at 2:20 PM, David Davis <span dir="ltr"><<a href="mailto:daviddavis@redhat.com" target="_blank">daviddavis@redhat.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_-8117093144351452307m_-5461314167612999549m_-6905887484913322292h5"><div dir="ltr">Jeffrey,<div><br></div><div>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:</div><div><br></div><div><a href="https://pulp.plan.io/projects/pulp/wiki/Pulp_3_Minimum_Viable_Product" style="font-size:12.800000190734863px" target="_blank">https://pulp.plan.io/projects/<wbr>pulp/wiki/Pulp_3_Minimum_Viabl<wbr>e_Product</a><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="m_-8117093144351452307m_-5461314167612999549m_-6905887484913322292m_6070443076536452421m_2479760346279020856gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br></div><div>David<br></div></div></div></div></div></div></div></div> <br><div class="gmail_quote">On Thu, Dec 8, 2016 at 9:36 AM, Miller, Jeffrey L <span dir="ltr"><<a href="mailto:jeff-l-miller@uiowa.edu" target="_blank">jeff-l-miller@uiowa.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div lang="EN-US" link="blue" vlink="purple"> <div class="m_-8117093144351452307m_-5461314167612999549m_-6905887484913322292m_6070443076536452421m_2479760346279020856m_-5718701812055690771WordSection1"> <p class="MsoNormal"><a name="m_-8117093144351452307_m_-5461314167612999549_m_-6905887484913322292_m_6070443076536452421_m_2479760346279020856_m_-5718701812055690771__MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">David,<u></u><u></u></span></a></p> <p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></span></p> <p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">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.<u></u><u></u></span></span></p> <p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></span></p> <p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">-Jeffrey<u></u><u></u></span></span></p> <p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></span></p> <p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></span></p> <p class="MsoNormal"><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></span></p> <span></span> <p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <a href="mailto:pulp-list-bounces@redhat.com" target="_blank">pulp-list-bounces@redhat.com</a> [mailto:<a href="mailto:pulp-list-bounces@redhat.com" target="_blank">pulp-list-bounces@redh<wbr>at.com</a>] <b>On Behalf Of </b>David Davis<br> <b>Sent:</b> Thursday, December 8, 2016 8:08 AM<br> <b>To:</b> <a href="mailto:pulp-list@redhat.com" target="_blank">pulp-list@redhat.com</a><br> <b>Subject:</b> [Pulp-list] Deprecating Pulp Nodes<u></u><u></u></span></p><div><div class="m_-8117093144351452307m_-5461314167612999549m_-6905887484913322292m_6070443076536452421m_2479760346279020856h5"> <p class="MsoNormal"><u></u> <u></u></p> <div> <div> <p class="MsoNormal">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:<u></u><u></u></p> </div> <div> <p class="MsoNormal"><u></u> <u></u></p> </div> <div> <p class="MsoNormal"><a href="http://pulpproject.org/2016/12/07/deprecating-nodes/" target="_blank">http://pulpproject.org/2016/12<wbr>/07/deprecating-nodes/</a><u></u><u></u></p> </div> <div> <p class="MsoNormal"><u></u> <u></u></p> </div> <div> <p class="MsoNormal">Feel free to respond with any questions or concerns.<u></u><u></u></p> </div> <div> <p class="MsoNormal"><u></u> <u></u></p> </div> <div> <p class="MsoNormal">David<u></u><u></u></p> </div> </div> </div></div></div> </div> </blockquote></div><br></div> <br></div></div>______________________________<wbr>_________________<br> Pulp-list mailing list<br> <a href="mailto:Pulp-list@redhat.com" target="_blank">Pulp-list@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/pulp-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-list</a><br></blockquote></div><br></div> </blockquote></div><br></div></div></div></div> <br>______________________________<wbr>_________________<br> Pulp-list mailing list<br> <a href="mailto:Pulp-list@redhat.com" target="_blank">Pulp-list@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/pulp-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-list</a><br></blockquote></div><br></div> </div></div></blockquote></div><br></div>