Bagpipe driver: use Neutron registry not an ML2 MD
This change makes the bagpipe driver use the Neutron
registry callbacks instead of a custom ML2 mech driver.
The now obsolete bgpvpn_notify mech driver still exists
to avoid breaking past configs, but it is empty and logs
a warning on startup.
With this change, the bagpipe driver also stops
preventing network deletion, because without a mech driver
we can't, which is good since it fixes bug 1489881.
This change also changes the behavior to ignore DHCP ports.
Reviewed: https:/ /review. openstack. org/221007 /git.openstack. org/cgit/ openstack/ networking- bgpvpn/ commit/ ?id=9dac6d33216 81b3619f4b96bb7 801c2c7e4cd611
Committed: https:/
Submitter: Jenkins
Branch: master
commit 9dac6d3321681b3 619f4b96bb7801c 2c7e4cd611
Author: Thomas Morin <email address hidden>
Date: Wed Jul 1 12:10:10 2015 +0200
Bagpipe driver: use Neutron registry not an ML2 MD
This change makes the bagpipe driver use the Neutron
registry callbacks instead of a custom ML2 mech driver.
The now obsolete bgpvpn_notify mech driver still exists
to avoid breaking past configs, but it is empty and logs
a warning on startup.
With this change, the bagpipe driver also stops
preventing network deletion, because without a mech driver
we can't, which is good since it fixes bug 1489881.
This change also changes the behavior to ignore DHCP ports.
Implements: blueprint bagpipe- use-neutron- registry f9768f4546118cb 311fbfbdb51
Closes-Bug: 1489881
Partial-Bug: 1492349
Change-Id: I0dcfbadd222ad1