NSX-MP to NSX-P Migration

In VMware Integrated OpenStack 7.3, the Neutron driver supports NSX-MP to NSX-P migration.

You can migrate your VMware Integrated OpenStack deployments leveraging NSX-T Management plane to NSX-T Policy Manager.

You can also leverage the NSX-T capabilities exposed only with Policy Manager such as IPv6 support with DHCPv6 and SLAAC.

In addition, objects created by VMware Integrated OpenStack on NSX-T can also be displayed in NSX Policy user interface. The migration process performs the following operations:

Verifies that you use the minimum required NSX-T version.
Validate tests, more specifically:
- The test ensures that it does not configure unsupported service plugins. VMware Integrated OpenStack with NSX-T Policy does not support Neutron layer-2 gateway extension.
- The test verifies that BGP is enabled on the Tier-0 gateways and the DHCP relay is not configured for any availability zone.
Migrates all resources managed by VMware Integrated OpenStack, Tier-0 routers, profiles, and other NSX-T resources not consumed by VMware Integrated OpenStack.
- At the end of the process, NSX-T resource corresponding to Neutron objects can have the same id as the Neutron.
- Tags applied to resources on NSX-Policy Manager are the same as tags previously applied on NSX-T Management Plane.
Reconfigures the VMware Integrated OpenStack control plane for using the policy plugin instead of the MP plugin. It also updates the Neutron custom resource required for running the NSX Policy plugin.

Note:

When migrating from NSX MP to the NSX Policy, the VMware Integrated OpenStack orchestrates the NSX migration coordinator for promoting Management Plane objects to Policy objects.
The VMware Integrated OpenStack controls each NSX objects associated with Neutron resources, and other dependent objects such as certificates and profiles.
If you modify backend resources directly, the NSX resource is not in sync with Neutron status and VMware Integrated OpenStack cannot perform the promotion for that specific resource causing the migration to the Policy fail.
After you finish the migration, ensure that the NSX resources managed by VMware Integrated OpenStack remain unaltered at the backend.
During migration, you cannot include load balancers and firewall groups in the ERROR state because you cannot migrate any resources created for the load balancers and the firewall groups on the NSX-T backend to NSX Policy.

Prerequisites

Verify that you use NSX-T 3.1.0 or later for the MP to the Policy migration.
Verify that the migration coordinator service is running on NSX-T.
Note: You must backup NSX-T manager before triggering the migration. If the migration fails, you must restore the NSX manager and retry the migration from VMware Integrated OpenStack once restore has been successful. After the migration, you cannot revert to NSX-T Management plane. There is no supported solution to revert to the NSX MP plugin after a successful migration to the NSX-T Policy manager.

Procedure

Start the migration service on nsx. SSH to the first nsx manager as the admin user and run:
```
start service migration-coordinator
```
Log in to the VMware Integrated OpenStack manager and run:
```
viocli update neutron
```
Add the following code in Neutron configuration. After the update, you can see neutron-mp2p-migration pod CREATED and RUNNING.
```
manifests:
 mp2p_migration: true
```
Monitor the neutron-mp2p-migration pod. If the migration process is complete, the status of the pod appears as: COMPLETED. You can use the following code for verifying that the Neutron server uses the policy plugin.
```
viocli update neutron
manifests:
  mp2p_migration: true
  vmware_dvs_plugin: false
  vmware_nsxpolicy_plugin: true
  vmware_nsxv_plugin: false
  vmware_nsxv3_plugin: false
```
Once the migration is complete and the Neutron server pods have started the new configuration, SSH to the nsx manager to stop the migration, by running:
```
stop service migration-coordinator
```

Results

After successful migration, you can see that the migrated resources from MP are in the Policy.