client_parameters was been designed as a way to pass parameters
for service clients to the ServiceClients class.
After the initial implementation, the client registry was added,
which allows for automatic registration of all clients and their
parameters. If configuration is available, parameters will be
pushed into the registry automatically.
When the registry part was implemented, the client_parameters logic
has been broken. Parameters are loaded and prepared correctly, but
ultimately they are not used for registration, they are basically ignored.
So this commit simply deprecates client_parameters, so that once it's not
used in tempest/clients.py anymore and the deprecation periodic is over
it can be removed.
closes-bug: #1680915
Change-Id: Ib37bde098d15ce440297728f0d0e1087b8693b6c
The allow_port_security_disabled option had been added as a temporary
option for skipping the test on Liberty. Current Tempest doesn't support
Liberty, so this patch removes the config option from Tempest.
Change-Id: Ia7d7f3f545e7582be3c3f005576adceede5e97cb
This feature provides the ability to delete a volume and have Cinder
handle deletion of snapshots associated with that volume.
It is allow a volume and its snapshots to be removed in one operation
both for usability and performance reasons.
Change-Id: I99f9910f75aef095f2bbb37680ee584e52bf82da
v2 volume transfers service clients does API calls on
separate resource url "os-volume-transfer" but those
are currently in v2 volumes_client.py.
Each resource service clients should be in separate file.
This commit separate the transfer service client from volumes client
and deprecate the same from volumes service client.
Change-Id: Ia85bcfbadbff4f7c594dc5631ecdd595c5d275f3
The dvr_extra_resources option had been added since the commit
Ib1a6007bbd65182743e1f1ed5819134d748e8d92 . This option was for extra
resources which were provisioned to bind a router to Neutron L3 agent.
The extra resources need to be provisioned in Liberty release or older,
and are not required since Mitaka release. Current Tempest doesn't
support Liberty, so this patch removes the config option from Tempest.
Change-Id: I1eb228559a170a2a157a180ac8404bcbd5efd062
The reseller feature has been implemented as built-in feature which
can not be disabled since Mitaka, and Tempest doesn't support Liberty
now. So this patch removes the corresponding config option from Tempest.
Change-Id: Ieb974047fb204674cef82cf896016d6780a4757a
Adds the following API call to the roles_client library:
- list all role inference rules (/v3/role_inferences)
This enables querying these APIs for a list of all the
role assignments or all the role inferences.
Note that listing all role inference rules is distinct
from listing inference rules. This can be confirmed
in the API docs [0] and in the code itself [1]
(see list_role_inference_rules vs list_implied_roles).
[0] https://developer.openstack.org/api-ref/identity/v3/#list-all-role-inference-rules
[1] 3e5ead0a45/keystone/assignment/routers.py
Change-Id: I9d6c0dc83a85bbca173b753183d838adfee04008
Below compute config options for validation server had been
deprecated with corresponding options in validation group almost
year back.
- 1908e37d2551760831e338788511db93d5129e16
- ``compute.image_ssh_user`` (available as ``validation.image_ssh_user``)
- ``compute.ssh_user`` (available as ``validation.image_ssh_user``)
- ``scenario.ssh_user`` (available as ``validation.image_ssh_user``)
- ``compute.network_for_ssh`` (available as ``validation.network_for_ssh``)
- ``compute.ping_timeout `` (available as ``validation.ping_timeout``)
This patch removes them from tempest conf.
Few plugins still using the old configs and this depends on their fix.
Change-Id: I2221b2d50fee97a464c7d5f0b3c2e13142cb394f
This patch adds compute server evacuate API client method.
This client method is required to implement evacuate related tests
in OpenStack Patrole project.
Change-Id: Ie0d65d83923331caaa9cbbbd63b096ff8400bffa
Partial-Bug:: #1673811
Adding a new client lib to handle the OAUTH consumers API testing
Included unit tests for the client lib, and
API tests for the OAUTH consumers API
Co-Authored-By: Nishant Kumar <nk613n@att.com>
Co-Authored-By: Avishek Dutta <ad620p@att.com>
Change-Id: I6d0884637cfe00a5313a5d019e1e062316f76d57
Closes-Bug: #1672810
Many projects provides multiple API versions and the version
information is very important for users, because users can know
what features are available on clouds. However, Tempest didn't
test the Cinder API versions in long-term. So this patch adds
the corresponding test.
NOTE: This patch adds the response status code validation also
for 300 but Cinder api-ref currently shows 200 and 202 also.
These status codes are never returned actually and the patch
Id28e26fca0adbdcfb0d905f52ca697a74db3be75 will fix it on
Cinder side.
Change-Id: Id5791665d8435fac7552733b0c1126cee4359d00
Lots of Cinder backend drivers have support unmanage and manage
features. It's necessary to add test case for these feature apis.
Including:
[1] Add volume manage client as library
[2] Add unmanage volume api to v2 volumes client
[3] Add release note
[4] Add test case: test_volume_unmanage_manage
Depends-On: I055aa66738deb5ae2fb925429cec565e3901340c
Change-Id: I4294de92a801db2697ba870ff1b5fdbe4b2f5a4b
Cinder v1 API tests have been removed since the commit
I04de2d90fe11f8ec4acbfa983bc0ad3aa979f45b
Then this patch adds the corresponding reno.
Change-Id: I7cab71962ed33c196ef2c00825bfcc4f2917398e
Cincer v1 API has been deprecated since Juno, and Tempest doesn't
need to run the corresponding tests as the default. Then this patch
makes Cinder v1 API deprecated.
Change-Id: I836dc9d75f361078b7c8bd8430e6cb463a6e1ca1
Many projects provides multiple API versions and the version
information is very important for users, because users can know
what features are available on clouds. However, Tempest didn't
test the Clance API versions in long-term. So this patch adds
the corresponding test.
Change-Id: Ib85819fb71f0b12b64351b307d83a3beb77d7fad
This is a leftover from when sahara was moved out of tree.
It causes conflicts when the sahara plugin loads, and it should
be removed.
This option is not used right now by Tempest code, so even if someone
is using it, it has not effect whatsoever on test execution.
The only case in which this option may have effect, is when the
sahara-tests Tempest plugin is installed. When the
sahara plugin is loaded, the config option will be there.
I think in this case we should skip deprecation, and just remove it
like we did in the past when moving Tempest code to a plugin.
Change-Id: Ie7556b97237b0101000d140d351edea5e518783f