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 |
||
---|---|---|
.. | ||
samples | ||
conf.py | ||
dns-api-v2-blacklist.inc | ||
dns-api-v2-index.rst | ||
dns-api-v2-limits.inc | ||
dns-api-v2-pool.inc | ||
dns-api-v2-quota.inc | ||
dns-api-v2-recordset.inc | ||
dns-api-v2-reverse-floatingips.inc | ||
dns-api-v2-service-status.inc | ||
dns-api-v2-shared-zones.inc | ||
dns-api-v2-tld.inc | ||
dns-api-v2-tsigkey.inc | ||
dns-api-v2-zone-export.inc | ||
dns-api-v2-zone-import.inc | ||
dns-api-v2-zone-ownership-transfer-accept.inc | ||
dns-api-v2-zone-ownership-transfer-request.inc | ||
dns-api-v2-zone-tasks.inc | ||
dns-api-v2-zone.inc | ||
index.rst | ||
parameters.yaml | ||
status.yaml |