Testing OpenStack upgrades
Go to file
Eduardo Olivares 532c091567 Add support for OSP13 to assert_ovn_containers_running
Container names differ between OSP13 and OSP16:
ovn-dbs-bundle-podman-<number>
ovn-dbs-bundle-docker-<number>

Besides, OVN agents are not listed in OSP13, so the method to
identify whether OVN is configured or not has been changed.

Change-Id: If77fca4ff7ba030a89543ff4b712a26ff037b699
2020-03-11 14:19:17 +01:00
devstack Find an external network when no one is provided 2020-02-20 08:23:19 +01: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
playbooks Restore TripleO CI jobs using new Tobiko role 2020-02-12 08:50:03 +00:00
releasenotes Fix requirements and use ReadTheDocs HTML documentation theme 2019-05-07 17:00:32 +02:00
roles fix for : remove os-faults bug and commented ha checks 2020-03-08 13:15:54 +02:00
tobiko Add support for OSP13 to assert_ovn_containers_running 2020-03-11 14:19:17 +01:00
tools/ci unblock Downstream CI : STDERR: virtualenv.py: error: no such option: --seeder 2020-02-21 01:45:42 +02:00
zuul.d Remove fedora nodeset 2020-03-10 10:40:19 +01:00
.ansible-lint Create Ansible role to install arbitrary Python version 2019-12-16 10:31:32 +01:00
.coveragerc Relax low coverage trealdshold 2019-10-16 12:51:55 +02:00
.gitignore Fix Tox Infrared job 2020-02-18 15:40:01 +01: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 Create Tox InfraRed upstream job 2020-01-16 15:53:38 +00:00
bindep.txt Fix Tox Infrared job 2020-02-18 15:40:01 +01:00
linters-requirements.txt Add ansible playbooks linters job 2019-12-13 17:35:41 +00:00
report-requirements.txt Use master branch of python-subunit to generate reports 2019-12-18 15:22:11 +00:00
requirements.txt Remove unused integrations: os_faults and ansible 2020-02-19 17:35:09 +00:00
setup.cfg Remove unused integrations: os_faults and ansible 2020-02-19 17:35:09 +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 Fix stack creation bug 2020-02-25 16:16:53 +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