x
/
tobiko
Code Issues Proposed changes
Testing OpenStack upgrades
1,577 Commits 2 Branches 24 Tags 40 MiB
Python 99.5%
Shell 0.2%
Dockerfile 0.2%
Go to file
Arkady Shtempler 0e1ed4901c Check LB "provisioning_status" and improving Netcat Cirros HTTP stub 
We need to check LB "provisioning_status" in addition to
"operating_status" to make sure that the LB is ACTIVE.

Improve Netcat command used to emulate HTTP server/stub on Cirros
members. Current implementation doesn't send any HTTP response
header back to client (not standard HTTP) and tools like: WGET and CURL
are facing issues because of that, for example:
CURL -  "curl: (56) Recv failure: Connection reset by peer"
WGET - "Length: unspecified" + retries.

Change-Id: I650d7bc09a19264f8a9f811b6cd5bac7a26c107e
 		2021-02-16 20:04:51 +02:00
doc [docs] Updated quickstart guide and example conf file 2021-02-12 15:00:27 -05:00
etc/oslo-config-generator Autogenerate config options and sample config file 2019-07-18 17:51:49 +02:00
infrared_plugin Use tobiko 0.4.0 as default version for Downstream jobs 2021-02-09 10:40:17 +01:00
playbooks Remove DevStack support from tobiko repository 2020-10-01 14:34:39 +02:00
releasenotes Add check requirements job 2021-01-05 13:35:44 +01:00
roles Gate Tobiko projects running faults test cases 2021-02-02 08:16:58 +00:00
tobiko Check LB "provisioning_status" and improving Netcat Cirros HTTP stub 2021-02-16 20:04:51 +02:00
tools Update pytest reports generation 2021-02-04 15:07:23 +00:00
zuul.d Gate changes using the default faults job 2021-02-12 14:13:02 +01: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 Update Dockerfile to use bindep and tox 2020-06-19 07:39:26 +02:00
.gitignore gitignore add .idea 2020-11-22 10:31:22 +02:00
.gitreview OpenDev Migration Patch 2019-04-19 19:51:27 +00:00
.pre-commit-config.yaml Remove -j0 option from pylint pre-commit hook 2020-07-24 10:39:58 +00:00
.stestr.conf Fix requirements and use ReadTheDocs HTML documentation theme 2019-05-07 17:00:32 +02:00
Dockerfile Update Dockerfile to use bindep and tox 2020-06-19 07:39:26 +02:00
LICENSE Introduce pre-commit hooks for linters verifications 2020-07-03 06:15:47 +00:00
Pipfile Add tobiko-fault command 2019-03-20 14:14:33 +02:00
README.rst Fixed typo in README 2021-02-10 10:03:06 -05:00
ansible.cfg Rewrite Vagrant file using ansible and Centos 8 2020-06-23 11:47:17 +02:00
bindep.txt Add centos-7 support 2020-09-01 13:31:28 +02:00
docker-compose.yml Update Dockerfile to use bindep and tox 2020-06-19 07:39:26 +02:00
extra-requirements.txt Use pytest-cov plugin for getting coverage 2021-01-27 21:11:21 +00:00
linters-requirements.txt Pass broken jobs with Python 3.8 (Ubuntu Focal and Fedora 32) 2020-12-10 13:00:04 +01:00
lower-constraints.txt Add check requirements job 2021-01-05 13:35:44 +01:00
pytest.ini Update pytest reports generation 2021-02-04 15:07:23 +00:00
requirements.txt Remove last dependency from stestr 2021-01-28 04:41:33 +00:00
setup.cfg Switch to pytest test runner 2020-12-18 13:51:08 +00:00
setup.py Add initial structure 2018-08-13 12:58:24 +00:00
test-requirements.txt Use pytest-cov plugin for getting coverage 2021-01-27 21:11:21 +00:00
tobiko.conf.example [docs] Updated quickstart guide and example conf file 2021-02-12 15:00:27 -05:00
tox.ini Fix reboot when target host si not reachable 2021-02-01 10:10:26 +00:00

README.rst

Tobiko 0.3

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 (new)

and below Linux distributions:

  • CentOS 7 / RHEL 7 (with Python 3.6)
  • CentOS 8 / RHEL 8 (with Python 3.6)
  • Ubuntu Focal (with Python 3.8)

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

  • Fedora 31 (with Python 3.7)
  • Fedora 32 (with Python 3.8)
  • Fedora 33 (with Python 3.9)
  • OSX (with Python 3.6 and Python 3.8)
  • Ubuntu Bionic (with Python 3.6)
  • Ubuntu Focal (with Python 3.9)

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.

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 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 to implement a work-flow designed to run an ordered sequence of test cases groups (like for example tests that creates resources and verify they are working, tests that execute cloud disruptions, and finally tests that verify if resources initially created are still working). The main use of these roles is writing continuous integration jobs for Zuul (via bare Ansible roles) or other services like Jenkins (via the InfraRed plug-in).
  • To verify previously created workloads are working fine after executing OpenStack nodes update/upgrade.
  • 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

Related projects