Open Stack

Ben, yes, we submitted nsh support patch set last year, but ovs community told me we have to push kernel part into Linux kernel tree, we're struggling to do this, but something blocked us from doing this.

Recently, ovs did some changes in tunnel protocols which requires the packet decapsulated by a tunnel must be a Ethernet packet, but Linux kernel (net-next) tree accepted VxLAN-gpe patch set from Redhat guy (Jiri Benc) which requires the packet decapsulated by VxLAN-gpe port must be L3 packet but not L2 Ethernet packet, this blocked us from progressing better.

Simon Horman (Netronome guy) has posted a series of patches to remove the mandatory requirement from ovs in order that the packet from a tunnel can be any packet, but so far we didn't see they are merged.

I heard ovs community looks forward to getting nsh patches merged, it will be great if ovs guys can help progress this.

-----Original Message-----
From: Ben Pfaff [mailto:blp at ovn.org] 
Sent: Tuesday, May 31, 2016 10:38 PM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

On Mon, May 30, 2016 at 10:12:34PM -0400, Paul Carver wrote:
> I don't know the details of why OvS hasn't added NSH support so I 
> can't judge the validity of the concerns, but one way or another there 
> has to be a production-quality dataplane for networking-sfc to front-end.

It looks like the last time anyone submitted NSH patches to Open vSwitch was September 2015.  They got some reviews but no new version has been posted since.

Basically, we can't add NSH support if no one submits patches.

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev