Testing OpenStack upgrades
Go to file
Federico Ressi 3eadbe21f9 Set remote test directories owner user
Change-Id: I007b5f88a72f4c3a821466358d0c3793008354cf
2020-04-22 13:49:13 +00:00
devstack Test against stable/train with DevStack and CentOS 7 2020-04-20 14:29:20 +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 Set remote test directories owner user 2020-04-22 13:49:13 +00:00
playbooks Switch to 2-node configuration for IR plugin testing 2020-04-15 15:56:13 +02:00
releasenotes Fix requirements and use ReadTheDocs HTML documentation theme 2019-05-07 17:00:32 +02:00
roles Set remote test directories owner user 2020-04-22 13:49:13 +00:00
tobiko Change order conf files are imported 2020-04-20 14:29:20 +02:00
tools Implement test workflow steps 2020-04-08 14:32:58 +02:00
zuul.d Test against stable/train with DevStack and CentOS 7 2020-04-20 14:29:20 +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
.gitignore Spliting infrared plugin into roles 2020-03-17 11:07:08 +00: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
LICENSE Add common module for handling clients 2018-08-15 16:10:50 +03: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
Vagrantfile Fix Tox Infrared job 2020-02-18 15:40:01 +01:00
ansible.cfg Let automate coloring in infrared environment 2020-03-26 14:47:13 +01:00
bindep.txt Implement test workflow steps 2020-04-08 14:32:58 +02:00
infrared-requirements.txt Use default python for testing infrared plugin 2020-03-23 15:47:59 +01:00
linters-requirements.txt Test that DHCP lease is correctly served when DHCP agent is down 2020-03-31 14:21:19 +00:00
report-requirements.txt Make reports with python-subunit>=1.4 2020-04-02 09:58:17 +02:00
requirements.txt Remove unused integrations: os_faults and ansible 2020-02-19 17:35:09 +00: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 Update requrements files. 2019-04-08 11:58:37 +02:00
tobiko.conf.example Add simple Octavia traffic scenario 2019-11-26 19:13:53 +00:00
tox.ini Move infrared plugin to infrared_plugin/ folder 2020-04-21 17:54:42 +02: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 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