Testing OpenStack upgrades
Go to file
pkomarov 3e6880aa17 Fixes: ansible shell non needed quotes :
TASK [Install pip using get-pip.py] ********************************************
task path: /root/rhos-ci/jenkins/workspace/DFG-network-neutron-14_director-rhel-virthost-3cont_2comp-ipv4-vxlan-tobiko/infrared/plugins/tobiko/infrared/tasks/install.yml:1
Saturday 28 September 2019  17:31:57 +0300 (0:00:00.181)       0:00:13.996 ****
fatal: [undercloud-0]: FAILED! => {
    "changed": true,
    "cmd": "\"curl https://bootstrap.pypa.io/get-pip.py | python2\"",
    "delta": "0:00:00.011237",
    "end": "2019-09-28 10:31:58.071984",
    "rc": 127,
    "start": "2019-09-28 10:31:58.060747"
}

STDERR:

/bin/sh: curl https://bootstrap.pypa.io/get-pip.py | python2: No such file or directory

MSG:

non-zero return code

Change-Id: I280263782e846fb78dd51cdccfbb18aac2db3812
2019-09-29 16:05:40 +03:00
.tobiko-env/lib/python2.7/site-packages/neutron_lib/tests/etc Add SSH connectivity to overcloud nodes. 2019-08-29 14:12:26 +03:00
devstack Automatically create SSH key file if it doesn't exists 2019-07-22 11:46:52 +02:00
doc Remove RTD Pip requirements file. 2019-09-24 11:14:19 +02:00
etc/oslo-config-generator Autogenerate config options and sample config file 2019-07-18 17:51:49 +02:00
infrared Fixes: ansible shell non needed quotes : 2019-09-29 16:05:40 +03:00
playbooks Merge "Set path for tobiko logs in devstack tobiko jobs" 2019-09-26 08:44:04 +00:00
releasenotes Fix requirements and use ReadTheDocs HTML documentation theme 2019-05-07 17:00:32 +02:00
report Add tox environment to generate HTML test case reports. 2019-05-23 13:04:16 +02:00
roles Set path for tobiko logs in devstack tobiko jobs 2019-09-25 20:33:19 +00:00
tobiko Write to log the begin and the end of every test case. 2019-09-28 07:43:08 +00:00
tools/ci Add tool to print out yaml file to js format 2019-07-04 10:39:18 +02:00
zuul.d Merge "Set path for tobiko logs in devstack tobiko jobs" 2019-09-26 08:44:04 +00:00
.coveragerc Add cover CI job and tox env 2019-04-25 09:58:55 +00:00
.gitignore Add tobiko.conf to .gitignore file 2019-07-19 17:41:54 +02:00
.gitreview OpenDev Migration Patch 2019-04-19 19:51:27 +00:00
.pylintrc Add pylint static analysis test. 2018-11-27 10:37:24 +01: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
pep8-requirements.txt Fix requirements and use ReadTheDocs HTML documentation theme 2019-05-07 17:00:32 +02:00
Pipfile Add tobiko-fault command 2019-03-20 14:14:33 +02:00
plugin.spec allow specifying custom tobiko gerrit 2019-06-25 05:12:15 +00:00
README.rst Update tobiko documentation page URL. 2019-06-06 15:52:23 +02:00
requirements.txt Add glance client to requirements file. 2019-07-19 17:41:54 +02:00
setup.cfg Autogenerate config options and sample config file 2019-07-18 17:51:49 +02: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 Use the IPv6 documentation prefix as the default cidr 2019-09-19 17:54:22 -04:00
tox.ini Refactor OS-faults integration 2019-09-24 13:47:36 +02:00
Vagrantfile Update DevStack plugin after Keystone auth params improvement 2019-05-09 14:30:41 +00: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 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.

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