Reviewed: https://review.opendev.org/c/openstack/neutron/+/808961 Committed: https://opendev.org/openstack/neutron/commit/7d64d0c116cf3f5ec2a35fb2ffe08dde61343ad8 Submitter: "Zuul (22348)" Branch: master
commit 7d64d0c116cf3f5ec2a35fb2ffe08dde61343ad8 Author: Frode Nordahl <[email protected]> Date: Tue Sep 14 14:33:29 2021 +0200 [OVN] Off-path SmartNIC DPU Port Binding with OVN Traditionally it has been the CMSs, in OpenStacks case Nova's, responsibility to create Virtual Interfaces (VIFs) as part of instance life cycle, and subsequently manage plug/unplug operations on the Open vSwitch integration bridge. With the advent of SmartNIC DPUs which are connected to multiple distinct CPUs we can have a topology where the instance runs on one host and Open vSwitch and OVN runs on a different host, the SmartNIC DPU control plane CPU. One of the main use cases for having this topology is security where we treat the hypervisor host as untrusted and prohibit direct communication between the hypervisor host and the SmartNIC DPU control plane host. In addition to that control facilities such as switchdev devices are only visible from the SmartNIC DPU control plane CPUs. Adds support for binding ports of type VNIC_REMOTE_MANAGED by looking up chassis based on serial number that Nova provides in the binding_profile. Information required by the OVN controller to successfully look up and plug representor port is provided as options on the LSP as defined by the representor plug provider documentation [0][1]. 0: https://docs.ovn.org/en/stable/topics/vif-plug-providers/vif-plug-providers.html 1: https://github.com/ovn-org/ovn-vif/blob/main/Documentation/topics/vif-plug-providers/vif-plug-representor.rst Partial-Bug: #1932154 Depends-On: I496db96ea40da3bee5b81bcee1edc79e1f46b541 Depends-On: I83a128a260acdd8bf78fede566af6881b8b82a9c Change-Id: Icc6c2d0f7f8f5cc94997db6244175a8e8884789f ** 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/1932154 Title: [rfe] Off-path SmartNIC Port Binding with OVN Status in neutron: Fix Released 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
