Utilities for consistent cleanup after Tempest run.

Registered by David Paterson on 2014-04-30

The existing code \tempest\stress\cleanup.py can be used to do some general cleanup after a Tempest run but a more robust tool is needed to completely reset the environment including some database surgery should a test failure leave the system in a strange state.

Blueprint information

Status:
Complete
Approver:
Matthew Treinish
Priority:
Medium
Drafter:
David Paterson
Direction:
Approved
Assignee:
David Paterson
Definition:
Approved
Series goal:
Accepted for juno
Implementation:
Implemented
Milestone target:
milestone icon juno-3
Started by
Matthew Treinish on 2014-07-25
Completed by
Matthew Treinish on 2014-10-20

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/post-run-cleanup,n,z

Addressed by: https://review.openstack.org/91725
    Add spec for bp:post-run-cleanup

Addressed by: https://review.openstack.org/91777
    Add spec for bp:post-run-cleanup

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

Addressed by: https://review.openstack.org/101241
    Add spec for bp:post-run-cleanup

Addressed by: https://review.openstack.org/112581
    Add tempest post-run cleanup script

Addressed by: https://review.openstack.org/112641
    Add tempest post-run cleanup script

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.