7d64d0c116
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 |
||
|---|---|---|
| .. | ||
| notes | ||
| source | ||