Testing OpenStack upgrades
![]() - Put order in keystone credentials parameters - Add keystone auth parameters: * domain_name * trust_id - Add support for environment variables: * OS_USER_ID * OS_PROJECT_ID * OS_TENANT_ID * OS_DOMAIN_NAME * OS_DOMAIN_ID * OS_USER_DOMAIN_ID * OS_PROJECT_DOMAIN_ID * OS_TRUST_ID Co-Authored-By: Federico Ressi <fressi@redhat.com> Change-Id: I66085db690c8f72408b79b3abea9dce7c60b4ea2 |
||
---|---|---|
devstack | ||
doc | ||
infrared | ||
playbooks | ||
releasenotes | ||
roles | ||
tobiko | ||
zuul.d | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.pylintrc | ||
.stestr.conf | ||
LICENSE | ||
pep8-requirements.txt | ||
Pipfile | ||
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
- Provide a Python framework to write system scenario test cases;
- Provide CLI tools to implement a workflow designed to test potentially destructive operations (like cloud nodes reboot, update, upgrade...).
- Provide tools to monitor and recollect the healthy status of the cloud
References
- Free software: Apache License, Version 2.0
- Documentation: https://docs.openstack.org/tobiko/latest/
- Release notes: https://docs.openstack.org/releasenotes/tobiko/
- Source: https://opendev.org/x/tobiko
- Bugs: https://storyboard.openstack.org/#!/project/x/tobiko