vmware-nsx/neutron/services/l3_router
Ihar Hrachyshka cc6eff30d7 Introduced rpc_compat.create_connection()
This will be used to emulate oslo-rpc API using oslo.messaging.

blueprint oslo-messaging

Change-Id: I2c1aa159132e4aad0138d4b0b7ff90eb98ed400c
2014-06-16 12:44:22 +02:00
..
__init__.py Adds support for L3 routing/NAT as a service plugin 2013-09-11 12:12:10 +02:00
l3_apic.py Cisco APIC Layer 3 Service plugin 2014-06-04 08:37:06 -07:00
l3_router_plugin.py Introduced rpc_compat.create_connection() 2014-06-16 12:44:22 +02:00
README Adds support for L3 routing/NAT as a service plugin 2013-09-11 12:12:10 +02:00

This service plugin implements the L3 routing functionality (resources router
and floatingip) that in earlier releases before Havana was provided by core
plugins (openvswitch, linuxbridge, ... etc).

Core plugins can now choose not to implement L3 routing functionality and
instead delegate that to the L3 routing service plugin.

The required changes to a core plugin are in that case:
- Do not inherit 'l3_db.L3_NAT_db_mixin' (or its descendants like extraroute)
  anymore.
- Remove "router" from 'supported_extension_aliases'.
- Modify any 'self' references to members in L3_NAT_db_mixin to instead use
  'manager.NeutronManager.get_service_plugins().get(constants.L3_ROUTER_NAT)'
  For example,
     self.prevent_l3_port_deletion(...)
  becomes something like
     plugin = manager.NeutronManager.get_service_plugins().get(
         constants.L3_ROUTER_NAT)
     if plugin:
         plugin.prevent_l3_port_deletion(...)

If the core plugin has relied on the L3Agent the following must also be changed:
- Do not inherit 'l3_rpc_base.L3RpcCallbackMixin' in any '*RpcCallbacks' class.
- Do not be a consumer of the topics.L3PLUGIN topic for RPC.

To use the L3 routing service plugin, add
'neutron.services.l3_router.l3_router_plugin.L3RouterPlugin'
to 'service_plugins' in '/etc/neutron/neutron.conf'.
That is,
service_plugins = neutron.services.l3_router.l3_router_plugin.L3RouterPlugin