The commit replaces DefCore committee (a former name) by
Interop Working Group (the current name) and updates a few
more old interop references.
Change-Id: I8bd05246e42c0e98a9825a4621ac9c3ed714d1dc
In python 3, all strings are considered as unicode string.
This patch drops the explicit unicode literal (u'...')
or (u"..") appearances from the unicode strings.
Change-Id: I64af1c7c7415cd4ab99b6a913fb84fecbc0a3bf1
This adds delete_on_termination field for the compute API response schema
for the 2.79 microversion in 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)
Change-Id: I7a9b22477b800c6d60acb67c27aff5dcb61d7875
As Tempest support the keystone's scope and new default roles
like reader, this commit document that how those can be
requested and used in Tempest or its plugins tests.
Change-Id: Iebacbeda231f82d6d16dbdcde635f19ae862181f
Now a days, Tempest does not have much active core reviewers due
to that merging the incoming code change is taking too much time.
As you can see we have lot of backlogs in open review ~400
If situation improve in future and we have more Core review
then we can change the policy back to two +2 requirement.
Discussion in QA office hour:
- http://eavesdrop.openstack.org/meetings/qa/2021/qa.2021-01-26-14.00.log.html#l-147
Change-Id: Ic005de3e56cb4fde9cfce183ee598c7e9f77f464
Following stestr's example where arguments such as --blacklist-file,
--black-regex and --whitelist-file are deprecated since its
3.1.0 release, let's do the change here as well in order to
get tempest consumers some time for the transition.
This change deprecates the following arguments and replaces them
by new ones which are functionally equivavelnt:
* --black-regex is replaced by --exclude-regex
* --blacklist-file is replaced by --exclude-list
* --whitelist-file is replaced by --include-list
For now, Tempest will accept both (new and old) arguments to make
the transition smoother for all consumers.
The patch also bumps min version of tox to 3.18.0 in order to
replace tox's whitelist_externals by allowlist_externals option:
https://github.com/tox-dev/tox/blob/master/docs/changelog.rst#v3180-2020-07-23
Change-Id: I3e09b31f63d2cd7ea41c48e62432bd3bc54fcf44
compute microversion 2.3 schema is already covered in
I2f36a51fa47b28df1afada5396dec3ce7dc43d78
This commit update the doc for the same.
Change-Id: I58160cc2bd42cabce1abc482dd769e2323c90026
stable/stein is not suported in Tempest now, so
let's remove their jobs from master gate.
Also, update doc to reflect it.
Depends-On: https://review.opendev.org/c/openstack/stackviz/+/768212
Change-Id: I0cbc2883e1cfdb3b1d6b10a7ecea83a4bae32afb
Generate documentation for each test from its docstring.
The sphinx-apidoc tool is used to generate the .rst
files necessary for the generation of the documentation.
When the documentation is being build only functions that
start with "test" are passed to the resulting documentation.
Change-Id: I1878f67e10df9bb1f8289beda8e59a56b5057fe4
As discussed in Victoria PTG[1], we need to start pining
the constraint in tox.ini on Tempest new release so that our
tox.ini can match with compatible constraints with Tempest version.
[1] https://etherpad.opendev.org/p/qa-victoria-ptg
Change-Id: Ib705f59ef3aea93b2778cc87fc44d390b5a62c94
Let's remove deprecated scenario image options which have been
deprecated for more than 4 years.
From now on CONF.scenario.img_file will need a full path for the image.
CONF.scenario.img_dir was deprecated and will be removed in the next
release. Till Tempest 25.0.0, old behavior is maintained and keep working
but starting Tempest 26.0.0, you need to specify the full path
in CONF.scenario.img_file config option.
Change-Id: I96d26ad3889f55d867fdea016953cce522a6fbdf
Related-Bug: #1393881
Switch to openstackdocstheme 2.2.0 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* parallelizing building of documents
Update Sphinx version as well.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
Set openstackdocs_pdf_link to link to PDF file.
Depends-On: https://review.opendev.org/728938
Change-Id: Ia31f69f00eb24771bf700b4e25ae73a09c1c8aed
Microversion 2.59 [1] compute API added a "uuid" parameter to the body of
the following migration responses:
- GET /os-migrations
- GET /servers/{server_id}/migrations/{migration_id}
- GET /servers/{server_id}/migrations
This commit adds the uuid to the response validation schema for
list_migrations.
[1] https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#id55
Change-Id: Ic748f70d90446c79324df30147e4a270b72d710e
support-policy section was renamed in
- https://review.opendev.org/#/c/725446/
but redirect for that was not correct. Fixing that
redirect.
Change-Id: Ia2921533c7a61bab4325a4a89b2b84f391e0aafd
Now we have more documents for plugins on stable release,
support and their testing policy. Let's prepare a
index page for it will be easy for plugins maintainer.
Also renaming the stable support policy section to have a clear
name.
Adding redirect links for moved documents.
Change-Id: I17a9a6e0e88605a0ee5047678d6ed168c31396ec
As Tempest and plugins master version is used to test the supported
stable branches, we need to test them on master gate.
Adding document for that so that we can test the stable branches
more consistently on plugins side too.
Change-Id: Ied3c6bb4032fd3740ae0d6d185e4a138fd335b02
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>
This commit enables xindy for the PDF build. We can do this since the
bug[0] was already fixed.
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1643664
Change-Id: I98aa27ea412fdc2d562fe845dd834550d6751a2b
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
Martin Kopec