8733f8f85b
The new API would be v2/zones/<zone_id>/tasks/move Only POST would be allowed on this API. This move zone from existing pool and add it in new pool. After zone pool_id field will be updated in DB, clone-zone will be created on target pool backend servers. The zone transfer(AXFR/IXFR) will happen and the zone on target pool gets synced with the Designate DB. This command serve as replacement to "zone export + zone delete + zone import" procedure. Added following things in pool move operation: - Add/Update NS servers of new pool in the zone Implements: blueprint zone-move Change-Id: I5307de429114b20efd9785c3c0cdb33977418423
11 lines
496 B
YAML
11 lines
496 B
YAML
---
|
|
features:
|
|
- |
|
|
Added zone pool move command which allows admin user to move zone from
|
|
pool A to specified pool B. This command overcome the issues observed in
|
|
zone export-import thereby reducing hours of time of large zone imports
|
|
(e.g. 20-30k records). Please note, if you have moved a zone to a
|
|
different pool, the pool must be configured with a proper tsig key for
|
|
mini-DNS query operations. Without this, you cannot have overlapping zones
|
|
in different pools.
|