The OpenStack Tempest integration test suite was originally designed for testing code changes at the gate via Jenkins continuous integration.  This is still Tempest’s primary use case and is crucial to insuring code changes are not able to break a functioning source tree.  Tempest by itself does not provide a way to persist test results for historical purposes, nor does it provide any reporting functionality for comparing test runs to identify deltas between runs.  Another OpenStack project, Rally, fills these gaps in Tempest.

 

In this technical session we will illustrate the entire Rally verification cycle, from configuring Rally to connect to your OpenStack deployment.  We will outline best practices for running tempest, creating Rally reports that show the deltas between Tempest runs, and lastly running Tempest cleanup.