yahoo-eng-team team mailing list archive

[OpenStack Infra <2083456@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/931067
Committed: https://opendev.org/openstack/neutron/commit/1300110ccb9963e48a7c19e70599194d5c7da92c
Submitter: "Zuul (22348)"
Branch:    master

commit 1300110ccb9963e48a7c19e70599194d5c7da92c
Author: Jakub Libosvar <libosvar@xxxxxxxxxx>
Date:   Tue Oct 1 16:54:18 2024 -0400

    Set distributed flag to NB_Global
    
    The patch introduces a new maintenance routine that always sets
    NB_Global.external_ids:fip-distributed value in Northbound OVN DB to the
    same value that enable_distributed_floating_ip config option has.
    
    This is useful for projects that do not use RPC and rely on data only in
    the OVN database.
    
    Closes-Bug: #2083456
    Change-Id: I7f30e6e030292b762dc9fc785c494c0dc215c749
    Signed-off-by: Jakub Libosvar <libosvar@xxxxxxxxxx>


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

Title:
  Unable to detect from OVN DB if Neutron uses distributed floating IPs
  or not

Status in neutron:
  Fix Released

Bug description:
  Actually I don't know if this should be an RFE or a bug.

  Previously Neutron set external_mac in a NAT entry if the floating IP
  was distributed and it was left unset if the traffic was centralized.
  Nowadays, the behavior is inconsistent and external_mac is set after
  the port associated with the FIP transitions to the UP state - meaning
  that while the port is down, we are not able to say if the traffic
  will be distributed or not.

  It would be good to have this configuration option stored at one place
  - for example NB_Global.external_ids column can store a value for
  distributed routing since it's a global option for the whole Neutron.
  There are projects, like ovn-bgp-agent that could use this information
  before-hand so the agent knows if the floating IP should be exposed on
  the compute node or on the network node.

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