← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2098085] [NEW] SRIOV mechanism driver may attach to the wrong segment where a host has access to multiple segments of the same network

 

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
         Status: In Progress

-- 
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:
  In Progress

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



Follow ups