70bb03c922
* Since tripleo-ci-fedora-28-standalone is not yet ready to support tempest and python3, till then let's disable tempest run on it. Once it is available we can enable tempest here. Change-Id: If6047b5f19198789a07bb4b2e1dc16111355bf9c |
||
---|---|---|
.. | ||
README.rst | ||
base.yaml | ||
build-image.yaml | ||
layout.yaml | ||
multinode-jobs.yaml | ||
nodesets.yaml | ||
standalone-jobs.yaml | ||
undercloud-jobs.yaml |
README.rst
Override config
featureset override
Take advantage of zuul job config to override featureset settings like tempest tests that should run. The following settings from the featureset config can be overriden:
- `run_tempest`: To run tempest or not (true|false).
- `tempest_whitelist`: List of tests you want to be executed.
- `test_black_regex`: Set of tempest tests to skip.
- `tempest_format`: Installing tempest from venv, packages or containers
- `tempest_extra_config`: A dict values in order to override the tempest.conf
- `tempest_plugins`: List of tempest plugins needs to be installed
Example:
- job:
name: tripleo-ci-centos-7-scenario001-multinode-oooq-container
parent: tripleo-ci-multinode
...
vars:
featureset_override:
run_tempest: true
tempest_whitelist:
- 'tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern'
tempest_black_regex: 'tempest.api.network|tempest.api.compute'
tempest_format: 'containers'
tempest_extra_config: {'telemetry.alarm_granularity': '60'}
tempest_plugins:
- 'python-keystone-tests-tempest'
- 'python-cinder-tests-tempest'