Testing OpenStack upgrades
923231c8ba
Irrelevant files where overriden in functional and scenario test case jobs loosing values from the base devstack job. This fixes it. Change-Id: I26dc52bb70cc1747df374978479e3fd4786846a8 |
||
---|---|---|
devstack | ||
doc | ||
infrared | ||
playbooks | ||
releasenotes | ||
report | ||
roles | ||
tobiko | ||
tools/ci | ||
zuul.d | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.pylintrc | ||
.stestr.conf | ||
LICENSE | ||
pep8-requirements.txt | ||
Pipfile | ||
plugin.spec | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
Vagrantfile |
Tobiko
Test Big Cloud Operations
Tobiko is an OpenStack testing framework focusing on areas mostly complementary to Tempest. While tempest main focus has been testing OpenStack rest APIs, the main Tobiko focus would be to test OpenStack system operations while "simulating" the use of the cloud as the final user would.
Tobiko's test cases populate the cloud with workloads such as instances, allows the CI workflow to perform an operation such as an update or upgrade, and then runs test cases to validate that the cloud workloads are still functional.
Main Project Goals
- To provide a Python framework to write system scenario test cases.
- To provide tools for testing OpenStack system operations like update, upgrades and fast forward upgrade.
- To provide CLI tools to implement a workflow designed to test potentially destructive operations (like rebooting cloud nodes, restarting services or others kinds of fault injections).
- To provide tools to monitor and recollect the healthy status of the cloud as seen from user perspective (black-box testing) or from inside (white-box testing).
References
- Free software: Apache License, Version 2.0
- Documentation: https://tobiko.readthedocs.io/en/latest/
- Release notes: https://docs.openstack.org/releasenotes/tobiko/
- Source: https://opendev.org/x/tobiko
- Bugs: https://storyboard.openstack.org/#!/project/x/tobiko