← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1463129] [NEW] Plugins have no way to do post-api/rpc worker fork initialization

 

Public bug reported:

There are several classes of plugin initialization that need to be
handled *after* neutron server forks child processes for API/RPC
workers. For example, any client sockets that are set up for SDN
controllers pre-fork are broken in child processes since the file
descriptors are copied over, but both parent and child processes may try
to read/write to this fd. Also, if a thread is initiated pre-fork to
handle any polling or connection handling, child processes will not have
this thread after fork.

As an example, the networking-ovn project completely deadlocks when
api/rpc workers != 0.

** Affects: neutron
     Importance: Undecided
     Assignee: Terry Wilson (otherwiseguy)
         Status: In Progress

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

Title:
  Plugins have no way to do post-api/rpc worker fork initialization

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  There are several classes of plugin initialization that need to be
  handled *after* neutron server forks child processes for API/RPC
  workers. For example, any client sockets that are set up for SDN
  controllers pre-fork are broken in child processes since the file
  descriptors are copied over, but both parent and child processes may
  try to read/write to this fd. Also, if a thread is initiated pre-fork
  to handle any polling or connection handling, child processes will not
  have this thread after fork.

  As an example, the networking-ovn project completely deadlocks when
  api/rpc workers != 0.

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


Follow ups

References