3f3874717c
This is an initial patch in a series that, by using an event framework, cleans up the relationship between ML2 and L3, so that they are no longer tightly coupled. A follow-up will take address the coupling during the port delete operation. The newly introduced notification hooks not only benefit the L3 service plugin, but any other plugin that has an interest in knowing about port events. Long term, the notification bits can move in a more 'common' place so that other plugins can take advantage of them, but as mentioned in a parent patch, the perestroika is not quite there yet. Related-blueprint: services-split Related-blueprint: plugin-interface-perestroika Change-Id: I6527b1cb53a71a1f68329a7a3b1878094558f8c2 |
||
|---|---|---|
| .. | ||
| firewall | ||
| l3_router | ||
| loadbalancer | ||
| metering | ||
| vpn | ||
| __init__.py | ||
| advanced_service.py | ||
| provider_configuration.py | ||
| service_base.py | ||