yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1424722@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

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

Title:
  neuton should instantiate a oslo.messaging transport after fork

Status in neutron:
  Expired

Bug description:
  As per
  http://docs.openstack.org/developer/oslo.messaging/transport.html,

  "oslo.messaging can’t ensure that forking a process that shares the
  same transport object is safe for the library consumer, because it
  relies on different 3rd party libraries that don’t ensure that. In
  certain cases, with some drivers, it does work"

  In neutron, we initialize transport object before forking workers. We
  do it by calling to neutron.common.rpc:init, which is called from
  neutron.common.config:init, which is called BEFORE we call
  neutron.service:serve_rpc which actually forks workers.

  Note that in neutron case, it's not a matter of moving the
  initialization a bit lower due to the way how plugins are
  instantiated.

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