Comment 2 for bug 1932154
Revision history for this message
| Frode Nordahl (fnordahl) wrote Re: [rfe] Off-path SmartNIC Port Binding | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
At the core of the challenge is a requirement to support SmartNIC DPU
deployments with cards in restricted mode. In this mode we treat
the hypervisors as untrusted components which disallows direct
communication between Nova running on the host and components running
on the SmartNIC control plane CPUs.
Due to how these cards are laid out, information such as name of
representor ports are also not available from the host side, restricted
mode or not. So a component running on the SmartNIC control plane CPU
is required to discover names of representor ports and to perform
plugging on instance creation.
My understanding of the direction of the Neutron OVN driver is that the
traditional AMQP RPC and agent topology is being phased out, replaced by
native OVN functionality.
Following this theme, we are proposing to coordinate representor port
plugging through the OVN database and have the ovn-controller, or some
other OVN service, do the plugging. There is an RFC patch up for
discussion [0][1][2] and we have a target to complete that work for
OVN 21.09 if we reach agreement.
0: https:/
1: https:/
2: https:/