yahoo-eng-team team mailing list archive

[OpenStack Infra <2078382@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/917800
Committed: https://opendev.org/openstack/neutron/commit/44cbbba369ad12bfdc8276319c7bcea173ddaa96
Submitter: "Zuul (22348)"
Branch:    master

commit 44cbbba369ad12bfdc8276319c7bcea173ddaa96
Author: Miguel Lavalle <mlavalle@xxxxxxxxxx>
Date:   Tue Apr 30 20:15:23 2024 -0500

    User defined router flavor driver with no LSP
    
    There is a use case where a user defined router flavor requires router
    interfaces that don't have a corresponding OVN LSP. In this use case,
    Neutron acts only as an IP address manager for the router interfaces.
    
    This change adds a user defined router flavor driver that implements
    the described use case. The new functionality is completely contained in
    the new driver, with no logic added to the rest of ML2/OVN. This is
    accomplished as follows:
    
    1) When an interface is added to a router, the driver deletes the LSP
    and the OVN revision number.
    
    2) When an interface is about to be removed from a router, the driver
    re-creates the LSP and the OVN revision number. In this way, ML2/OVN
    can later delete the port normally.
    
    Closes-Bug: #2078382
    
    Change-Id: I14d675af2da281cc5cd435cae947ccdb13ece12b


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

Title:
  [OVN] User defined router flavor with no LSP associated to router
  interfaces

Status in neutron:
  Fix Released

Bug description:
  There is at least one OpenStack operator that requires the ability to
  create a ML2/OVN user defined router flavor that doesn't have Logical
  Switch Ports associated to their router interfaces. This allows a user
  defined flavor driver to process traffic bypassing the OVN pipeline.
  In this use case, Neutron acts only as an IP address manager for the
  router interfaces.

  The associated functionality shouldn't conflict with the ML2/OVN
  mechanism manager when deleting the associated Neutron ports, which
  would happen if the LSP is just removed without making provisions for
  the eventual removal of the router interface.

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