Rally (https://github.com/openstack/rally) is a performance analysis/benchmark tool that interacts with various OpenStack components.
Downstream, it is mainly used to check the various API latencies. There are no active maintainers from Red Hat contributing to Rally.
As part of the Open Decision Framework, how/if Rally should carry over to Nextgen testing should be discussed.

Requirements:

• To support Rally testing in OpenStack Nextgen CI, it is encouraged to consider adapting https://github.com/openstack-k8s-operators/test-operator to support the Rally framework.
  This will require extending the operator to support executing Rally scenarios using Kubernetes Custom Resources.
• To execute Rally, a fully deployed cloud is required (in our case, EDPM, which is the dataplane overcloud). It is invoked using the `rally` Python utility.
  It leverages the various OpenStack endpoints to allow running different performance analysis scenarios. Based on the available OpenStack endpoints, multiple scenarios are possible. The user ensures that Rally has all the required authentication, and Rally will run the scenarios.

Requirements Maintainers: Based on the ODF decision.

Used by: Rally is used primarily by downstream Neutron CI jobs.

Reviewers: Based on the ODF decision.

Example of existing Jenkins stage for Rally:  https://code.engineering.redhat.com/gerrit/gitweb?p=rhos-qe-jenkins.git;a=blob;f=jobs/defaults/stages/ir_rally_run.groovy.inc;h=bd3563f052a941ef2b6b8598554a9556a06ea132;hb=refs/heads/master