yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1583299] [NEW] Add a Common Flow Classifier in Neutron

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: cathy Hong Zhang <cathy.h.zhang@xxxxxxxxxx>
Date: Wed, 18 May 2016 18:45:43 -0000
Reply-to: Bug 1583299 <1583299@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

[Existing problem]
Currently, multiple Stadium features inside Neutron need flow classifier functionality. In the future there could be more Neutron features that will need this functionality. Instead of each feature creating its own FC API and resource, we should have one common FC API and resource inside Neutron that can be used by all the networking features in OpenStack (inside or outside of Neutron stadium). This will avoid a lot of redundancy and maintenance issues.

[Proposal]
Currently the features that need FC are: Tap as a service, SFC, QoS, FW, BGP/VPN, GBP. There has been a meeting discussion in the Austin Summit (https://etherpad.openstack.org/p/Neutron-FC-OVSAgentExt-Austin-Summit). The interested party has a follow-on meeting discussion on 5/17/2016 (http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2016/network_common_flow_classifier.2016-05-17-17.02.html).

According to the consensus of the meeting, a new RFE for flow classifier
should be submitted in neutron-core and we will develop FC as a RFE over
neutron-core.

A general guideline on the FC design is that it should provide a
superset of FC rules used by existing features and the FC rules should
be easy to extend for new features in the future.

** Affects: neutron
Importance: Undecided
Status: New

** Tags: rfe

--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1583299

Title:
Add a Common Flow Classifier in Neutron

Status in neutron:
New

Bug description:
[Existing problem]
Currently, multiple Stadium features inside Neutron need flow classifier functionality. In the future there could be more Neutron features that will need this functionality. Instead of each feature creating its own FC API and resource, we should have one common FC API and resource inside Neutron that can be used by all the networking features in OpenStack (inside or outside of Neutron stadium). This will avoid a lot of redundancy and maintenance issues.

According to the consensus of the meeting, a new RFE for flow
classifier should be submitted in neutron-core and we will develop FC
as a RFE over neutron-core.

A general guideline on the FC design is that it should provide a
superset of FC rules used by existing features and the FC rules should
be easy to extend for new features in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1583299/+subscriptions