Hi Yi Yang, It is great that you establish contact. We have just started a new initiative to revive the work on upstreaming support for flexible (aka L3) tunneling and NSH support in OVS. Please have a look at the mail below. https://mail.openvswitch.org/pipermail/ovs-dev/2016-November/324788.html
I visited the OVS Fall Conference last week and talked to the OVS maintainers about this. Jesse has retired from VMware and it is now Pravin Shelar who is responsible in OVS for the NSH topic. Jiri Benc took over the L3 tunneling patches from Simon and he has just recently achieved that the kernel datapath patches were merged to the Linux net-next repository. https://mail.openvswitch.org/pipermail/ovs-dev/2016-November/325042.html Pravin and Jiri basically agree with us that the way forward for NSH is to implement support for Packet type-aware pipeline (EXT-112) and Generic Encap/Decap (EXT-382) in OVS as basis for introducing OpenFlow actions to push/pop NSH and Ethernet headers, as this is only the future-proof way to allow flexible handling of tunnel encapsulations in OF. The corresponding patches to OVS ofproto and dpif-netdev layer would supersede large parts of Simon's patches for the user-space, which do not go all the way to make the packet type available to the OF controller. The kernel datapath patches might also have to be refined a bit for that. The current NSH patches could then be based on that infrastructure. We would like to call for a conference call later this week with all interested parties discuss the technical solution and talk about how to split up the work. Timezone might be tricky, though (California, Europe, China). We'll have to see what we can do. In the meantime, we would greatly appreciate any comments to the technical proposal sketched in my earlier mail linked above. BR, Jan NB: that this initiative does not directly address issues with NSH MD2 support re-using Geneve TLV tunnel metadata infrastructure. We consider this a separate topic. We can discuss that as well, but from our point of view it has lower priority. We need to get the basic support for NSH over Ethernet and VXLAN-GPE in place first. From: Yang, Yi Y [mailto:[email protected]] Sent: Monday, 14 November, 2016 14:45 To: Jesse Gross <[email protected]> Cc: Jan Scheurich <[email protected]>; Yang, Yi Y <[email protected]> Subject: what is OVS NSH patchset merge status? Importance: High Hi, Jesse We're always waiting for Cascardo's "create tunnel devices using rtnetlink interface" patchset [1] merge and Simon's "userspace: Support for layer 3 encapsulated packets" patchset [2] merge, but so far we don't see any positive progress, I'm not sure they wouldn't like to continue to do them or they have given up their efforts because they think merging will be unexpectable. I want to know what current blocking issues are, I asked Simon and Cascardo, they didn't give any response, what happened? Our Johnson Li has given up this effort because he has no way to proceed, now I take over this hot potato :), I expect we can have some progress, I especially want to know what your concerns and what you think about it. [1] https://mail.openvswitch.org/pipermail/ovs-dev/2016-June/316879.html [2] https://mail.openvswitch.org/pipermail/ovs-dev/2016-June/234362.html _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
