Open Stack

Kyle,

I can speak very little about the QoS branch, but from what I gather it is
mature enough to be merged back.
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.

Salvatore

On 8 August 2015 at 04:39, Kyle Mestery <mestery at mestery.com> wrote:

> 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.
>
> 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.
>
> Thanks!
> Kyle
>
> [1]
> https://review.openstack.org/#/q/project:openstack/neutron+branch:feature/qos+status:open,n,z
> [2]
> https://review.openstack.org/#/q/project:openstack/neutron+branch:feature/pecan+status:open,n,z
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150810/4fa1f297/attachment.html>