]> review.fuel-infra Code Review - openstack-build/neutron-build.git/commit
Break coupling between ML2 and L3 during delete operation
authorarmando-migliaccio <armamig@gmail.com>
Fri, 6 Feb 2015 17:21:32 +0000 (09:21 -0800)
committerHenry Gessau <gessau@cisco.com>
Fri, 20 Mar 2015 12:48:53 +0000 (08:48 -0400)
commitbad541a0824a41579833c98e4af3bcdf63d4ee1a
treeddd15a243c712cfcddedcd1a311436808e9d9291
parent2d406067f8ef369fd72f979c33687edc68105a91
Break coupling between ML2 and L3 during delete operation

This is an initial attempt at breaking out the L3 logic from the ML2
framework as much as possible. This patch takes care of the notification
to the L3 agent(s), after a port has been deleted. Both base L3 and
L3+DVR operations are affected.

Related-blueprint: services-split
Related-blueprint: plugin-interface-perestroika

Change-Id: Ic41b87246ec4d89c2da49afaaccaeb8bd041dcb9
neutron/common/exceptions.py
neutron/db/l3_db.py
neutron/db/l3_dvrscheduler_db.py
neutron/extensions/l3.py
neutron/plugins/ml2/plugin.py
neutron/services/l3_router/l3_router_plugin.py
neutron/tests/unit/db/test_l3_dvr_db.py
neutron/tests/unit/ml2/test_ml2_plugin.py
neutron/tests/unit/test_l3_schedulers.py