bagpipe driver: need to co-exist with Neutron routers

Bug #1627645 reported by Thomas Morin
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Thomas Morin

Bug Description

The bagpipe driver currently has a documented limitation that it can't
coexist with Neutron routers. If an association exists with a BGPVPN, the VMs
won't be able to reach subnets that would be reachable from a Router.
Another side-effect is that the Neutron router itself can't be joined, which
is blocking reachability of the metadata server, at least in some cases.

Tags: bagpipe
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-bgpvpn (master)

Fix proposed to branch: master

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-bgpvpn (master)

Submitter: Jenkins
Branch: master

commit 17875b86fb3ebb58f557e0aa51a97fb02c157dbd
Author: Thomas Morin <email address hidden>
Date: Tue Sep 13 14:31:07 2016 +0200

    bagpipe: compatibility with Neutron routers

    Add information on gateway MAC address to RPC notifications: when/if
    a router interface is plugged provide the gateway MAC address
    to the agent in RPCs.

    This change includes the Neutron server-side part of the solution, the
    agent-side evolution is covered in networking-bagpipe repo.

    Additionally, we remove a Router/Network check that has become
    redundant now that the check has been introduced in the plugin
    ( Ie1f6a733e8a16b8b41e89c5a82637d7cb03bd423 ).

    Partial-Bug: 1627645
    Change-Id: I89c07d9166f23d910542a825c5000fdd22580217

Changed in bgpvpn:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.