Testing OpenStack upgrades
Go to file
Eduardo Olivares f178b798d2 External subnets with DHCP enabled should not be ignored
Tobiko considers no external networks exist when the existing one have
no subnets with DHCP disabled.
With this patch, any external network with subnets is accepted,
regardless of having DHCP enabled or disabled.

Related-Issue: https://issues.redhat.com/browse/TOBIKO-105
Change-Id: Ib2e00fc0581e08abe55a903c167ad70f4490c506
2024-08-08 09:14:50 +02:00
doc Upgrade sphinx version 2024-03-20 08:30:12 +00:00
etc Update tobiko.conf documentation page 2022-01-21 11:23:52 +00:00
infrared_plugin Update latest stable tag to 0.7.3 2024-07-08 17:07:32 +02:00
playbooks Download ubuntu images prior to pytest execution 2023-02-03 08:20:04 +00:00
releasenotes Add support to skip tests from CLI 2023-12-04 12:17:26 +01:00
roles Set correct tox_min_version for the stable/2023.2 branch 2024-03-26 08:22:09 +00:00
tobiko External subnets with DHCP enabled should not be ignored 2024-08-08 09:14:50 +02:00
tools Remove dependency with vulnerable library py - upgrade to tox>=4.13 2024-03-06 12:41:03 +01:00
zuul.d Remove docker-tobiko jobs from check pipeline 2024-05-29 10:49:07 +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 Fix two issues that broke tobiko gates 2024-03-08 13:50:08 +01:00
.pylintrc Add .pylintrc file and disable dict-values-not-iterating check 2022-03-11 23:09:15 +01:00
.readthedocs.yaml Stop using "system_packages" in readthedocs builds 2023-09-15 06:36:51 +00: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 Dropping python3.6 and python3.7 support 2023-08-25 15:39:07 +02: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 topology which represents Podified RHOSP deployment 2023-12-12 12:43:48 +00: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 Refactoring tobiko lockers 2024-03-08 12:50:51 +00:00
mypy.ini Make Actor class generic type 2022-03-01 13:01:53 +01:00
Pipfile Dropping python3.6 and python3.7 support 2023-08-25 15:39:07 +02:00
pytest.ini Fix ovn_migration and ovn_migration_sanity testenvs 2024-04-12 08:55:16 +02:00
README.rst Fix link to Red Hat Openstack Platform reference 2024-02-29 13:19:12 +01:00
requirements.txt Refactoring tobiko lockers 2024-03-08 12:50:51 +00:00
setup.cfg Dropping python3.6 and python3.7 support 2023-08-25 15:39:07 +02:00
setup.py Add initial structure 2018-08-13 12:58:24 +00:00
test-requirements.txt Remove dependency with vulnerable library py - upgrade to tox>=4.13 2024-03-06 12:41:03 +01:00
tobiko.conf.example Update tobiko.conf documentation page 2022-01-21 11:23:52 +00:00
tox.ini Fix tox testenvs with incorrect test paths 2024-07-10 08:42:13 +00:00
upper-constraints.txt Pin numpy to 1.26.4 (python3.9) 2024-06-18 08:53:03 +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.8
  • Python 3.9
  • Python 3.10 (new)

and below Linux distributions:

  • CentOS 9 / RHEL 8 (with Python 3.9)
  • Ubuntu Focal (with Python 3.8)
  • Ubuntu Jammy (with Python 3.10)

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

  • OSX (with Python 3.6 to 3.10)

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