3.2. ML2/OVS to ML2/OVN in-place migration: validated and prohibited scenarios
Red Hat continues to test and refine in-place migration scenarios. Work with your Red Hat Technical Account Manager or Global Professional Services to determine whether your OVS deployment meets the criteria for a valid in-place migration scenario.
3.2.1. Validated ML2/OVS to ML2/OVN migration scenarios
- DVR to DVR
Start: RHOSP 16.1.1 or later with OVS with DVR. Geneve project (tenant) networks.
End: Same RHOSP version and release with OVN with DVR. Geneve project (tenant) networks.
SR-IOV and TLS-everywhere were not present in the starting environment or added during or after the migration.
- Centralized routing + SR-IOV with virtual function (VF) ports only
Start: RHOSP 16.1.1 or later with OVS (no DVR)and SR-IOV.
End: Same RHOSP version and release with OVN (no DVR) and SR-IOV.
Workloads used only SR-IOV virtual function (VF) ports. SR-IOV phyical function (PF) ports caused migration failure.