yahoo-eng-team team mailing list archive

Thread
Date

[Bug 2065198] [NEW] Allow ml2 MechanismDrivers to start own rpc listeners

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Sebastian Lohff <2065198@xxxxxxxxxxxxxxxxxx>
Date: Wed, 08 May 2024 17:14:40 -0000
Reply-to: Bug 2065198 <2065198@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx

Public bug reported:

Some MechanismDrivers need their own RPC backend that can be used by an
agent to talk to this driver. When running in uwsgi/rpc mode we need to
make sure these RPCs listeners are started as part of the neutron-rpc-
server. Currently this is only done for service plugins, but
MechanismDrivers are part of the Ml2Plugin (which is itself a service
plugin).

To allow drivers to start their own RPC listener I propose that the
ML2Plugin takes care of this. Ml2Plugin can call
MechanismManager.start_driver_rpc_listeners(), which then calls
start_rpc_listeners() on each MechanismDriver. The resulting server
plugins could then also be returned as part of
Ml2Plugin.start_rpc_listeners().

I have a PoC for this running in my dev environment and if we agree on a
rough concept would be willing to provide a patch for this.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2065198

Title:
  Allow ml2 MechanismDrivers to start own rpc listeners

Status in neutron:
  New

Bug description:
  Some MechanismDrivers need their own RPC backend that can be used by
  an agent to talk to this driver. When running in uwsgi/rpc mode we
  need to make sure these RPCs listeners are started as part of the
  neutron-rpc-server. Currently this is only done for service plugins,
  but MechanismDrivers are part of the Ml2Plugin (which is itself a
  service plugin).

  To allow drivers to start their own RPC listener I propose that the
  ML2Plugin takes care of this. Ml2Plugin can call
  MechanismManager.start_driver_rpc_listeners(), which then calls
  start_rpc_listeners() on each MechanismDriver. The resulting server
  plugins could then also be returned as part of
  Ml2Plugin.start_rpc_listeners().

  I have a PoC for this running in my dev environment and if we agree on
  a rough concept would be willing to provide a patch for this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2065198/+subscriptions