[openstack-dev] [neutron] Regarding Flow classifiers existing proposals
vikram.choudhary at huawei.com
Fri Jun 5 09:11:43 UTC 2015
From: Miguel Angel Ajo [mailto:mangelajo at redhat.com]
Sent: 05 June 2015 14:12
To: Vikram Choudhary
Cc: azama-yuji at mxe.nes.nec.co.jp; Henry Fourie; Cathy Zhang; armamig at gmail.com; Dongfeng (C); Kyle Mestery; openstack-dev at lists.openstack.org; Dhruv Dhody; Kalyankumar Asangi
Subject: [neutron] Regarding Flow classifiers existing proposals
Added openstack-dev, where I believe this conversation must live.
I totally agree on this, thank you for bringing up this conversation. This is not something we want to do for QoS this cycle, but probably next cycle.
Anyway, an unified data model and API to create/update classifiers will not only be beneficial from the code duplication point of view, but will also provide a better user experience.
I’m all for it.
Miguel Ángel Ajo
On Friday 5 June 2015 at 09:57, Vikram Choudhary wrote:
There are multiple proposal floating around flow classifier rules for Liberty ,  and .
I feel we all should work together and try to address all our use case having a unified framework rather than working separately achieving the same goal.
Moreover, I can find the proposal for flow classifier as defined by the existing SFC  proposal is too generic and could address all the use cases by minor extension’s.
In this regard, I would like all to come forward, exchange their thoughts, work together and make it happen good the first go rather doing the same effort separately and end up in duplicating code & effort ☹.
I always feel less code will make our life happy in the long run ;)
Please let me know about your views.
 Add Neutron API extensions for packet forwarding
 Neutron API for Service Chaining [Flow Filter resource]
 QoS API Extension [Defines classifier rule in QoSRule. Classifier rule can really grow big in the long run]:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev