Testing OpenStack upgrades
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Slawek Kaplonski e33a3bc507 Include all project requirements in doc/requirements.txt file 22 hours ago
doc Include all project requirements in doc/requirements.txt file 21 hours ago
etc/oslo-config-generator Autogenerate config options and sample config file 1 year ago
infrared_plugin tobiko IR version : set default execution version to 0.3.1 tag 4 weeks ago
playbooks Remove DevStack support from tobiko repository 3 months ago
releasenotes Add check requirements job 2 weeks ago
roles Update requirements 2 weeks ago
tobiko Temporarily replace compute hard reboot by soft reboot test due to BZ1890895 1 day ago
tools Add check requirements job 2 weeks ago
zuul.d Execute only one infrared job on check and gate pipelines, all of them on periodic 1 week ago
.ansible-lint Spliting infrared plugin into roles 10 months ago
.coveragerc Relax low coverage trealdshold 1 year ago
.dockerignore Update Dockerfile to use bindep and tox 7 months ago
.gitignore gitignore add .idea 2 months ago
.gitreview OpenDev Migration Patch 1 year ago
.pre-commit-config.yaml Remove -j0 option from pylint pre-commit hook 6 months ago
.stestr.conf Fix requirements and use ReadTheDocs HTML documentation theme 1 year ago
Dockerfile Update Dockerfile to use bindep and tox 7 months ago
LICENSE Introduce pre-commit hooks for linters verifications 6 months ago
Pipfile Add tobiko-fault command 1 year ago
README.rst Update documentation 1 month ago
ansible.cfg Rewrite Vagrant file using ansible and Centos 8 7 months ago
bindep.txt Add centos-7 support 4 months ago
docker-compose.yml Update Dockerfile to use bindep and tox 7 months ago
extra-requirements.txt Add check requirements job 2 weeks ago
linters-requirements.txt Pass broken jobs with Python 3.8 (Ubuntu Focal and Fedora 32) 1 month ago
lower-constraints.txt Add check requirements job 2 weeks ago
requirements.txt Add check requirements job 2 weeks ago
setup.cfg Switch to pytest test runner 1 month ago
setup.py Add initial structure 2 years ago
test-requirements.txt Add check requirements job 2 weeks ago
tobiko.conf.example Add simple Octavia traffic scenario 1 year ago
tox.ini Let lower-constraints job not using upper-constraints file 1 week ago

README.rst

Tobiko 0.3

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 is 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 Nova instances; they execute disruption operations such as services/nodes restart; finally they run test cases to validate that the cloud workloads are still functional.

Tobiko's test cases can also be used, for example, for testing that previously created workloads are working right after OpenStack services update/upgrade operation.

Project Requirements

Tobiko Python framework is being automatically tested with below Python versions:

  • Python 3.6
  • Python 3.8
  • Python 3.9 (new)

and below Linux distributions:

  • CentOS 7 / RHEL 7 (with Python 3.6)
  • CentOS 8 / RHEL 8 (with Python 3.6)
  • Ubuntu Focal (with Python 3.8)

Tobiko has also been tested for development purposes with below OSes:

  • Fedora 31 (with Python 3.7)
  • Fedora 32 (with Python 3.8)
  • Fedora 33 (with Python 3.9)
  • OSX (with Python 3.6 and Python 3.8)
  • Ubuntu Bionic (with Python 3.6)
  • Ubuntu Focal (with Python 3.9)

The Tobiko Python framework is being used to implement test cases. As Tobiko can be executed on nodes that are not part of the cloud to test against, this doesn't mean Tobiko requires cloud nodes have to run with one of above Python versions or Linux distributions.

Main Project Goals

  • To test OpenStakc and Red Hat OpenStack Platform projects before they are released.
  • To provide a Python framework to write system scenario test cases (create and test workloads), to write white boxing test cases (to log to cloud nodes for internal inspection purpose), to write disruptive test cases (to simulate service disruptions like for example rebooting/interrupting a service to verify cloud reliability).
  • To provide Ansible roles to implement a work-flow designed to run an ordered sequence of test cases groups (like for example tests that creates resources and verify they are working, tests that execute cloud disruptions, and finally tests that verify if resources initially created are still working). The main use of these roles is writing continuous integration jobs for Zuul (via bare Ansible roles) or other services like Jenkins (via the InfraRed plug-in).
  • To verify previously created workloads are working fine after executing OpenStack nodes update/upgrade.
  • 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