yahoo-eng-team team mailing list archive

[OpenStack Infra <2098085@xxxxxxxxxxxxxxxxxx>]

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

commit f352a4eb570dfcf25f62346a088425e2dab91d1a
Author: Andrew Bonney <andrew.bonney@xxxxxxxxx>
Date:   Tue Feb 11 15:18:35 2025 +0000

    ml2/sriov: bind port on segment that subnet belongs
    
    Follow up to change I56b22820d29b2d57faf28a2f9b685ab0b2c924b4
    
    Currently, if an SRIOV agent has access to multiple segments
    within a single routed provider network, the driver will always
    attach to the first segment it has access to. If a port has been
    explicitly associated with a subnet and hence a segment, this
    behaviour may not be correct.
    
    This patch makes use of the same feature now available in the
    base driver class and ensures that where a port is already
    associated with a subnet, the SRIOV driver attaches to the
    correct segment.
    
    Closes-Bug: #2098085
    Change-Id: I40a0de80ebf4ba2b32f0105a7b2d533ba13bc692


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

Title:
  SRIOV mechanism driver may attach to the wrong segment where a host
  has access to multiple segments of the same network

Status in neutron:
  Fix Released

Bug description:
  Since https://review.opendev.org/c/openstack/neutron/+/840418 and the
  related chain of changes, it has been possible to use Neutron for use
  cases where a single host has access to multiple segments of a single
  routed provider network, provided ports are already associated with a
  subnet. The original changes added support to the base class, but
  didn't cover the SRIOV driver which overrides the bind_port method
  (whilst for the most-part doing a similar set of tasks).

  We have found it useful to make use of this feature in our
  LXB+Caracal/Dalmation deployments, and I assume this may also be
  useful to OVS+SRIOV although I'm not familiar enough to know for sure.

  We have patched the SRIOV driver in a similar way via
  https://review.opendev.org/c/openstack/neutron/+/941345 and thought it
  worth sharing more widely.

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