b004985c24
This patch includes the initial framework to allow existing neutron deployments running different backends to be migrated over to the nsx-v3 plugin. The main logic that is required to do this is to allow the ability of an id to be specified for a given resource. This patch makes this possible with the addition of a new extension api-replay. The reason why a new extension is needed is because the RESOURCE_MAP is loaded after the plugin is loaded. Therefore, there is no way for me to change the mapping directly in the plugin without creating an extension to do so. This patch also adds support for migrating the router-uplink and floatingips which was missing in the previous patchset. Here's an example output of the migration tool running: http://codepad.org/I7x6Rq3u Change-Id: I2ee9778374a8d137e06125f2732524c7c662c002
VMware-NSX package
You have come across the VMware-NSX family of Neutron plugins
External Resources:
The homepage for the VMware-NSX project is on Launchpad.
Use this site for asking for help, and filing bugs. Code is available both git.openstack.org and github.
For help on usage and hacking of VMware-NSX, please send a message to the openstack-dev mailing list.
For information on how to contribute to VMware-NSX, please see the contents of the CONTRIBUTING.rst file.