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 |
||
---|---|---|
.. | ||
create-zone-export-response.json | ||
create-zone-import-response.json | ||
create-zone-request.json | ||
create-zone-transfer-accept-request.json | ||
create-zone-transfer-accept-response.json | ||
create-zone-transfer-request-request.json | ||
create-zone-transfer-request-response.json | ||
delete-zone-response.json | ||
list-share-zone-response.json | ||
list-zone-export-response.json | ||
list-zone-import-response.json | ||
list-zone-transfer-accept-response.json | ||
list-zone-transfer-request-response.json | ||
list-zones-response.json | ||
poolmove-zone-request.json | ||
share-zone-request.json | ||
share-zone-response.json | ||
show-zone-export-content.txt | ||
show-zone-export-response.json | ||
show-zone-import-response.json | ||
show-zone-nameservers-response.json | ||
show-zone-transfer-request-response.json | ||
update-zone-request.json | ||
update-zone-response.json | ||
update-zone-transfer-request-request.json | ||
update-zone-transfer-request-response.json | ||
zone-response.json |