start_rpc_listeners is usally called by a neutron.service.RpcWorker which is collected
by the neutron.service Manager. ML2 Plugins can provide their start_rpc_listener callback by returning
it via the ml2 mechanism get_workers() callback.
Why?
it's the neutron/openstack way to register the RPC consumer workers.
this way it honors the wsgi script that doesn't want the RPC consumers
to spawn, they should soley be handeled by the rpc-server.
start_rpc_listeners is usally called by a neutron.service.RpcWorker which is collected by the neutron.service Manager. ML2 Plugins can provide their start_rpc_listener callback by returning it via the ml2 mechanism get_workers() callback.
Why?