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 Container Cloud). This means everything you need is in one place. Some legacy names may remain in the code and documentation and will be updated in future releases. The separate Container Cloud documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

Verification and cleanup¶

After completing the migration from Open vSwitch (OVS) to Open Virtual Network (OVN), you must verify that the cloud is fully operational and remove temporary migration-related configurations and reference workloads. This step ensures that the environment is clean, consistent, and ready for production use.

To verify the environment and clean up migration settings:

Verify that the OpenStackDeployment custom resource reports status APPLIED.
Verify networking connectivity of reference workloads:
- Ping the floating IP addresses directly
- Verify workload availability in OpenStack
- Review the OpenStack Portprober dashboard
If applicable, verify reference workloads access to the Metadata service by logging in to instances through SSH and running, for example:
```
curl http://169.254.169.254
```
Remove reference workloads that were created during Prepare environment for migration.

Remove migration-related settings from the OpenStackDeployment custom resource. The migration utility patches this resource during its execution. After migration, delete the following keys from OpenStackDeployment:

From the root of spec, remove the migration:neutron:ovs_ovn_migration key.

From spec:services:networking, remove:

openvswitch:values:manifests:daemonset_ovn_controller
neutron:values:conf:dhcp_agent
neutron:values:conf:manifests:daemonset_metadata_agent
neutron:values:conf:manifests:deployment_server

Example of the spec:services:networking configuration before cleanup:

spec:
  services:
    networking:
      neutron:
        values:
          conf:
            dhcp_agent:
              DEFAULT:
                dhcp_lease_duration: 259200
                dhcp_renewal_time: 60
          manifests:
            daemonset_metadata_agent: true
            deployment_server: true
      openvswitch:
        values:
          manifests:
            daemonset_ovn_controller: true

From spec:services:compute, remove:

libvirt:values:pod:lifecycle:upgrades:daemonsets:pod_replacement_strategy
nova:values:pod:lifecycle:upgrades:daemonsets:pod_replacement_strategy

Example of the spec:services:compute configuration before cleanup:

services:
  compute:
    libvirt:
      values:
        pod:
          lifecycle:
            upgrades:
              daemonsets:
                pod_replacement_strategy: RollingUpdate
    nova:
      values:
        pod:
          lifecycle:
            upgrades:
              daemonsets:
                pod_replacement_strategy: RollingUpdate

After completing these steps, your environment will be running with OVN in a clean state, with all temporary migration settings removed. This ensures a stable and maintainable production environment.