Testing OpenStack upgrades
Go to file
Eduardo Olivares 643b180873 [BGP] undercloud_ssh_key_filename added to infrared plugin options
The undercloud_ssh_key_filename was a configurable parameter, but the
infrared plugin and the tobiko-configure role did not support it
This patch adds support to configure a value for this parameter using
the infrared tobiko plugin

Change-Id: I79929044034d6e457a4673195613cc69c24afa3e
2022-11-24 12:37:00 +01:00
doc Fix sphinx_rtd_theme in doc requirements 2022-09-07 09:12:40 +00:00
etc Update tobiko.conf documentation page 2022-01-21 11:23:52 +00:00
infrared_plugin [BGP] undercloud_ssh_key_filename added to infrared plugin options 2022-11-24 12:37:00 +01:00
playbooks Generate SSH keys on the first host in the inventory 2022-02-08 13:55:52 +01:00
releasenotes Create module to capture output of ss command 2022-09-07 12:48:17 +03:00
roles [BGP] undercloud_ssh_key_filename added to infrared plugin options 2022-11-24 12:37:00 +01:00
tobiko [BGP] Fix test_equal_containers_state 2022-11-24 12:37:00 +01:00
tools Configure limit of opened files for the test runner process 2022-08-19 16:54:04 +02:00
zuul.d Update private key which should be used to sync github mirror 2022-10-13 09:57:03 +02:00
.ansible-lint Spliting infrared plugin into roles 2020-03-17 11:07:08 +00:00
.coveragerc Relax low coverage trealdshold 2019-10-16 12:51:55 +02:00
.dockerignore Refactor container files 2021-11-12 13:40:42 +00:00
.gitignore Move TripleO ansible inventory file to .ansible/inventory folder 2022-05-25 14:46:25 +02:00
.gitreview OpenDev Migration Patch 2019-04-19 19:51:27 +00:00
.pre-commit-config.yaml Update URL for flake8 from gitlab to github 2022-11-16 15:22:30 +01:00
.pylintrc Add .pylintrc file and disable dict-values-not-iterating check 2022-03-11 23:09:15 +01:00
.stestr.conf Fix requirements and use ReadTheDocs HTML documentation theme 2019-05-07 17:00:32 +02:00
ansible.cfg Rewrite Vagrant file using ansible and Centos 8 2020-06-23 11:47:17 +02:00
bindep.txt Update OpenStack jobs 2022-07-21 16:22:12 +00:00
docker-compose.yml Update OpenStack jobs 2022-07-21 16:22:12 +00:00
Dockerfile Update OpenStack jobs 2022-07-21 16:22:12 +00:00
extra-requirements.txt Add pytest-subtests plugin 2022-07-25 09:35:42 +02:00
LICENSE Introduce pre-commit hooks for linters verifications 2020-07-03 06:15:47 +00:00
linters-requirements.txt Update pre-commit hooks configuration 2021-12-21 14:46:44 +01:00
lower-constraints.txt Fix finally verify_osp_version using packaging lib 2022-07-06 12:43:18 +02:00
mypy.ini Make Actor class generic type 2022-03-01 13:01:53 +01:00
Pipfile Add tobiko-fault command 2019-03-20 14:14:33 +02:00
pytest.ini Add 'minimal' marker to pytest.ini file 2022-02-16 16:40:25 +00:00
README.rst Remove version from the README file 2022-02-13 11:51:44 +01:00
requirements.txt Fix finally verify_osp_version using packaging lib 2022-07-06 12:43:18 +02:00
setup.cfg Mark Python 3.9 and 3.10 as supported runtime 2022-02-18 06:46:23 +01:00
setup.py Add initial structure 2018-08-13 12:58:24 +00:00
test-requirements.txt Update lower constraints file 2022-02-04 12:58:17 +00:00
tobiko.conf.example Update tobiko.conf documentation page 2022-01-21 11:23:52 +00:00
tox.ini Update OpenStack jobs 2022-07-21 16:22:12 +00:00
upper-constraints.txt Add pytest-subtests plugin 2022-07-25 09:35:42 +02:00

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 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
  • Python 3.10 (new)

and below Linux distributions:

  • CentOS 7 / RHEL 7 (with Python 3.6)
  • CentOS 8 / RHEL 8 (with Python 3.6)
  • CentOS 9 / RHEL 8 (with Python 3.9) (new)
  • Fedora 34 (with Python 3.9)
  • Fedora 35 (with Python 3.10)
  • Ubuntu Focal (with Python 3.8)

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

  • OSX (with Python 3.6 to 3.10)
  • Ubuntu Bionic (with Python 3.6)

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.

There is also a Docker file that can be used to create a container for running test cases from any node that do support containers execution.

Main Project Goals

  • To test OpenStack 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 verify previously created workloads are working fine after executing OpenStack nodes update/upgrade.

  • 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 implementing a workflow designed to run an ordered sequence of test suites. For example a workflow could do below steps:

    • creates workloads;
    • run disruptive test cases (IE reboot OpenStack nodes or services);
    • verify workloads are still working.

    The main use of these roles is writing continuous integration jobs for Zuul or other services like Jenkins (IE by using the Tobiko InfraRed plug-in).

  • To provide tools to monitor and recollect the healthy status of the cloud as seen from user perspective (black-box testing) or from an inside point of view (white-box testing built around SSH client).

References