This removes the append_version_to_url config option in favor of
a pattern that will build the request url by interpolating arguments.
Change-Id: I0b1152d518a5f4ddfcfc5d5a7b28606932a86c4b
* Fixes a policy check on doing the zone export that caused a 403
unless the tenant was an admin
* Adds ZoneFile and ZoneFileRecord models to parse a zone file
* Adds some "meta" tests for the new models
* Updates the test_export_domain test to check the zone file text
Change-Id: I65c93f5d5283fc5962f4a2bf0ac8abae1966e6d6
Do the needful to move Zone Exports to an asynchronous resource in the
v2 API, as discussed at the Austin 2015 summe mid-cycle
* Make designate-zone-manager an RPC service, with a read-only connection
to the database
* Add a 'location' column to the zone_tasks table that stores a location
(swift, URI) that is used to determine where the export will be made
available to the user
* Add all the infrastucture to make zone export resources live (objects,
central, storage methods)
* Add a quota on the size of allowed synchronous exports
* Tests, docs
THIS DOES NOT IMPLEMENT
* Zone exports to Swift
* Debateable: See the note in zone_manager/service.py about how the configuration
and determination of future swift exports will work.
ApiImpact
Blueprint: async-export
Change-Id: I1c168b10358164c3ca5be986b4d615df71062851
