Hi Yuji, This is very similar to the flow classifier which has been proposed in https://review.openstack.org/#/c/177946. Since quite some people have reviewed and given comments on https://review.openstack.org/#/c/177946 and the latest version has incorporated those comments, I would suggest that you incorporate your input to https://review.openstack.org/#/c/177946 and work with LouisF and Vikram on driving and developing a unified flow classifier API and model.
Thanks, Cathy -----Original Message----- From: Yuji Azama [mailto:yuj-az...@rc.jp.nec.com] Sent: Wednesday, June 10, 2015 9:24 PM To: Cathy Zhang; Henry Fourie; mangel...@redhat.com; Vikram Choudhary Cc: arma...@gmail.com; Dongfeng (C); mest...@mestery.com; openstack-dev@lists.openstack.org; Dhruv Dhody; Kalyankumar Asangi Subject: RE: [neutron] Regarding Flow classifiers existing proposals Hello everyone, I want to join to IRC meeting. But I cannot join to the meeting because there is time difference. I tried to write my idea in spec of common classifier resource. ( https://review.openstack.org/#/c/190463 ) Thanks, Yuji -----Original Message----- From: Cathy Zhang [mailto:cathy.h.zh...@huawei.com] Sent: Saturday, June 06, 2015 3:36 AM To: Henry Fourie; Miguel Angel Ajo; Vikram Choudhary Cc: Azama Yuji(安座間 勇二); arma...@gmail.com; Dongfeng (C); Kyle Mestery; openstack-dev@lists.openstack.org; Dhruv Dhody; Kalyankumar Asangi Subject: RE: [neutron] Regarding Flow classifiers existing proposals Sure. I will add this item to the next IRC meeting agenda. Thanks, Cathy From: Henry Fourie Sent: Friday, June 05, 2015 11:27 AM To: Miguel Angel Ajo; Vikram Choudhary Cc: azama-y...@mxe.nes.nec.co.jp; Cathy Zhang; arma...@gmail.com; Dongfeng (C); Kyle Mestery; openstack-dev@lists.openstack.org; Dhruv Dhody; Kalyankumar Asangi Subject: RE: [neutron] Regarding Flow classifiers existing proposals Miguel, I agree, we can probably use the service-chaining meeting to discuss this. We can have it as an agenda item for the next meeting: http://eavesdrop.openstack.org/#Neutron_Service_Chaining_meeting - Louis From: Miguel Angel Ajo [mailto:mangel...@redhat.com] Sent: Friday, June 05, 2015 1:42 AM To: Vikram Choudhary Cc: azama-y...@mxe.nes.nec.co.jp; Henry Fourie; Cathy Zhang; arma...@gmail.com; Dongfeng (C); Kyle Mestery; openstack-dev@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 L. 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 https://review.openstack.org/#/c/186663/ <https://review.openstack.org/#/c/186663/> [2] Neutron API for Service Chaining [Flow Filter resource] https://review.openstack.org/#/c/177946/6/specs/liberty/neutron-api-fo r-service-chaining.rst <https://review.openstack.org/#/c/177946/6/specs/liberty/neutron-api-f or-service-chaining.rst> [3] QoS API Extension [Defines classifier rule in QoSRule. Classifier rule can really grow big in the long run]: https://review.openstack.org/#/c/88599/10/specs/liberty/qos-api-extens ion.rst <https://review.openstack.org/#/c/88599/10/specs/liberty/qos-api-exten sion.rst> Thanks Vikram __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev