The __init__ just passes the same arguments, so it is not necessary
to implement it. This patch removes it for the cleanup.
Change-Id: Ib465356c47d06bfc66bef69126b089be24d19474
tempest-lib is marked as deprecated now.
The library is not maintained and Tempest itself provides the stable
interfaces under tempest.lib as [1] said.
So this patch makes the project use tempest.lib for long-term maintenance.
[1]: https://github.com/openstack/tempest-lib/blob/master/README.rst#tempest-lib
Change-Id: Ic45028c2fd803fca5e82a0caa85914414f511022
This adds the quotas api from /admin to /v2 with some changes.
All users can GET /v2/quotas/<project_id>
Users with "All-Projects" permission can view other projects
(by setting X-Auth-All-Projects:True in the HTTP Headers)
Users with "All-Projects" and "set-quotas" can set other
projects quotas
Moved the API rendering to Designate Object based rendering
Change-Id: I7a0b828824ad6f274d922748f5f9a68157cd939a
Depends-On: I06180a7402fc45940d4b312666cf2dfd33af1305
These tests are moved to the designate-tempest-plugin in
https://review.openstack.org/#/c/329187/
Change-Id: I399d4018f78d59c61c5bd5cc3be57bf678a3a75b
Depends-On: I9752685afccee5dcd009f76b5242fd6f12f0fc37
These tests have been migrated to designate-tempest-plugin in
https://review.openstack.org/329062
Change-Id: I0c52bc66e67928f98cfa367277ec1f2c429a02a8
Depends-On: Ic93b8c1bbfc30792cbb071df797e11e17cc99033
This patch removes zone_import and zone_export client's methods and
tests as they have been moved to designate-tempest-plugin.
Change-Id: I38258c1bdfd32b7719f25df795acde2af5e66eec
These tests now have equivilant tests in the designate tempest
plugin, we should remove the old copy.
Change-Id: I0b55891d25880da8974f4fdb02d4c31e7b85fe6b
The decorator use the types.MethodType to attach the parameterized
test to the test class, but the function changed in python 3.x. This
uses six to do the right thing so this can be used outside the tempest
tests that are always run with python 2.x.
Change-Id: I56fee078d3fa718536208fd3bd5228cc45d24444
When listing recordsets with filtering on record data,
designate makes a first filtering against recordsets table
to retrieve a list of recordsets belonging to the specified
zone, followed by the second filtering against records table
on record data (e.g. IPs), then intersects the two.
Check https://github.com/openstack/designate/blob/master/designate/api/v2/controllers/recordsets.py
This approach does not work properly when pagination happens.
Imagine a zone has 21 A records with 10.* like IPs,
and 9 A records with 192.* like IPs. When requesting
"/v2/zone/{zone_id}/recordsets?data=10.*", designate makes
the first filtering and get the first page (i.e. 20 recordsets) which may
have both 192.* and 10.* records mixed together,
the second filtering actually excludes all 192.* records from the first page.
But that ends up with a page less than 20 records, so designate won't
include a 'next' link in the response.
This patch fixes the problem.
Closes-bug: #1561746
Change-Id: Ib06dd288d129ff4b39c388d80f24d179c6af28d8
Remove tests which have now been moved to the Designate tempest plugin, for
each test, I checked to ensure the new test was functionally the same - and
added or updated tests where there was a gap.
Change-Id: Iff08cc5bf77f64824165c72612f0783cb85be211
Depends-On: I3f0efe61452186c7399fd6196ff3509872c77a80
By _default_, Pecan exposes the functionality
to try and "use the extension in the URL for
guessing the content type to return."
I'm not even kidding:
http://pecan.readthedocs.org/en/latest/pecan_core.html#pecan.core.Pecan
`guess_content_type_from_ext`.
So this allowed an API user to GET /v2/zones.json that returned
the same thing as /v2/zones. Similarly for /zones/id.json.
So this turns that off.
Change-Id: I38a2e35f58cf7619bee64247d7ac01a50b0dcc58
- This implements a few `TODO`s in the code around actually polling
nameservers for zone deletes. I found this necessary for changes
that were truing up missed DELETEs, and wanted to make a poll/
update_status call to verify deletion across a fleet of nameservers
when one was down.
- This originally failed in PowerDNS, because in older versions
that are still in all the distro repos, PDNS responded with a
NOERROR and empty answer section when it got a query for a zone
it knew nothing about. NEAT.
http://blog.powerdns.com/2015/03/02/from-noerror-to-refused/
- NOTE: This increases timeout for functional tests and we maybe
shouldn't do that.
Change-Id: Ied1e5daf4798127e00a06265164759d98fc9ba72
This lets us write custom hooks out of tree that are called whenever a
request is made in the functional tests.
The hook gets notified:
1. Just before a request, with the request args
2. Just after a request, with the resp and resp_body
3. When a request causes an exception, with the exception object (which
contains the resp and resp_body if it came from tempest_lib)
This is useful for maintaining certain out-of-tree test modifications,
like:
1. Rate limiting client requests
2. Additional custom logging
3. ???
Change-Id: Ie2ca4ee85972aa8f9b22c402ed8fad368d2ff7d9
* Test trailing slashes in SPF, TXT recordsets
* Test negative values in MX, SSHFP records
* Move recordset validation tests to a new module
Change-Id: I3f3ee09df45ddbefda66591c1937d733eaaf5ef3
This client now supports the `v2_path_pattern` config option, and now
allows you to pass in filters when listing tlds.
Change-Id: If6e1a343c1a0252f9f9d19f50c5d4c9772fa638c
_assert_exception() is expected to catch the case where an exception
with certain data must be thrown out. But it misses the case that no
exception is thrown. This patch fixes the bug.
Change-Id: Ia51e12d171512db4e9bc6fc1dd3eb66c951051e8
Closes-bug: #1537892
Replace assertEqual(None, *) with assertIsNone in tests to have more
clear messages in case of failure.
Change-Id: I471f34681f1bac78b9a6b4fe2e39f79670f5f25c
Closes-Bug:#1280522
After merge of change [1] to devstack project, preconfigured creds for
Tempest cannot be used anymore. But Manila requires such.
For the moment, latest Tempest interfaces cannot allow us to use
preconfigured creds because of bug #1524717.
So, until this bug fixed, we should workaround Devstack changes and
set legacy opts explicitly.
[1] I65b56ff681d6c27094380693c953fbc3664eceb0
Related-Bug: #1531049
Closes-Bug: #1531189
Change-Id: I4dc266713ec06bc6e98616a1277c8ae6cadf199d
This is a pretty invasive change :)
A non complete list of changes:
* Database Tables
* Database Columns
* Designate Objects and fields on Objects
* Designate Objects Adaptors stop doing some of the renames
* All RPCAPI versions are bumped - totally backward
incompatable (function names have changed)
Change-Id: Ib99e918998a3909fa4aa92bf1ee0475f8a519196
assertEqual expects that the arguments provided to it should be
(expected, observed). If a particular order is kept as a convention,
then it helps to provide a cleaner message to the developer if Unit Tests
fail. There are several Unit Test files where the arguments for assertEqual
have been swapped.
Change-Id: I6fdedcde67f76883257d35d1b812ab8a0e3e0733
Related-Bug: #1259292
Graham Hayes