<div dir="ltr">Thanks Salv. I'll add an item to tomorrow's meeting agenda to discuss this a bit more and come up with a plan.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 10, 2015 at 2:39 AM, Salvatore Orlando <span dir="ltr"><<a href="mailto:salv.orlando@gmail.com" target="_blank">salv.orlando@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"><div><div>Kyle,<br><br></div>I can speak very little about the QoS branch, but from what I gather it is mature enough to be merged back.<br></div><div>However, I believe the Pecan work is still incomplete as we need a solution to run the RPC over AMQP server independently. Once we have that we can start merging back what we have.<br><br></div><div>Salvatore<br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On 8 August 2015 at 04:39, Kyle Mestery <span dir="ltr"><<a href="mailto:mestery@mestery.com" target="_blank">mestery@mestery.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="h5"><div dir="ltr"><div><div><div>As we're beginning to wind down Liberty-3 in a few weeks, I'd like to present the rough, high level plan to merge back the QoS and pecan branches into Neutron. Ihar has been doing a great job shepherding the QoS work, and I believe once we're done landing the final patches this weekend [1], we can look to merge this branch back next week.<br><br></div>The pecan branch [2] has a few patches left, but it's also my understanding from prior patches we'll need some additional testing done. Kevin, what else is left here? I'd like to see if we could merge this branch back the following week. I'd also like to hear your comments on enabling the pecan WSGI layer by default for Liberty and what additional testing is needed (if any) to make that happen.<br><br></div>Thanks!<br></div>Kyle<br><div><div><div><br>[1] <a href="https://review.openstack.org/#/q/project:openstack/neutron+branch:feature/qos+status:open,n,z" target="_blank">https://review.openstack.org/#/q/project:openstack/neutron+branch:feature/qos+status:open,n,z</a><br>[2] <a href="https://review.openstack.org/#/q/project:openstack/neutron+branch:feature/pecan+status:open,n,z" target="_blank">https://review.openstack.org/#/q/project:openstack/neutron+branch:feature/pecan+status:open,n,z</a><br></div></div></div></div>
<br></div></div>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>