Bug Fixes¶

• The os-vif OVS plugin now supports using per-port OVS bridges when hybrid plugis not used. This is disabled by default and can be enabled by defining[os_vif_ovs]/per_port_bridge=True in the compute service nova.conf.This capability should only be enabled if you are deploying with ml2/ovnand experience packet loss during live migrations. This is not supportedon windows or when using ironic smartnic ports. This option was introducedto address bug: #1933517. When using OVN as a network backend OVNrequires the OVS interface to both have an ofport-id and the neutron portuuid defined in the external_ids field. When the port is plugged if[os_vif_ovs]/per_port_bridge is not enabled then the OVS port will notbe assigned an openflow port id until the tap device is created on the host.On loaded system with many flows and ports it can take a few second for OVNto detect the creation of the tap device and install the correct flows.During that interval packets can be dropped.When[os_vif_ovs]/per_port_bridge is enabled, os-vif will add the VM tapdevice to a new bridge that is connected to the integration bridge via apatch port. This enables OVN to install the openflow rules on theintegration bridge before the tap is created reducing the possibility forpacket loss during a live migration. By default per port bridges are disabledand this feature is considered experimental, however it will likely be enabledby default in the future after we gain experience with how this bridge topologyscales in larger deployments.