Testing OpenStack upgrades
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Go to file
Federico Ressi 9c616e2c7a Create shell function to reboot an host
This adds a new function called reboot_host such that
given an SSH client to a remote host it executes /sbin/reboot command
and then it start polling for remote host uptime value to make sure
the node is actually rebooted before a given timeout.

Change-Id: I4ec2954484d6f8cc11e85f6994c174c427ec2c16
3 years ago
devstack Make sure Python 3 is installed before running DevStack 3 years ago
doc Remove RTD Pip requirements file. 4 years ago
etc/oslo-config-generator Autogenerate config options and sample config file 4 years ago
infrared Create Tox InfraRed upstream job 3 years ago
playbooks Create Tox InfraRed upstream job 3 years ago
releasenotes Fix requirements and use ReadTheDocs HTML documentation theme 4 years ago
roles Disable report files compression by default 3 years ago
tobiko Create shell function to reboot an host 3 years ago
tools/ci Fix tools/ci/tox script when 'python' command is not available 3 years ago
zuul.d Disable memory_tacker service 3 years ago
.ansible-lint Create Ansible role to install arbitrary Python version 4 years ago
.coveragerc Relax low coverage trealdshold 4 years ago
.gitignore Allow to configure undercloud via ssh_config file 3 years ago
.gitreview OpenDev Migration Patch 4 years ago
.stestr.conf Fix requirements and use ReadTheDocs HTML documentation theme 4 years ago
LICENSE Add common module for handling clients 5 years ago
Pipfile Add tobiko-fault command 4 years ago
README.rst Drop support for Python3.5 3 years ago
Vagrantfile Update Vagrantfile to use networking-ovn with DevStack 4 years ago
ansible.cfg Create Tox InfraRed upstream job 3 years ago
bindep.txt Use "platform:rhel-8" in bindep to specify it is RHEL8 3 years ago
linters-requirements.txt Add ansible playbooks linters job 4 years ago
plugin.spec Use tools/ci/tox script for running tests and making reports 3 years ago
report-requirements.txt Use master branch of python-subunit to generate reports 4 years ago
requirements.txt Podman integration 4 years ago
setup.cfg Autogenerate config options and sample config file 4 years ago
setup.py Add initial structure 5 years ago
test-requirements.txt Update requrements files. 4 years ago
tobiko.conf.example Add simple Octavia traffic scenario 4 years ago
tox.ini Create Tox InfraRed upstream job 3 years ago

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