yahoo-eng-team team mailing list archive

[OpenStack Infra <2065198@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/919590
Committed: https://opendev.org/openstack/neutron/commit/6bb9535c452e14deefc50d563100418656a24f63
Submitter: "Zuul (22348)"
Branch:    master

commit 6bb9535c452e14deefc50d563100418656a24f63
Author: Sebastian Lohff <sebastian.lohff@xxxxxxx>
Date:   Tue May 14 16:55:00 2024 +0200

    Allow ml2 drivers to start their own RPC listeners
    
    To allow MechanismDrivers to start their own RPC listeners (e.g. for
    communication with custom agents) the MechanismManager will now call
    start_rpc_listeners() of each driver. This is done as part of
    Ml2Plugin.start_rpc_listeners(). 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.
    
    This patch depends on MechanismDrivers.start_rpc_listeners() in
    neutron-lib[0].
    
    [0] https://review.opendev.org/c/openstack/neutron-lib/+/919589
    
    Change-Id: I31e253180f474abf6d266d23c50f9dc89f17f687
    Depends-On: https://review.opendev.org/c/openstack/neutron-lib/+/919589
    Closes-Bug: #2065198


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
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:
  Fix Released

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