Simplify stress tests and make them run

Registered by David Kranz

The current stress tests are too complicated and are not being used. The complexity is from having its own threading model and state management. Most of the benefits could be attained by running scenarios in as many threads as desired. The current tests should be replaced and put in a periodic run. More scenarios should be added.

Blueprint information

Status:
Complete
Approver:
David Kranz
Priority:
High
Drafter:
David Kranz
Direction:
Approved
Assignee:
Marc Koderer
Definition:
Approved
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
milestone icon havana-2
Started by
David Kranz
Completed by
David Kranz

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:stress-update,n,z

Addressed by: https://review.openstack.org/36752
    Rework stress to be more UnitTest like

Gerrit topic: https://review.openstack.org/#q,topic:bp/stress-tests,n,z

Addressed by: https://review.openstack.org/36820
    Add global statistic for stress tests

Gerrit topic: https://review.openstack.org/#q,topic:fix-stress-tox,n,z

Addressed by: https://review.openstack.org/37262
    Fix tox job for stress tests.

Addressed by: https://review.openstack.org/37263
    Add an option to run_stress.py to run tests serially.

Gerrit topic: https://review.openstack.org/#q,topic:bug/1201418,n,z

Addressed by: https://review.openstack.org/36652
    Add stress test to attach volumes to vm's

Addressed by: https://review.openstack.org/37180
    run_stress.py -h doesn't work without a connection

Addressed by: https://review.openstack.org/37424
    Add option to execute stress test in random order

Addressed by: https://review.openstack.org/37541
    Fix stress-tox-job.json action file.

Addressed by: https://review.openstack.org/38111
    Add exit codes if run_stress.py detects an error

Addressed by: https://review.openstack.org/39524
    Add argument to stop stress test on first error

Addressed by: https://review.openstack.org/40566
    Change logging in stress test

Gerrit topic: https://review.openstack.org/#q,topic:stress-unit,n,z

Addressed by: https://review.openstack.org/43444
    Create discovery option for stress test

(?)

Work Items

Work items:
Create sanity check for tempest/stress (dkranz): POSTPONED
Add more actions: POSTPONED
Adapt framework to allow all existing tempest test: DONE
Use oslo logger: DONE
Add parameter to stop on first error (mkoderer): DONE
Commit simple stress test: DONE
Add an entry in tox.ini to run run_stress.py: DONE
Make test action more look like a unit test: DONE
Showing the usage (-h) should not require a connection to OpenStack: DONE
Add statistics at the end of a run: DONE
Driver needs to check for failures in the actions and return process nonzero code on failure: DONE
Create a json test description for a standard test to be run in a periodic jenkins job: DONE
Create a periodic jenkins job to use this tox entry: DONE

This blueprint contains Public information 
Everyone can see this information.