* Dont load masters when loading attribute relations as this causes
update_domain() to explode after the zone is AXFR'd
* Change srv.ip > srv.host
Closes-Bug: #1492749
Closes-Bug: #1492750
Change-Id: Ia6b1e855708254ab2d17ffd92eed3c140b2b9836
Remove the specification in tox.ini that _ is a builtin so that
it will no longer assume that _ does not need to be imported.
This helps ensure that the _ from i18n is used.
Activating this check did not flag any violations.
Change-Id: I5ce6b01544eab566353ad69a3d36d009f178f606
Adds SSLMiddleware that checks a configurable header to set
the correct url_scheme used to generate links when host headers
are in use.
Change-Id: Id864bb53d175c868fdee58c04fd2ea27ee188e08
Closes-Bug: #1490034
When https://review.openstack.org/#/c/170612/ landed, the host/port
configuration for pool targets moved to be regular pool_target options.
The config that is shown in the documentation reflects this, but the sample
config does not. This gets really confusing, because the default host/port
is 127.0.0.1:53, so the Pool Manager will still start, and NOTIFYs will
be sent there.
Change-Id: If682bdcdf2bfb5f2a6c7f435a41e0577e262a5f3
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
This lets us run functional tests that need to auth with keystone
but that need to run against a url outside of the service catalog.
Change-Id: Ie3f739ea2626bd0c597188f3312a7c2b950ae4fb
In preparation for async zone exports, move imports to be their own objects,
away from zone tasks. This is essentially a giant renaming.
Change-Id: If6eefbf5553d0fc09e638e879b88c73c133c56fe
* Failed test cases will show all captured logging
* Forward OS_*_CAPTURE environment variables along from tox to testr
Change-Id: Ice9a64d07bb77dd46fb1da6a8ffaa8fd85d5f38b
* Call them "functional tests" instead of "tempest tests"
* The functional tests are run with tox now
* Updated the config file
Change-Id: Ibf9e986ac63e277e1b4f5f319113b4558be2a900
The idea here is, like many things, the time and frequency of sending
NOTIFYs is not the same for every backend. So we let the backends decide
when to send their NOTIFYs. Ideally this makes the Pool Manager code simpler
and the backend code easier to understand, and avoids sending some
unnecessary NOTIFYs.
This requires a change to MiniDNS' rpcapi to make notify_zone_changed and
get_serial_number take a host and port, instead of a nameserver object.
Change-Id: I8d67cebeecc8261e715849aefeafd20f0d60d304
Modified export zones to improve time.
Initially took 6 minutes 30 seconds to export a zone with 30,000
recordsets. Now takes 2-4 seconds. To export a zone with 100,000
recordsets, it now takes approximately 7-16 seconds.
MySQL Dump with 2 big zones (30,000 recordsets and 100,000 recordsets)
http://goo.gl/CEZ3pT
WIP
Change-Id: Ifc079ec89b7190532c90e1edb0e70f8d3da0018e
