yahoo-eng-team team mailing list archive

[Rodolfo Alonso <2102090@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Since the migration of the Neutron API to the WSGI module, the ML2/OVN
Placement extension method ``read_initial_chassis_config`` is not
executed when the Neutron API is restarted. This method is called from
``OvnSbSynchronizer.do_sync``, but this class and method is no longer
called from the Neutron API process but from the maintenance process
(now these are two separate processes).

The aim of this bug is to implement the Placement initial configuration
on the Neutron API.

**NOTE**: this architectural proposal needs to be agreed upon by the
Neutron maintainer members. This is NOT a bug but a possible
improvement.

** Affects: neutron
     Importance: Undecided
         Status: New

** Description changed:

  Since the migration of the Neutron API to the WSGI module, the ML2/OVN
  Placement extension method ``read_initial_chassis_config`` is not
  executed when the Neutron API is restarted. This method is called from
  ``OvnSbSynchronizer.do_sync``, but this class and method is no longer
  called from the Neutron API process but from the maintenance process
  (now these are two separate processes).
  
  The aim of this bug is to implement the Placement initial configuration
  on the Neutron API.
  
  **NOTE**: this architectural proposal needs to be agreed upon by the
- Neutron maintainer members.
+ Neutron maintainer members. This is NOT a bug but a possible
+ improvement.

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

Title:
  [OVN][Placement] With Neutron API WSGI module, the initial chassis
  configuration is not executed

Status in neutron:
  New

Bug description:
  Since the migration of the Neutron API to the WSGI module, the ML2/OVN
  Placement extension method ``read_initial_chassis_config`` is not
  executed when the Neutron API is restarted. This method is called from
  ``OvnSbSynchronizer.do_sync``, but this class and method is no longer
  called from the Neutron API process but from the maintenance process
  (now these are two separate processes).

  The aim of this bug is to implement the Placement initial
  configuration on the Neutron API.

  **NOTE**: this architectural proposal needs to be agreed upon by the
  Neutron maintainer members. This is NOT a bug but a possible
  improvement.

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