x/tobiko
Code Issues Proposed changes
Testing OpenStack upgrades
2,344 Commits 2 Branches 31 Tags 41 MiB
Python 99.5%
Shell 0.2%
Dockerfile 0.2%
7ab82b6512
Go to file
Federico Ressi 7ab82b6512 Make Actor class generic type 
This allow to specify a protocol for an actor as below:

  class Protocol:
     "Class containing abstact methods to be implemented"

  class MyActor(Actor[MyProtocol]):
      "Class containing methods implementations"

Move tobiko.common._proxy module to tobilo.actors
Mova tobiko.actor._actor module to tobiko.actors

Change-Id: Ic9a7440a870c48db9449ccec907599eaaab88cfd
2022-03-01 13:01:53 +01:00
doc Refactor Tobiko installation guide 2022-01-24 09:58:13 +00:00
etc Update tobiko.conf documentation page 2022-01-21 11:23:52 +00:00
infrared_plugin Add option to select test cases by markers 2022-02-15 14:56:17 +00:00
playbooks Generate SSH keys on the first host in the inventory 2022-02-08 13:55:52 +01:00
releasenotes Moves RTD theme requirements definition 2021-09-29 11:29:25 +00:00
roles Add option to select test cases by markers 2022-02-15 14:56:17 +00:00
tobiko Make Actor class generic type 2022-03-01 13:01:53 +01:00
tools Fix bindeps installation on CentOS 2022-01-21 14:36:34 +00:00
zuul.d Use CentOS 9 on tobiko-tripleo jobs 2022-02-22 13:53:41 +00: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 Ignore named report files .gitignore 2022-02-01 08:06:57 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:51:27 +00:00
.pre-commit-config.yaml Update mypy linters hook 2022-01-10 13:42:54 +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 bindep file to support Debian Linux 2022-01-21 14:35:48 +00:00
docker-compose.yml Allow containers to write to ~/.ssh 2022-01-31 15:09:59 +00:00
Dockerfile Use Fedora 34 for the lower-constraints and Infrared containers 2022-01-31 16:03:54 +01:00
extra-requirements.txt Add ReporPortal PyTest plugin 2022-02-15 05:50:05 +01: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 Update lower constraints file 2022-02-04 12:58:17 +00: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 Update lower constraints file 2022-02-04 12:58:17 +00: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 HA tests included in the faults-neutron workflow 2022-02-10 11:00:16 +01:00
upper-constraints.txt Update upper constraints file 2021-12-21 14:49:16 +00:00

README.rst

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

Related projects