Tempest and its plugin are very tightly coupled for testing
Upstream or Production Cloud. Due to its branchless model,
one of the challenges we faced/facing is to provide their
compatible version set.
Since Queens release and with operator request, we started
doing a coordinated release of plugins along with Tempest
which will be marked as the First compatible version for
that particular release.
For example https://releases.openstack.org/train/index.html#tempest-plugins
We test our stable branch with master version of Tempest &
plugins until it is moved to Extended Maintainance state.
One stable release is in EM state, Tempest officially declares
the end of support tag so that we can use that as the last compatible
version for that EM stable testing. But we do not have the correct
last compatible version from plugins which can be used for testing
the EM branch. It should be with hash from the master at the time
stable release is moved to EM not the hash when the stable release
was done otherwise it will be incompatible with Tempest.
We have faced and fixed many issue due to that during py2-drop work
where we have to pick and try all different versions from plugin to
make it work against EM testing.
Change-Id: I99a6df0a2c02e19efaf484fcd97b875887f08d8e
Microversion v2.73 was introduced in Nova by I46edd595e7417c58410648
changing the request responses of ``GET servers/{server_id}``, ``GET
/servers/detail``, ``POST /servers/{server_id}/action`` where the
action is rebuild and ``PUT servers/{server_id}``.
Change-Id: I8c800f6e280ec6fdf204d344124d994a25d0af19
Tempest, its plugins and their dependencies in ussuri
cycle are python-requires>=py3.6 which makes distro not
having python 3.6 to do hack to install py3.6 etc.
We cannot do >py3.6 in basepython so one way is to drop the
py3.5 support and basepython to py3 so that it can choose
the available py version in env.
It time to drop the py3.5 from Tempest. Last supported version of
Tempest for py3.5 is 23.0.0.
oslo drop py2 so we need to remove the py2 unit test job which
is failing and blocking gate.
There is seoarate work to drop the py2 things from Tempest in
compplete set.
Change-Id: I872dbb57df46d1193c0d409bb00d56f372d295fe
Related-Bug: 1861308
Tempest is branchless and support many OpenStack stable branches
and python versions. Users of Tempest should have a clear doc about
what all openstack releases and python versions are supported.
Change-Id: Idc76e07efdd3710a59c773c564ca532419989ed5
The officially supported test runner for Tempest is stestr.
overview.rst has frequently used testr as Tempest runner.
Hence, there is need to replace it.
Change-Id: Ie9f9557ebb791225cb2a9f7dabba67f92a1ac376
Signed-off-by:- Soniya Vyas<svyas@redhat.com>
Some options are now automatically configured by the version 1.20:
- project
- html_last_updated_fmt
- latex_engine
- latex_elements
- version
- release.
Change-Id: Ia656e992e86293339521627acc892f81f7bd6a0b
This commit add PDF building tox.ini environment and options for LaTeX
output. overview.rst is copied from README.rst. And, the original
README.rst file is shrunk because we don't need such a long information
in the README file. People can see the same contents in overview.rst
now.
Change-Id: Id654c814988e78704726d2ba8bea9a03ce8596f8
The name locking test accounts was an early name in the development of
the pre-provisioned credentials development. It described what it did
used tests accounts and lock files to ensure one test class only was
using an account at a time. However, that name hasn't been really used
in a long time and we've called the feature pre-provisioned credentials.
The configuration guide section for pre-provisioned credentials still
had some out dated references to locking test accounts which were never
updated when the feature was renamed. This commit corrects the oversight
and consistently names the feature in that section of the documentation.
Change-Id: I0f3a7b373c5ca2d84a8e82c1e2c3bcd6a2d833f9
This commit makes the BLACKLIST to be published on the Tempest plugin
registry page which we discussed at the PTG[0].
[0] https://etherpad.openstack.org/p/qa-train-ptg
Change-Id: I707aba930037e86f5f94dac73da957f5afacf935
Thorough replacement of git.openstack.org and review.openstack.org URLs
with their opendev.org counterparts.
Change-Id: I88e894db7b854d32593c770f5aa9b8a91fad7866
The 2.71 compute API includes the "server_groups" parameter
in the response to the following APIs:
- GET /servers/{server_id} (show)
- PUT /servers/{server_id} (update)
- POST /servers/{server_id}/action (rebuild)
This will be used in an upcoming change to test attaching
and detaching the root volume of a shelved offloaded instance.
Change-Id: I612a15c475404ded0af15b6241b9ac8ec9fb8e26
This adds the compute API response schema validation for the
2.70 microversion and the following APIs:
- GET /servers/{server_id}/os-volume_attachments (list)
- GET /servers/{server_id}/os-volume_attachments/{volume_id} (show)
- POST /servers/{server_id}/os-volume_attachments (attach)
This will be used in an upcoming change for testing root volume
attach/detach of a shelved offloaded server.
Since the response schema for these have not changed since 2.1 we
have to backfill all of the other servers API response schema
files going back to 2.1.
Change-Id: I2f36a51fa47b28df1afada5396dec3ce7dc43d78
Several docstrings have incorrect format, what prevents to generate
a documentation using sphinx-apidoc extension.
Change-Id: I66431c7030089173d7635c1e2a72765db21f9780
This commit adds servers schema for microversion 2.8 [0]:
Add ‘mks’ protocol and ‘webmks’ type for remote consoles.
The appropriate api_schema files are updated with the
2.8 microversion changes.
Note that no test is added to cover this new microversion
since it isn't possible to test mks protocol in Tempest
gates so as per REVIEWING documentation [1] we shouldn't
add such a test. So, we could only cover the vnc protocol
for 2.8 but this would also not be of much value since
the vnc value (instead of mks) would be returned by the
server.
[0] https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#id7
[1] https://docs.openstack.org/tempest/latest/REVIEWING.html#ensuring-code-is-executed
partially-implements: blueprint full-schema-for-all-microversions
Change-Id: I5a6d2852db8e2a67013eee71a094e9b521a92524
The ‘uuid’ attribute of an aggregate is returned from calls
to the /os-aggregates endpoint from microversion 2.41, so
this is to add 'uuid' in schema of aggregate.
https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#id37
Change-Id: I90e53056ceae5ad6b6ea2995f3f8c6eceea4739a
partially-implements: blueprint full-schema-for-all-microversions
There might be chance that few plugin name and url
does not fit into hard coded column width and give error.
This commit count the column width as per plugins name.
Also display the number of plugins in new SR column.
Change-Id: Ia5736d2581ee3b6f851b8d08f855c2a19c157c47
1. Some limits fields are removed from Microversion 2.35/2.38/2.56,
so we should check limits fields according to microversion.
2. In test_max_metadata_exceed_limit, maxImageMeta is deprecated from
Microversion 2.38, so maxServerMeta is used instead, btw, maxServerMeta
seems to be more suitable for this testcase.
Besides, test_max_metadata_exceed_limit is not used in interop, so we
can safely change its name.
ref: https://developer.openstack.org/api-ref/compute/#show-rate-and-absolute-limits
Implements blueprint: clear-deprecated-api
Change-Id: I53e2ee82c9c52afb0a56526c655eb9b3b6b8f483
This patchset fixes typos (capitalization mistakes,
grammar mistakes) found in the documentation pages.
Change-Id: If500aeab1af7dd8b56d63cbc481ee501216df161
This patch set adds information on test removal, relocation,
renaming to REVIEWING because it is important that such
actions do not break interop. Interop is closely tied to
Tempest because it directly references Tempest tests that
are not only expected to exist, but to also work.
The same is true of breaking blacklist/whitelist
references to Tempest tests, this is also included
in the new documentation section.
It is important that there be REVIEWING guidelines
in place to assist reviewers understand this importance.
Also references are included for defcore/interop to help
users find more information on these topics.
Currently interop is only mentioned in 1 place in Tempest [0]
and yet there is little information about it. This patchset
aims to make it easier to find more information about it
for reviewers and users alike.
[0] http://git.openstack.org/cgit/openstack/tempest/tree/doc/source/test_removal.rst
Change-Id: Ifbde674b42355077fcd8daa07be8be1248b77b0f
This patchset fixes typos (capitalization mistakes, grammar
mistakes) found in the test_removal.rst documentation page.
Change-Id: Ia9a6b9d7a2a151a460a620be9fa6875f2efda00f
This patchset adds update_service to compute module's services_client
library. This API is introduced in microversion 2.53 and supersedes
the following APIs:
* ``PUT /os-services/disable`` (``disable_service``)
* ``PUT /os-services/disable-log-reason`` (``disable_log_reason``)
* ``PUT /os-services/enable`` (``enable_service``)
* ``PUT /os-services/force-down`` (``update_forced_down``)
Negative tests were added for all the APIs above. The negative
tests only test the microversion >= 2.53 case: the new
udpate_service API is called (also with bad parameters).
The v2_11 schema was updated to reference all the unchanged
APIs from v2_1 for the compute services api_schema. Also,
the v2_53 schema was introduced for the new update_service
API and it also references all the unchanged APIs from v2_1.
Finally, unit tests and releasenotes are included.
Change-Id: I5e7b81496cbb87cda81413124b5f82bd5356e666
Compute microversion 2.61 adds 'extra_specs' in flavor APIs response
This commit fill the schema gap for that.
Change-Id: Id1f1e51fbae1cc3d0c9efdcd9009f384745915d6
This patchset fixes some incorrect compute microversion references.
2.54: should have id 49 (was 4)
2.55: should have id 50 (was 49)
2.57: should have id 52 (was 51)
Change-Id: I81d90637fe16e1d5de1e26f50a86f9ff83d355ca
Current doc explaining the stable branches support policy is under
coding guide. But support policy should be at higher level which
can be useful for user or maintainer of Tempest.
Change-Id: Id46e14080559062b4d89e5f7a9acbcd5df09691e
This microversion adds the trusted_image_certificates parameter to the
server rebuild, server create, server update, and servers details
responses.
Change-Id: I48f62d36a871a95601ebf277a2f39a41a873daa8
Implements blueprint: nova-validate-certificates