Rally is tool that combines all tool together and build simple UI for end users.
You will be able in simple manner to deploy your clouds using your tool (DevStack/TrippleO/Fuel) on hardware that you have (bare metal nodes/ (virtual) servers / OpenStack), and then verify (using tempest) or benchmark it using (tempest/ or rally benchmark) and generate "report" about how cloud work: e.g.:
Rally uses tempest in 2 different ways: 1) Verification of cloud (installs tempest / generates tempest.conf / run specified set of tests or all / parse subunit results to json and store in Rally DB) 2) Rally has benchmark scenario that produce load using any of tempest unit tests (WIP)
In this session I would like to discuss next topic: 1) What can we move to tempest (e.g. tempest.confg generation) 2) How to simplify tempest.config and build sets of tests that should "pass always" 3) Measuring time inside tempest unit tests (of base actions: e.g. boot vm and wait unit it becomes in ACTIVE state) could be one "action", and this action could be reused in Rally to draw graphics with better details. 4) Future ideas about of integration, and making tempest more integratable.