Comment 6 for bug 1932154

Reviewed: https://review.opendev.org/c/openstack/neutron-specs/+/788821
Committed: https://opendev.org/openstack/neutron-specs/commit/8ff7a77df9ec4fb3b5cb21ca42fc302b855a63fb
Submitter: "Zuul (22348)"
Branch: master

commit 8ff7a77df9ec4fb3b5cb21ca42fc302b855a63fb
Author: Dmitrii Shcherbakov <email address hidden>
Date: Thu Apr 29 21:35:04 2021 +0300

    Off-path SmartNIC Port Binding with OVN

    https://blueprints.launchpad.net/neutron/+spec/off-path-smartnic-dpu-port-binding-with-ovn

    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.

    WIP code: https://review.opendev.org/c/openstack/neutron/+/808961
    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

    Needed-By: I07ef52769da72cde8867f996111b7df4a80e4d79
    Change-Id: Ic8db22d1b6570f68bd6400ecc653dc893a4b6184
    Closes-Bug: #1932154