<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 8, 2018 at 11:53 AM, Bryan Kearney <span dir="ltr"><<a href="mailto:bkearney@redhat.com" target="_blank">bkearney@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">ok.. so it is quiesce the old system and then normal updates?<br></blockquote><div>Yes, exactly. :)<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
-- bk<br>
<span class=""><br>
On 05/08/2018 07:27 AM, Brian Bouterse wrote:<br>
> Here is a look at what the Pulp2 -> Pulp3 necessary things would be<br>
> w.r.t this change. These could also be automated.<br>
> <br>
> 1. Empty the Pulp system of all of it's tasks and stop all Pulp services.<br>
> 2. Uninstall RabbitMQ or Qpid if its only purpose was to serve the Pulp<br>
> tasking system. (Satellite uses Qpid in other ways so it would likely<br>
> keep it in the architecture for other purposes).<br>
> 3. Uninstall Celery/kombu/billiard/py-amqp (the whole celery stack<br>
> effectively)<br>
> 4. upgrade the bits to Pulp3. This will also bring RQ with it automatically.<br>
> 5. Install Redis as a new service in your infra<br>
> 6. Replace the systemd files for the pulp_workers and<br>
> pulp_resource_manager. This causes systemd to start RQ instead of Celery.<br>
> 7. [optional] Configure Redis auth/ssl and configure Pulp's settings<br>
> file to match if that is part of your environment.<br>
> <br>
> Questions/ideas/concerns are welcome.<br>
> <br>
> <br>
> <br>
> On Tue, May 8, 2018 at 8:48 AM, Bryan Kearney <<a href="mailto:bkearney@redhat.com">bkearney@redhat.com</a><br>
</span><span class="">> <mailto:<a href="mailto:bkearney@redhat.com">bkearney@redhat.com</a>>> wrote:<br>
> <br>
> what does this look like for upgrading from Pulp2 to Pulp3?<br>
> <br>
> -- bk<br>
> <br>
> On 05/08/2018 05:34 AM, David Davis wrote:<br>
> > +1. Thank you @bmbouter and @dalley for working on this.<br>
> > <br>
> > <br>
> > David<br>
> > <br>
> > On Mon, May 7, 2018 at 5:37 PM, Daniel Alley <<a href="mailto:dalley@redhat.com">dalley@redhat.com</a> <mailto:<a href="mailto:dalley@redhat.com">dalley@redhat.com</a>><br>
</span><span class="">> > <mailto:<a href="mailto:dalley@redhat.com">dalley@redhat.com</a> <mailto:<a href="mailto:dalley@redhat.com">dalley@redhat.com</a>>>> wrote:<br>
> > <br>
> > I've finished my review and resolved all of the 'blocker' issues<br>
> > that were uncovered during testing. Overall, I'm highly confident<br>
> > that this is a better path forwards than the continued use of Celery<br>
> > / Kombu. There are a couple of outstanding edge cases to be<br>
> > resolved eventually, which I plan to file as issues post-merge, but<br>
> > nothing serious or intractable. <br>
> > <br>
> > If there are no objections, I think it would be reasonable to merge<br>
> > this code after this week's beta builds are published (after, in<br>
> > order to avoid major changes during Summit / PyCon prep time).<br>
> > <br>
> > Thank you, Brian, for doing the planning and work needed to make<br>
> > this happen. It was a lot of effort and is very highly appreciated.<br>
> > <br>
> > On Mon, Apr 30, 2018 at 8:28 AM, Brian Bouterse <<a href="mailto:bbouters@redhat.com">bbouters@redhat.com</a> <mailto:<a href="mailto:bbouters@redhat.com">bbouters@redhat.com</a>><br>
</span><span class="">> > <mailto:<a href="mailto:bbouters@redhat.com">bbouters@redhat.com</a> <mailto:<a href="mailto:bbouters@redhat.com">bbouters@redhat.com</a>>>> wrote:<br>
> > <br>
> > Through several rebases, now all PRs are showing the RQ PRs on<br>
> > Travis as passing with pulp-smash. Several points of feedback<br>
> > have been addressed.<br>
> > <br>
> > If you're interested in commenting on these PRs or trying them<br>
> > out, please do. I hope to merge after the other taking system<br>
> > maintainers @dalley and @daviddavis have finished their<br>
> > testing/review and barring any other calls for delay or blocking<br>
> > concerns.<br>
> > <br>
> > If there are any questions, issues, or concerns, please reach<br>
> > out, and we can talk through them.<br>
> > <br>
> > <br>
> > <br>
> > On Fri, Apr 20, 2018 at 4:18 PM, Brian Bouterse<br>
> > <<a href="mailto:bbouters@redhat.com">bbouters@redhat.com</a> <mailto:<a href="mailto:bbouters@redhat.com">bbouters@redhat.com</a>><br>
</span><div><div class="h5">> <mailto:<a href="mailto:bbouters@redhat.com">bbouters@redhat.com</a> <mailto:<a href="mailto:bbouters@redhat.com">bbouters@redhat.com</a>>>> wrote:<br>
> > <br>
> > I put together a prototype and posted the PRs. I'm still<br>
> > working to get Travis happy, but locally 100% of smash tests<br>
> > using these branches. It's worked very reliably for me so<br>
> > far. There are no gaps in the pulp feature set on top of RQ.<br>
> > <br>
> > I hope people test it out and give some feedback. See the<br>
> > commit messages for details on what was done. Here are the PRs:<br>
> > <br>
> > <a href="https://github.com/pulp/pulp/pull/3454" rel="noreferrer" target="_blank">https://github.com/pulp/pulp/<wbr>pull/3454</a><br>
> <<a href="https://github.com/pulp/pulp/pull/3454" rel="noreferrer" target="_blank">https://github.com/pulp/pulp/<wbr>pull/3454</a>><br>
> > <<a href="https://github.com/pulp/pulp/pull/3454" rel="noreferrer" target="_blank">https://github.com/pulp/<wbr>pulp/pull/3454</a><br>
> <<a href="https://github.com/pulp/pulp/pull/3454" rel="noreferrer" target="_blank">https://github.com/pulp/pulp/<wbr>pull/3454</a>>><br>
> > <a href="https://github.com/pulp/pulp_file/pull/72" rel="noreferrer" target="_blank">https://github.com/pulp/pulp_<wbr>file/pull/72</a><br>
> <<a href="https://github.com/pulp/pulp_file/pull/72" rel="noreferrer" target="_blank">https://github.com/pulp/pulp_<wbr>file/pull/72</a>><br>
> > <<a href="https://github.com/pulp/pulp_file/pull/72" rel="noreferrer" target="_blank">https://github.com/pulp/<wbr>pulp_file/pull/72</a><br>
> <<a href="https://github.com/pulp/pulp_file/pull/72" rel="noreferrer" target="_blank">https://github.com/pulp/pulp_<wbr>file/pull/72</a>>><br>
> > <a href="https://github.com/pulp/devel/pull/146" rel="noreferrer" target="_blank">https://github.com/pulp/<wbr>devel/pull/146</a><br>
> <<a href="https://github.com/pulp/devel/pull/146" rel="noreferrer" target="_blank">https://github.com/pulp/<wbr>devel/pull/146</a>><br>
> > <<a href="https://github.com/pulp/devel/pull/146" rel="noreferrer" target="_blank">https://github.com/pulp/<wbr>devel/pull/146</a><br>
> <<a href="https://github.com/pulp/devel/pull/146" rel="noreferrer" target="_blank">https://github.com/pulp/<wbr>devel/pull/146</a>>><br>
> > <a href="https://github.com/PulpQE/pulp-smash/pull/960" rel="noreferrer" target="_blank">https://github.com/PulpQE/<wbr>pulp-smash/pull/960</a><br>
> <<a href="https://github.com/PulpQE/pulp-smash/pull/960" rel="noreferrer" target="_blank">https://github.com/PulpQE/<wbr>pulp-smash/pull/960</a>><br>
> > <<a href="https://github.com/PulpQE/pulp-smash/pull/960" rel="noreferrer" target="_blank">https://github.com/PulpQE/<wbr>pulp-smash/pull/960</a><br>
> <<a href="https://github.com/PulpQE/pulp-smash/pull/960" rel="noreferrer" target="_blank">https://github.com/PulpQE/<wbr>pulp-smash/pull/960</a>>><br>
> > <br>
> > Feel free to send questions here or to the PR. Any feedback<br>
> > is welcome.<br>
> > <br>
> > -Brian<br>
> > <br>
> > <br>
> > <br>
> > <br>
> > On Thu, Mar 22, 2018 at 5:28 PM, Milan Kovacik<br>
> > <<a href="mailto:mkovacik@redhat.com">mkovacik@redhat.com</a> <mailto:<a href="mailto:mkovacik@redhat.com">mkovacik@redhat.com</a>><br>
</div></div><span class="">> <mailto:<a href="mailto:mkovacik@redhat.com">mkovacik@redhat.com</a> <mailto:<a href="mailto:mkovacik@redhat.com">mkovacik@redhat.com</a>>>> wrote:<br>
> > <br>
> > +1 I like RQ and I like<br>
> > <a href="http://python-rq.org/docs/testing/" rel="noreferrer" target="_blank">http://python-rq.org/docs/<wbr>testing/</a> <<a href="http://python-rq.org/docs/testing/" rel="noreferrer" target="_blank">http://python-rq.org/docs/<wbr>testing/</a>><br>
> > <<a href="http://python-rq.org/docs/testing/" rel="noreferrer" target="_blank">http://python-rq.org/docs/<wbr>testing/</a><br>
> <<a href="http://python-rq.org/docs/testing/" rel="noreferrer" target="_blank">http://python-rq.org/docs/<wbr>testing/</a>>> esp.<br>
> > there's Fakeredis ;)<br>
> > <br>
> > <br>
> > --<br>
> > milan<br>
> > <br>
> > <br>
> > On Thu, Mar 22, 2018 at 6:58 PM, Brian Bouterse<br>
> > <<a href="mailto:bbouters@redhat.com">bbouters@redhat.com</a> <mailto:<a href="mailto:bbouters@redhat.com">bbouters@redhat.com</a>><br>
</span><span class="">> <mailto:<a href="mailto:bbouters@redhat.com">bbouters@redhat.com</a> <mailto:<a href="mailto:bbouters@redhat.com">bbouters@redhat.com</a>>>> wrote:<br>
> > > Thanks for all the discussion both on list and on irc.<br>
> > After more<br>
> > > investigation, it sounds like there are no feature<br>
> > gaps, but we will need to<br>
> > > incorporate this workaround to cancel a task that is<br>
> > already running.<br>
> > ><br>
> > > The feedback I've heard on the idea is that it's<br>
> > valuable and looks<br>
> > > feasible, but we won't really know until we prototype<br>
> > it a bit. Based on the<br>
> > > technical outline in the previous email, I believe it<br>
> > can be prototyped in a<br>
> > > day or two. I plan to do this soon, once I contribute<br>
> > to a few other<br>
> > > required-for-beta planning items first. I'll post my<br>
> > PR to see what other<br>
> > > think of the change, probably next week.<br>
> > ><br>
> > ><br>
> > ><br>
> > > On Wed, Mar 21, 2018 at 6:41 PM, Daniel Alley<br>
> > <<a href="mailto:dalley@redhat.com">dalley@redhat.com</a> <mailto:<a href="mailto:dalley@redhat.com">dalley@redhat.com</a>><br>
</span><span class="">> <mailto:<a href="mailto:dalley@redhat.com">dalley@redhat.com</a> <mailto:<a href="mailto:dalley@redhat.com">dalley@redhat.com</a>>>> wrote:<br>
> > >><br>
> > >> I meant in the sense that, what is the aftermath when<br>
> > it comes back<br>
> > >> online, and is it screwed up in ways that cause side<br>
> > effects.<br>
> > >><br>
> > >> On Wed, Mar 21, 2018 at 5:02 PM, Jeremy Audet<br>
> > <<a href="mailto:jaudet@redhat.com">jaudet@redhat.com</a> <mailto:<a href="mailto:jaudet@redhat.com">jaudet@redhat.com</a>><br>
</span><span class="">> <mailto:<a href="mailto:jaudet@redhat.com">jaudet@redhat.com</a> <mailto:<a href="mailto:jaudet@redhat.com">jaudet@redhat.com</a>>>> wrote:<br>
> > >>><br>
> > >>> > RQ does not support revoking tasks. If you send<br>
> > the worker a SIGINT,<br>
> > >>> > it will finish the task and then stop processing<br>
> > new ones. If you send the<br>
> > >>> > worker SIGKILL, it will stop immediately, but I<br>
> > don't think it gracefully<br>
> > >>> > handles this circumstance.<br>
> > >>><br>
> > >>> Nothing handles SIGKILL gracefully. Processes can't<br>
> > catch that signal.<br>
> > >>> `kill -9 $pid` sends SIGKILL.<br>
> > >>><br>
> > >>> If one is looking for a way to gracefully,<br>
> > immediately kill an RQ<br>
> > >>> worker, then SIGTERM may do the trick. Anecdotally,<br>
> > many processes<br>
> > >>> handle this signal in a hurried fashion.<br>
> > Semantically, this is<br>
> > >>> appropriate: SIGINT is the "terminal interrupt"<br>
> > signal (Ctrl+c sends<br>
> > >>> SIGINT), whereas SIGTERM is the "termination signal."<br>
> > >><br>
> > >><br>
> > ><br>
> > ><br>
> > > ______________________________<wbr>_________________<br>
> > > Pulp-dev mailing list<br>
> > > <a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a> <mailto:<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a>><br>
</span>> <mailto:<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a> <mailto:<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a>>><br>
<span class="">> > > <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
> <<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a>><br>
> > <<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
> <<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a>>><br>
> > ><br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > _____________________________<wbr>__________________<br>
> > Pulp-dev mailing list<br>
> > <a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a> <mailto:<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a>><br>
</span>> <mailto:<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a> <mailto:<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a>>><br>
<div class="HOEnZb"><div class="h5">> > <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
> <<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a>><br>
> > <<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
> <<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a>>><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > Pulp-dev mailing list<br>
> > <a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a> <mailto:<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a>><br>
> > <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
> <<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a>><br>
> ><br>
> <br>
> <br>
> <br>
> ______________________________<wbr>_________________<br>
> Pulp-dev mailing list<br>
> <a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a> <mailto:<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a>><br>
> <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
> <<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a>><br>
> <br>
> <br>
<br>
<br>
</div></div></blockquote></div><br></div></div>