Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!
Starting with MOSK 25.2, the MOSK documentation set covers all product layers, including MOSK management (formerly MCC). This means everything you need is in one place. The separate MCC documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.
Migrate networking from Open vSwitch to Open Virtual Network¶
Available since MOSK 25.2
This section describes the in-place migration of the MOSK cloud from the Neutron ML2 plugin with the Open vSwitch (OVS) mechanism driver to the Neutron ML2 plugin with the Open Virtual Network (OVN) mechanism driver. The procedure is designed to minimize downtime for user workloads.
Caution
Mirantis strongly recommends performing the preparation and migration of your networking from OVS to OVN in a staging environment before executing the procedure in production.
Testing the full migration in a staging environment that closely mirrors the target environment configuration is essential to identify potential issues early and minimize operational risk.
Additionally, no automated rollback to OVS is available. The only option is to restore the Neutron database from a backup. Such a rollback may cause significant downtime for user workloads, and the network state may remain inconsistent even after restoration.
Step |
Description |
|---|---|
0 |
Staging environment setup. Performing the preparation and migration of your networking in a staging environment. |
1 |
Pre-migration verification. |
2 |
Resolution of the failed checks. This may include adjustement of MTU for VXLAN tenant networks that, due to long default DHCP lease duration, may take more than 24 hours |
3 |
Increase of the DHCP lease time. Due to long default DHCP lease duration, may take more than 24 hours. |
4 |
Main maintenance window:
|
5 |
Verification and cleanup |
For a detailed description of each step, refer to the sections below.