4824a714bf
This patch is adding support for a new port type called "external" in core OVN. Prior to this work, when a VM had a SR-IOV port attached to it, OVN itself wasn't able to reply to things such as DHCP requests packets since the OVS port was skipped. Core OVN then introduced the concept of "external" ports which are ports deployed on a different node than the one that the VM is running and is able to reply to such requests on behalf of the VM. With this patch, when a port with the VNIC type "direct" and no "switchdev" capability is created, ovn driver will then create a logical port with the type "external" for it and add it to a default HA Chassis Group. The port will then get bound to the "master" (higher priority) chassis of that group. Please note that, as a first step, this patch is creating only one HA Chassis Group which *all* external ports will belong to. That means that all external ports will be *scheduled onto the same node* (but it's HA nevertheless). In the future we should enhance this behavior. Change-Id: Ic6c4bb6c584682169f3ebd73105a847b05dddc76 Closes-Bug: #1841154 Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
12 lines
543 B
YAML
12 lines
543 B
YAML
---
|
|
features:
|
|
- |
|
|
The OVN driver now makes uses of the "external" ports concept
|
|
that was introduced by Core OVN. For example, with this work a VM
|
|
with a SR-IOV port attached (VNIC type "direct" and no "switchdev"
|
|
capability) will now be translated into an "external" port which is
|
|
able reply to packets (e.g DHCP) from another host that were bypassed
|
|
in the hypervisor before. Note that, for this first interaction all
|
|
external ports will belong to the same HA group and will be scheduled
|
|
onto the same node.
|