Migrating the Neutron backend to OVN in production
summary
Migration replaces the ML2 OVS mechanism with OVN by running a bash wrapper that calls TripleO + Ansible playbooks to deploy OVN DBs and controllers, stop ML2 agents, sync Neutron DB into OVN, and switch each node to BR-int. Preflight sets DHCP T1 to 30s and reduces instance MTU (example 1450→1442, MTU decreases by 8 bytes). Data-plane openflow rules jump (example ~39→536, openflow rules 39→536), observed SSH connectivity returns and measured downtime is about 1–2 seconds in tests.
AI-written summary · about
chapters (8)
- 0:00Introduction and overview
- 2:36Architecture differences
- 4:11Migration considerations
- 6:49Planning the migration
- 10:41Migration tooling
- 12:47Migration procedure steps
- 16:27Migration demo
- 29:48Q&A and conclusion
related talks
21mHassle-free migration from OVS to OVN
01h 16mTroubleshooting OpenStack Neutron with ML2/OVN backend driver
47mFrom NSX to OVN: Four Years of Prep and a Live Cloud Migration
28mPerformance optimization of Neutron server and Agent for large-scale scenario
23mOptimizing Live-Migration for Minimizing Packet Loss With KubeVirt and...
26mRun your Kubernetes cluster on OpenStack in Production
36mOVN-Kubernetes The new default CNI of OpenShift
19mAdvanced Network management with oVirt and OVN