Hassle-free migration from OVS to OVN
summary
Procedure for switching Neutron from ML2+Open vSwitch to OVN with concrete steps and timings. Requires upgrading Neutron (Ussuri), enabling the Open vSwitch firewall driver, adjusting MTU for Geneve overhead (38 bytes) or reducing guest MTU via DHCP, running neutron-ovn-db-sync after adding OVN central components, cleaning OVS bridges and namespaces, then starting OVN controllers. Demo uses charms automation on a three-node hyperconverged cluster with 1000 instances across 100 projects and records about 25 minutes control-plane downtime and ~3 minutes per-hypervisor data-plane downtime.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:22OVN introduction
- 5:08Prerequisites
- 6:02MTU
- 7:58Migration
- 9:45Manual migration
- 12:09Cleanup tool
- 12:59Instances
- 13:37Getting ready
- 14:18Adding OVN
- 15:42Progress
- 16:51Testing
related talks
36mMigrating the Neutron backend to OVN in production
01h 16mTroubleshooting OpenStack Neutron with ML2/OVN backend driver
47mFrom NSX to OVN: Four Years of Prep and a Live Cloud Migration
19mAdvanced Network management with oVirt and OVN
36mOVN-Kubernetes The new default CNI of OpenShift
51mOVN: Integrating an Off-the-Shelf SDN into a Virtualization Platform
18mSmartNIC DPU Enablement in OpenStack with OVN
23mOptimizing Live-Migration for Minimizing Packet Loss With KubeVirt and...