yahoo-eng-team team mailing list archive

[OpenStack Infra <1892477@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/707626
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1dddbbfc92b115bfd62e15081134a5cadbc15212
Submitter: Zuul
Branch:    master

commit 1dddbbfc92b115bfd62e15081134a5cadbc15212
Author: Lucas Alvares Gomes <lucasagomes@xxxxxxxxx>
Date:   Wed Feb 12 14:36:56 2020 +0000

    [OVN] Use the Chassis_Private table for agents healthcheck
    
    The core OVN team has introduced a new table called Chassis_Private to
    avoid nb_cfg flooding when checking for the Chassis' status. The OVN
    driver does rely on that mechanism for the agent liveness mechanism.
    
    This patch makes use of this new table but it's also backward
    compatible.
    
    For more information, check the core OVN changes at:
    https://patchwork.ozlabs.org/patch/1254394.
    
    Closes-Bug: #1892477
    Change-Id: Iea4263b852d1e3f81eb2557918ea3cbb7adb8016
    Signed-off-by: Lucas Alvares Gomes <lucasagomes@xxxxxxxxx>


** 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/1892477

Title:
  [OVN] Avoid nb_cfg update notification flooding during agents health
  check

Status in neutron:
  Fix Released

Bug description:
  The nb_cfg as a mechanism to "ping" OVN control plane is very useful
  in many ways. However, the current implementation will trigger update
  notifications flooding in the whole control plane. Each HV updates to
  SB the nb_cfg number and all these updates are notified to all the
  other HVs, which is O(n^2). Although updates are batched in fewers
  notifications than n^2, it still generates significant load on SB DB
  and also on ovn-controllers.

  In order to solve this problem the core OVN team created a new table
  called Chassis_Private that holds the private information for the
  chassis and is conditionally monitored by them. That way, updates to
  the nb_cfg column will not affect all other hypervisors.

  We need to make use of this new mechanism in the OVN driver.

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