Open Stack

Hi Cathy

Thank you for the quick response. This is the essence of my question – does Neutron keep OvS as a gold standard and why
And if so does that apply to stadium projects
As to OvS features, I guess the OvS ml is a better place, but wonder if the Neutron community wants to hold itself hostage to the pace of other projects who are reluctant to adopt a feature

At these point, standard organizations are almost done and open source can’t adopt a feature with high demand….

Thx

Uri (“Oo-Ree”)
C: 949-378-7568

From: Cathy Zhang [mailto:Cathy.H.Zhang at huawei.com]
Sent: Friday, May 13, 2016 4:02 PM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>; Armando M <armamig at gmail.com>
Subject: Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

Hi Uri,

Current networking-sfc API allows the user to specify the data path SFC encapsulation mechanism and NSH could be one of the encapsulation options.
But since OVS release has not supported the NSH yet, we have to wait until  NSH is added into OVS and then start to support the NSH encapsulation mechanism in the data path.

AFAIK, it is the position of Neutron to have any OVS related new features developed inside the OVS community.

Thanks,
Cathy

From: Elzur, Uri [mailto:uri.elzur at intel.com]
Sent: Friday, May 13, 2016 3:02 PM
To: OpenStack Development Mailing List (not for usage questions); Armando M
Subject: [openstack-dev] [Neutron] support of NSH in networking-SFC

Hi Armando

As an industry we are working on SFC for 3 years or so (more?). Still to date, we are told we can’t get Neutron or even a Stadium project e.g. networking-SFC to support NSH (in IETF LC phase) because OvS has not supported NSH. Is this an official position of Neutron that OvS is the gold standard to support any new feature?

We have seen OvS support other overlays that are not ahead of VXLAN-gpe in the IETF.

Thx

Uri (“Oo-Ree”)
C: 949-378-7568

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160513/678b7dc2/attachment.html>