Hi On Wed, Aug 20, 2014 at 12:12 AM, Salvatore Orlando <sorla...@nicira.com> wrote: > In the current approach QoS support is being "hardwired" into ML2. > > Maybe this is not the best way of doing that, as perhaps it will end up > requiring every mech driver which enforces VIF configuration should support > it. > I see two routes. One is a mechanism driver similar to l2-pop, and then you > might have a look at the proposed extension framework (and partecipate into > the discussion). > The other is doing a service plugin. Still, we'll have to solve how to > implement the "binding" between a port/network and the QoS entity.
We have exactly the same issue while implementing the BGPVPN service plugin [1]. As for the Qos extension, the BGPVPN extension can extend network by adding route target infos. the BGPVPN data model has a foreign key to the extended network. If Qos is implemented as a service plugin, I assume that the architecture would be similar, with Qos datamodel having foreign keys to ports and/or Networks. When a port is created, and it has Qos enforcement thanks to the service plugin, let's assume that a ML2 Qos Mech Driver can fetch Qos info and send them back to the L2 agent. We would probably need a Qos Agent which communicates with the plugin through a dedicated topic. But when a Qos info is updated through the Qos extension, backed with the service plugin, the driver that implements the Qos plugin should send the new Qos enforcment to the Qos agent through the Qos topic. So I feel like implementing a core resource extension with a service plugin needs : 1 : a MD to interact with the service plugin 2 : an agent and a mixin used by the the L2 agent. 3 : a dedicated topic used by the MD and the driver of the service plugin to communicate with the new agent Am I wrong? [1]https://review.openstack.org/#/c/93329/ > If we go > for the approach we've chosen so far the resource extension model you still > have to deal with ML2 extensions. But I like orthogonality in services, and > QoS is a service to me. > Another arguable point is that we might want to reconsider our > abuse^H^H^H^H^H use of resource attribute extension, but this is a story for > a different thread. > > Regarding the incubator request, I think we need to wait for the process to > be "blessed". But you have my support and I would happy to help to assist > with this work item through its process towards graduation. > > This obviously provided the QoS team wants me to do that! > > Salvatore > > > On 19 August 2014 23:15, Alan Kavanagh <alan.kavan...@ericsson.com> 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 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] [Neutron][QoS] Request to be considered for >> neutron-incubator >> >> 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 >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
