Chapter 7. Cleaning Tempest Resources
After running tempest
, there are files, users and tenants created in the testing process that must be deleted. Being able to self-clean is one of the design principles of tempest
.
7.1. Performing a Clean Up
First, you must initialize the saved state. This creates the file saved_state.json
, which prevents the cleanup from deleting objects that need to be kept. Typically you would run cleanup with --init-saved-state
prior to a tempest run. If this is not the case, saved_state.json
must be edited to remove objects that you want cleanup to delete.
# tempest cleanup --init-saved-state
Run the cleanup:
# tempest cleanup
The tempest cleanup
command deletes tempest resources but does not delete projects or the tempest administrator account.
7.2. Performing a Dry Run
It is recommended to perform a dry run before executing the real cleanup. A dry run lists the files that would be deleted by a cleanup, but does not delete any files. The files are listed in the dry_run.json
file. Check the dry_run.json
file to ensure that the cleanup does not delete any files that you require for your environment.
# tempest cleanup --dry-run
7.3. Deleting Tempest Objects
Run the following command to delete all tempest resources, including projects, but not the tempest administrator account:
# tempest cleanup --delete-tempest-conf-objects