Re: [openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator

2014-08-20 Thread Luke Gorrie
On 19 August 2014 23:15, Alan Kavanagh wrote: > +1, I am hoping this is just a short term holding point and this will > eventually be merged into main branch as this is a feature a lot of > companies, us included would definitely benefit from having supported and > many thanks to Sean for stickin

Re: [openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator

2014-08-20 Thread Mathieu Rohon
this. >> /Alan >> >> -Original Message- >> From: Collins, Sean [mailto:sean_colli...@cable.comcast.com] >> Sent: August-19-14 8:33 PM >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: [openstack-dev] [Neutron][QoS] Req

Re: [openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator

2014-08-20 Thread Wuhongning
ation binding, without reinvent these overlapped concept. From: Salvatore Orlando [sorla...@nicira.com<mailto:sorla...@nicira.com>] Sent: Wednesday, August 20, 2014 6:12 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][QoS]

Re: [openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator

2014-08-19 Thread Kevin Benton
einvent these overlapped concept. > > -- > *From:* Salvatore Orlando [sorla...@nicira.com] > *Sent:* Wednesday, August 20, 2014 6:12 AM > > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Neutron][

Re: [openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator

2014-08-19 Thread Wuhongning
e overlapped concept. From: Salvatore Orlando [sorla...@nicira.com] Sent: Wednesday, August 20, 2014 6:12 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator In the

Re: [openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator

2014-08-19 Thread Salvatore Orlando
ean for sticking with this and continue to push this. > /Alan > > -Original Message- > From: Collins, Sean [mailto:sean_colli...@cable.comcast.com] > Sent: August-19-14 8:33 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev] [Neutr

Re: [openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator

2014-08-19 Thread Alan Kavanagh
-Original Message- From: Collins, Sean [mailto:sean_colli...@cable.comcast.com] Sent: August-19-14 8:33 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator Hi, The QoS API extension has lived

Re: [openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator

2014-08-19 Thread Robert Kukura
Actually, whether the incubator is involved for not, this might be a great candidate for implementation using an ML2 extension driver. See https://review.openstack.org/#/c/89211/ for the code under review for Juno, and also https://docs.google.com/a/noironetworks.com/document/d/14T-defRnFl6M2xR

Re: [openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator

2014-08-19 Thread Kevin Benton
+1. This work in particular brings up a question about the incubator. One of the rules was that the neutron core code can't import code from the incubated projects. The QoS requires a mixin to annotate the port and network objects with QoS settings. How exactly would we actually use the QoS code f

[openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator

2014-08-19 Thread Collins, Sean
Hi, The QoS API extension has lived in Gerrit/been in review for about a year. It's gone through revisions, summit design sessions, and for a little while, a subteam. I would like to request incubation in the upcoming incubator, so that the code will have a more permanent "home" where we can coll