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-defRnFl6M2xR5ZNFGYD6aIiAVWdd1Al9BnjV_JOs
for planned followup work that would enforce extension semantics during
port binding.
-Bob
On 8/19/14, 2:46 PM, Kevin Benton wrote:
+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 from the incubator since we can't import the mixins in
the ML2 plugin?
On Tue, Aug 19, 2014 at 11:33 AM, Collins, Sean
<[email protected]
<mailto:[email protected]>> wrote:
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
collaborate and
improve.
--
Sean M. Collins
_______________________________________________
OpenStack-dev mailing list
[email protected]
<mailto:[email protected]>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Kevin Benton
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
