Testing OpenStack upgrades
Go to file
Federico Ressi 2c38d883bb Use special RHOSP vars files in tobiko-ensure-python3 role
Change-Id: I09055d0610ddc26c0ada947f95d823c28e9494b4
2020-06-10 05:33:10 +00:00
devstack Use the new ansible roles for DevStack CI jobs 2020-04-27 08:17:01 +02:00
doc Remove faults integration documentation 2020-02-19 10:15:23 +01:00
etc/oslo-config-generator Autogenerate config options and sample config file 2019-07-18 17:51:49 +02:00
infrared_plugin Automaticall use Python 3.8 IR patch when required 2020-06-09 12:15:14 +02:00
playbooks Test Tobiko against Python 3.8.2 2020-05-14 07:30:26 +02:00
releasenotes Fix requirements and use ReadTheDocs HTML documentation theme 2019-05-07 17:00:32 +02:00
roles Use special RHOSP vars files in tobiko-ensure-python3 role 2020-06-10 05:33:10 +00:00
tobiko Add support for tags at image creation 2020-06-09 11:14:52 +02:00
tools Delete IR workspace before importing new one 2020-06-09 14:59:10 +02:00
zuul.d Automaticall use Python 3.8 IR patch when required 2020-06-09 12:15:14 +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 Create Docker files for Tobiko project 2020-06-01 10:19:21 +02:00
.gitignore Refactor test execution scripts 2020-05-06 17:41:35 +02:00
.gitreview OpenDev Migration Patch 2019-04-19 19:51:27 +00:00
.stestr.conf Fix requirements and use ReadTheDocs HTML documentation theme 2019-05-07 17:00:32 +02:00
ansible.cfg Let automate coloring in infrared environment 2020-03-26 14:47:13 +01:00
bindep.txt Remove python3-devel package from RHEL-7 bindeps 2020-06-03 16:00:18 +02:00
docker-compose.yml Create Docker files for Tobiko project 2020-06-01 10:19:21 +02:00
Dockerfile Create Docker files for Tobiko project 2020-06-01 10:19:21 +02:00
LICENSE Add common module for handling clients 2018-08-15 16:10:50 +03:00
linters-requirements.txt Add support for tags at image creation 2020-06-09 11:14:52 +02:00
Pipfile Add tobiko-fault command 2019-03-20 14:14:33 +02:00
README.rst Drop support for Python3.5 2020-01-16 13:07:38 +01:00
requirements.txt Create Docker files for Tobiko project 2020-06-01 10:19:21 +02:00
setup.cfg Execute test cases with InfraRed plugin on CenOS and Ubuntu 2020-03-20 10:36:35 +00:00
setup.py Add initial structure 2018-08-13 12:58:24 +00:00
test-requirements.txt Refactor test execution scripts 2020-05-06 17:41:35 +02:00
tobiko.conf.example Add simple Octavia traffic scenario 2019-11-26 19:13:53 +00:00
tox.ini Stop considering OpenStack upstream requirements good for InfraRed Tox 2020-05-22 14:01:50 +00:00
Vagrantfile Fix Tox Infrared job 2020-02-18 15:40:01 +01: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 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.

Project Requirements

Tobiko Python framework is being tested with below Python versions:

  • Python 3.6
  • Python 3.7
  • Python 3.8

and below Linux distributions:

  • CentOS 7 (with Python 3.6 and 3.8)
  • Ubuntu Bionic (with Python 3.6 and 3.7)

The framework is being used for executing 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 tested Python versions or Linux distributions.

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