Since py2 is no longer supported, built in methods can replace the
six package usage, as been done in the neutron project
Change-Id: I922963fbbcc0ab263e1f6e56907b73b007015a75
- Add elapsed time logging
- Skip irrelevant retries of nsx requests
- retrive only tier0/tier1 logical routers whenever relevant
- Update max number of tier1 logical ports to migrate
Change-Id: If6878e20701312daf66be1a035db4614013c7e47
Becasue of the different implementation fo edge firewall in the
mp/policy drivers, the script will migrate those without the migration coordinator.
Once the migration is done, each MP edge firewall with rule will be re-created
as a policy one, and its rules will be deleted.
Change-Id: I8de2055bd40a195067fb8c0b23309a25225dd083
1. Stop using constant AUTO_DELETE_PORT_OWNERS
as Commit Iba02f5a2211b18c2deb9097daad6be5e7d21faf8 removed this
2. Upgrade python-openstackclient and update osc security groups code
to match patch Ifd20b5fc47fd0ea0bb5aeda84820dcc0fb1e8847
Change-Id: I25ad6e1670d19fa3dcf8210eb4fd13aef6c3ad37
Migrate resources that used to be in the neutron config and used by
neutron resoruces, but were changed.
Look for mdproxies & switching profiles currently used by neutron logical
ports and migrate those as well.
Change-Id: I7eeb24aea8d8b000f76dc998777aafd4788b68af
Migrated segments have different dhcp server config.
When updating the segment, the correct one should be used as changing
it is not allowed
Change-Id: I64a5bfec0da892bcd3cdee6ab1fe0c6466655711
DbCertificateStorageDriver should use the pk_password from the
nsx_p config section and not from the nsx_v3 one
Change-Id: Ibe843e9e994bb679bdae68b0683aa36e2c78d891
- Migrate MDproxy with admin user
- When creating the dhcp server config post migration it should be done with
with the admin uer and not the openstack principle identity
- Select Tier1 locale-service id even if there is no edge cluster
Change-Id: I68c184d245e50e363bcf5b53ea71cce661ee7aa3
replace indirect call the SR removal with a direct one
(The indirect call via _core_plugin also works)
Change-Id: Ie379cbda369f7d45818275294f10e05cb9a7ef3b
If the LB has an external vip, the member must have a local subnet-id
connected to a router with an uplink,
or the member must have an IP which is a FIP address
In addition, remove one leftover log, and remove a lock on router
id when it is None
Change-Id: Iefb492e43b5cc47a84ce82e4dfbcb0d1e5e6bffe
Before starting the migration, check for unsupported configurations
that will fail the migration.
Currently those include:
- Tier0 with BGP disabled and BGP rules
- DFW/Edge firewall sections witl 1500 rules or more
Change-Id: I702417c287b629844f2b8e1adda98b137e1ee9ff
This patch will allow moving neutron from using the nsx_v3 plugin to the nsx_p plugin.
This includes:
- admin utility to move all resources to the policy api:
nsxadmin -r nsx-migrate-t2p -o import (--verbose)
This utility will:
-- Migrate all neutron used & created resource using the nsx migration api
-- roll back all resources in case it failed
-- post migration fix some of the policy resources to better match the expectation
of the policy plugin
- admin utility that will cleanup left overs in the nsx_v3 db:
nsxadmin -r nsx-migrate-t2p -o clean-all
(can be used, but everything should work without calling it as well)
- Some minor changes to the policy plugin and drivers to allow it to handle migrated resource
which are a bit different than those created with the policy plugin
-- Delete DHCP server config once a migrated network is deleted
-- Update LB L7 rules by their name suffix as their full display name is unknown
Change-Id: Ic17e0de1f4b2a2d95afa61ce33ffb0bc9e667b89
1. Make the validation optional (If False - only log the warnings)
2. Validate each resource against all clusters and fail only if not
connected to any
Change-Id: I9abd091fc42d4dbe22e1b806df4d9131ab054726
