bagpipe-bgp: linux vxlan driver should reject if instance has same VNI than another instance

[Thomas Morin]

In some BGPVPN interconnection scenarios, two EVPNs may be configured for bagpipe-bgp with same VNI.

This can't be supported by the linux vxlan driver (only a single vxlan interface can be created for a given VXLAN id, and it can't be plugged in more than one bridge).

This would be supported by the EVPN OVS driver with some change.

For these reason, the right thing is to reject the creation of an EVPN instance having same VNI than another instance.

[Thomas Morin (tmmorin-orange)]

https://review.openstack.org/#/c/563541/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/563541
Committed: https://git.openstack.org/cgit/openstack/networking-bagpipe/commit/?id=64ff268ba651dbde6ff6c820d6682ef0591a1f75
Submitter: Zuul
Branch: master

commit 64ff268ba651dbde6ff6c820d6682ef0591a1f75
Author: Thomas Morin <email address hidden>
Date: Fri Apr 20 17:57:45 2018 +0200

    bagpipe-bgp: strictly avoid having same VNI in two VPN instances

    In some BGPVPN interconnection scenarios, two EVPNs may be
    configured for bagpipe-bgp with same VNI.

    This can't be supported by the linux vxlan driver (only a
    single vxlan interface can be created for a given VXLAN id,
    and it can't be plugged in more than one bridge).

    This would be supported by the EVPN OVS driver with some
    change.

    For these reason, the right thing is to reject the creation
    of an EVPN instance having same VNI than another instance.

    Closes-Bug: 1765764

    Change-Id: Ia36c0d17031042bada1df6945573cb2dabf5560a

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/networking-bagpipe 9.0.0.0b2 development milestone.