[ovs-discuss] Problems with MPLS header pushing

[thomas.morin at orange.com]

Hi Ben,

2015-07-27, Ben Pfaff:
> If MPLS is going to work well in Open vSwitch, we need a developer to
> champion implementing and testing it.  None of the OVS developers right
> now have a use case for MPLS, so we don't use it and don't test it, and
> therefore don't find bugs, missing features, performance problems, etc.,
> and no one has incentive to improve the situation.

There are many people/projects based on OVS and needing an MPLS 
dataplane, in particular for use cases where OVS has to interconnect 
with IP/MPLS routers for BGP VPNs:
- the reference driver for networking-bgpvpn Neutron project
- work in progress in ODL for BGP VPN interconnection
- Nuage Networks solution

So I'm not pessimistic, I expect this to happen.
But 2.3 is likely to receive less interest.

> If you are able and willing to work on MPLS in OVS, please do!

Well I'll be humble here: without some support, my mastership of OVS in 
insufficient to allow me to dive in kernel/userspace interactions and 
fix things in an amount of time reasonable compared to how important 
MPLS is in the 2.3 branch.

In that particular case (trying to fix tat bug in the 2.3.x branch for 
MPLS) I could use some help: a hint on where to start to find why 
match->mask->key.ip.proto ends up being something else than 0xff in 
match_validate (datapath/flow_netlink.c).

-Thomas


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.