yahoo-eng-team team mailing list archive

[OpenStack Infra <2052821@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/909194
Committed: https://opendev.org/openstack/neutron/commit/25a1809964f4845d98d9b3d05148b764a65c9458
Submitter: "Zuul (22348)"
Branch:    master

commit 25a1809964f4845d98d9b3d05148b764a65c9458
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Sun Feb 11 18:50:55 2024 +0000

    [OVN] "Logical_Router" pinned to chassis, OVN L3 scheduler
    
    Pin a "Logical_Router" to a chassis when the gateway network (external
    network) is tunnelled. When the external network is tunnelled, the
    "Logical_Router_Port" acting as gateway port is not bound to any
    chassis (the network has no physical provider network defined).
    
    In that case, the router is pinned to a chassis instead. A
    "HA_Chassis_Group" is created per router. The highest "HA_Chassis" of
    this group is assigned to the router. If the gateway port is deleted,
    the pinned chassis is removed from the "options" field. If the
    router is deleted, the "HA_Chassis_Group" is deleted too.
    
    NOTE: in the a chassis belonging to the router "HA_Chassis_Group"
    changes, the list of "HA_Chassis" will be updated in
    ``ChassisEvent.handle_ha_chassis_group_changes``. However, a
    "HA_Chassis_Group" change is handled by OVN, when assiged.
    
    But in this case we are using this artifact, as commented before,
    to "manually assign" (from core OVN point of view) the highest
    priority "HA_Chassis" to the router (this upcoming funcionality
    will be implemented in core OVN). A new follow-up patch will be
    pushed to provide HA functionality and update the "HA_Chassis"
    assigned to the "Logical_Router" when the chassis list changes.
    
    Partial-Bug: #2052821
    Change-Id: I33555fc8a8441149b683ae68f1f10548ffb662a6


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

Title:
  [OVN] Pin a Logical_Router to a chassis when the external network is
  tunnelled

Status in neutron:
  Fix Released

Bug description:
  When a gateway network (external network) is added to a router (OVN
  Logical_Router), a gateway port (OVN Logical_Router_Port) is created.
  If the router GW network is a tunnelled network, the GW LRP won't be
  bound to any GW chassis; the network has no physical network thus
  there is no correspondence with any GW physical bridge. Check [1] for
  more information.

  In order to be able to send traffic through a GW chassis, it is needed to pin the LR to a chassis manually:
    LR:options:chassis=<GW chassis UUID>

  Note: there is a proposal [3] to make this functionality a core OVN
  functionality, being able to assign a "HA_Chassis_Group" to a Logical
  Router. This LP bug wants to implement the same functionality but in
  the Neutron code.

  [1]https://review.opendev.org/c/openstack/neutron/+/908325

  References:
  [2]https://bugzilla.redhat.com/show_bug.cgi?id=2259161
  [3]https://issues.redhat.com/browse/FDP-365

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