yahoo-eng-team team mailing list archive

[Frode Nordahl <1932154@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I just realized that we have submitted a spec [0] without following the
Neutron RFE process [1].

I'll repeat the summary here:

Off-path SmartNIC DPUs introduce an architecture change where network
agents responsible for NIC switch configuration and representor
interface plugging run on a separate SoC with its own CPU, memory and
that runs a separate OS kernel. The side-effect of that is that
hypervisor hostnames no longer match SmartNIC DPU hostnames which are
seen by ovs-vswitchd and OVN agents while the existing port binding
code relies on that. The goal of this specification is to introduce
changes necessary to extend the existing hardware offload code to cope
with the hostname mismatch and related design challenges while reusing
the rest of the code. To do that, PCI(e) add-in card tracking is
introduced for boards with unique serial numbers so that it can be used
to determine the correct hostname of a SmartNIC DPU which is responsible
for a particular VF. Additionally, more information is suggested to be
passed in the "binding:profile" during a port update to facilitate
representor port plugging.

We would be happy to attend the Neutron drivers meeting to discuss the
details.

0: https://review.opendev.org/c/openstack/neutron-specs/+/788821
1: https://docs.openstack.org/neutron/latest/contributor/policies/blueprints.html#neutron-request-for-feature-enhancements

Nova spec: https://review.opendev.org/c/openstack/nova-specs/+/787458
Nova BP: https://blueprints.launchpad.net/nova/+spec/integration-with-off-path-network-backends

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1932154

Title:
  [rfe] Off-path SmartNIC Port Binding

Status in neutron:
  New

Bug description:
  I just realized that we have submitted a spec [0] without following
  the Neutron RFE process [1].

  I'll repeat the summary here:

  Off-path SmartNIC DPUs introduce an architecture change where network
  agents responsible for NIC switch configuration and representor
  interface plugging run on a separate SoC with its own CPU, memory and
  that runs a separate OS kernel. The side-effect of that is that
  hypervisor hostnames no longer match SmartNIC DPU hostnames which are
  seen by ovs-vswitchd and OVN agents while the existing port binding
  code relies on that. The goal of this specification is to introduce
  changes necessary to extend the existing hardware offload code to cope
  with the hostname mismatch and related design challenges while reusing
  the rest of the code. To do that, PCI(e) add-in card tracking is
  introduced for boards with unique serial numbers so that it can be used
  to determine the correct hostname of a SmartNIC DPU which is responsible
  for a particular VF. Additionally, more information is suggested to be
  passed in the "binding:profile" during a port update to facilitate
  representor port plugging.

  We would be happy to attend the Neutron drivers meeting to discuss the
  details.

  0: https://review.opendev.org/c/openstack/neutron-specs/+/788821
  1: https://docs.openstack.org/neutron/latest/contributor/policies/blueprints.html#neutron-request-for-feature-enhancements

  Nova spec: https://review.opendev.org/c/openstack/nova-specs/+/787458
  Nova BP: https://blueprints.launchpad.net/nova/+spec/integration-with-off-path-network-backends

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