This method will allow MechanismDrivers to start their own RPC listeners, if they require some, e.g. for communication between the driver and a custom agent. It is added as an alternative to create the backends in initialize(), as in cases where a driver is split up into the API and RPC part we want to make sure these backends are only started in the RPC part of neutron. start_rpc_listeners() is modeled after NeutronPluginBaseV2.start_rpc_listeners() and will be called as part of start_rpc_listeners() of the Ml2Plugin. Change-Id: I5c50305bd3273318a1cdf393bbda9d33bdd91e4d Partial-Bug: #2065198
8 lines
250 B
YAML
8 lines
250 B
YAML
---
|
|
other:
|
|
- |
|
|
MechanismDrivers can now start their own RPC listeners by implementing
|
|
start_rpc_listeners(). It is preferred to use this method instead of
|
|
initialize() for this task to support the split between RPC and
|
|
API workers.
|