Cathy Zhang <cathy.h.zh...@huawei.com> wrote:
Hi everyone,
Per Armando’s request, Louis and I are looking into the following
features for Newton cycle.
· Neutron Common FC used for SFC, QoS, Tap as a service etc.,
· OVS Agent extension
Some of you might know that we already developed a FC in networking-sfc
project and QoS also has a FC. It makes sense that we have one common FC
in Neutron that could be shared by SFC, QoS, Tap as a service etc.
features in Neutron.
I don’t actually know of any classifier in QoS. It’s only planned to
emerge, but there are no specs or anything specific to the feature.
Anyway, I agree that classifier API belongs to core neutron and should be
reused by all interested subprojects from there.
Different features may extend OVS agent and add different new OVS flow
tables to support their new functionality. A mechanism is needed to
ensure consistent OVS flow table modification when multiple features
co-exist. AFAIK, there is some preliminary work on this, but it is not a
complete solution yet.
I think there is no formal spec or anything, just some emails around there.
That said, I don’t follow why it’s a requirement for SFC to switch to l2
agent extension mechanism. Even today, with SFC maintaining its own agent,
there are no clear guarantees for flow priorities that would avoid all
possible conflicts.
We will like to start these effort by collecting requirements and then
posting specifications for review. If any of you would like to join this
effort, please chime in. We can set up a meet-up session in the Summit to
discuss this face-in-face.
Great. Let’s have a meetup for this topic.
Ihar
__________________________________________________________________________
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
