bagpipe: compatibility with Neutron routers

Code Issues Proposed changes

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

This commit is contained in:

Thomas Morin

2016年09月13日 14:31:07 +02:00

parent aa84b4549c

commit 17875b86fb

4 changed files with 274 additions and 165 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/bagpipe/index.rst

View File

@@ -41,12 +41,6 @@ interface of a network associated to a BGP VPN.

Similarly, the driver will not bind a port on an external network. This behavior will be

revisited once a use case is well identified.

On Networks both associated to a BGP VPN and attached to a router

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

A network associated to a bgpvpn will loose access to its gateway, hence to any network

accessible behind its router which holds this gateway.

How to use ?

------------

bagpipe: compatibility with Neutron routers

6 doc/source/bagpipe/index.rst Unescape Escape View File

6
doc/source/bagpipe/index.rst

View File