Open Stack

On 13 May 2016 at 16:01, Cathy Zhang <Cathy.H.Zhang at huawei.com> wrote:

> 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.
>

One can support NSH whichever way they see fit. NSH in OVS is not something
Neutron can do anything about. Neutron is about defining abstractions that
can apply to a variety of technologies and experiment with what open source
component is available on the shelves. Anyone can take the abstraction and
deliver whatever technology stack they want with it and we'd happily gather
any feedback to iterate on the abstraction to address more and more use
case.


>
>
> 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/b509fba5/attachment.html>