[openstack-dev] [neutron] Regarding Flow classifiers existing proposals

Vikram Choudhary vikram.choudhary at huawei.com
Tue Jun 23 05:06:32 UTC 2015

Hi All,

We have started a etherpad link [1]  for collecting various use-cases about flow-classifier.
Request all to provide their opinion on the same. We will be discussing the same over SFC IRC meeting [2].
Any contribution will be appreciated.

[1] Etherpad Link

[2] SFC IRC Meeting


From: Vikram Choudhary
Sent: 05 June 2015 14:42
To: 'Miguel Angel Ajo'
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: RE: [neutron] Regarding Flow classifiers existing proposals

Thanks Miguel!

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<mailto:azama-yuji at mxe.nes.nec.co.jp>; Henry Fourie; Cathy Zhang; armamig at gmail.com<mailto:armamig at gmail.com>; Dongfeng (C); Kyle Mestery; openstack-dev at lists.openstack.org<mailto: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.

Best regards,
Miguel Ángel Ajo

On Friday 5 June 2015 at 09:57, Vikram Choudhary wrote:

Dear All,

There are multiple proposal floating around flow classifier rules for Liberty [1], [2] and [3].

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 [2] 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.

[1] Add Neutron API extensions for packet forwarding


[2] Neutron API for Service Chaining [Flow Filter resource]


[3] 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...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150623/e00716a3/attachment.html>

More information about the OpenStack-dev mailing list