Go to file
Ghanshyam 56149024a0 Use stable constraint in run-tempest for stable branch testing
Stable branches till stable/rocky is using python
version <py3.6. Tempest test those branch in venv
but Tempest tox use the master upper-constraint[1]
which block installation due to dependencies
require >=py3.6. For exmaple, oslo.concurrency 4.0.0
is not compatible for <py3.6.

As we pin Tempest for EM stable brach, we should be
able to use stable constraint for Tempest installation
as well as while running during run-tempest playbook.

tox.ini is hard coded to use master constraint[1] which force
run-tempest to recreate the tox env and use the master constraint.

Devstack can set stable u-c to use via env var but this is
not enough as Tempest role run-tempest recreate the tox
env with master u-c.
- https://review.opendev.org/#/c/705089/4/lib/tempest

Currently we are fixing run-tempest to use stable constraint
till stable/rocky which use distro having <py3.6.

Ideally, we can change compatible branch constraint in tox.ini
while doing release tag for Tempest. But that can be done
for future tags only.

[1] bc9fe8eca8/tox.ini (L14)

Change-Id: I4268049ff91e5527e4b95fd8a70fa53ba27d56ed
2020-02-06 13:12:07 +00:00
2020-02-04 19:23:01 +00:00
2016-10-19 14:31:13 +02:00
2019-04-19 19:29:35 +00:00
2018-09-05 08:45:46 +00:00
2019-09-04 13:44:17 +00:00
2012-04-12 16:04:36 +02:00
2019-09-11 16:42:28 +09:00
2019-04-04 14:01:16 +11:00
2020-02-04 19:23:01 +00:00
2017-03-08 17:20:35 +00:00
2018-07-18 10:42:38 +01:00
2020-02-04 20:07:02 +00:00

Team and repository tags

image

Tempest - The OpenStack Integration Test Suite

This is a set of integration tests to be run against a live OpenStack cluster. Tempest has batteries of tests for OpenStack API validation, scenarios, and other specific tests useful in validating an OpenStack deployment.

Get in touch via email. Use [tempest] in your subject.

Description
OpenStack Testing (Tempest) of an existing cloud
Readme 344 MiB
Languages
Python 99.8%
Shell 0.2%