x
/
performa
Code Issues Proposed changes
Distributed scenario runner, results processor and report generator
44 Commits 1 Branch 0 Tags 200 KiB
Python 69.3%
reStructuredText 30.6%
Shell 0.1%
Go to file
Andreas Jaeger 6d4ace51a6 Cleanup tox.ini: Remove obsolete constraints 
Remove old and unused constraints settings from tox.ini. Those
have never been used.

Note that the repo has in the past not used constraints in OpenStack
CI, this change keeps the status quo.

For more information about constraints see:
http://lists.openstack.org/pipermail/openstack-dev/2016-August/101474.html

Change-Id: I7eae051b0568adc75f384e67821eb86d1d2768ab
 		2016-08-26 18:10:38 +02:00
doc/source Rename and unify MQ / RabbitMQ scenarios 2016-03-28 16:56:06 +03:00
etc Rename and unify MQ / RabbitMQ scenarios 2016-03-28 16:56:06 +03:00
performa Kafka scenario for omsimulator 2016-04-19 15:58:04 +03:00
tools Add documentation bits 2016-03-01 13:17:11 +03:00
.coveragerc Initial Cookiecutter Commit. 2016-02-19 13:20:33 +03:00
.gitignore Initial Cookiecutter Commit. 2016-02-19 13:20:33 +03:00
.gitreview Initial Cookiecutter Commit. 2016-02-19 13:20:33 +03:00
.mailmap Initial Cookiecutter Commit. 2016-02-19 13:20:33 +03:00
.testr.conf Initial Cookiecutter Commit. 2016-02-19 13:20:33 +03:00
CONTRIBUTING.rst Initial Cookiecutter Commit. 2016-02-19 13:20:33 +03:00
HACKING.rst Initial Cookiecutter Commit. 2016-02-19 13:20:33 +03:00
LICENSE Initial Cookiecutter Commit. 2016-02-19 13:20:33 +03:00
MANIFEST.in Initial Cookiecutter Commit. 2016-02-19 13:20:33 +03:00
README.rst Add documentation bits 2016-03-01 13:17:11 +03:00
babel.cfg Initial Cookiecutter Commit. 2016-02-19 13:20:33 +03:00
config-generator.conf Add documentation bits 2016-03-01 13:17:11 +03:00
requirements.txt Proof-of-concept 2016-02-19 13:43:06 +03:00
setup.cfg Proof-of-concept 2016-02-19 13:43:06 +03:00
setup.py Initial Cookiecutter Commit. 2016-02-19 13:20:33 +03:00
test-requirements.txt Proof-of-concept 2016-02-19 13:43:06 +03:00
tox.ini Cleanup tox.ini: Remove obsolete constraints 2016-08-26 18:10:38 +02:00

README.rst

Performa

What Performa is?

Performa is distributed scenario runner, results processor and report generator. It is the strong mixture of powerful technologies: * Ansible for easy running modularized code in distributed manner * MongoDB for storing and transforming data * Pygal for creating light-weight charts * Jinja2 for templating the world

Example

performa --mongo-url 127.0.0.1 --mongo-db performa --scenario db/sysbench \
    --hosts "{target: [192.168.20.20]}" --remote-user developer --debug \
    --book doc/source/test_results/db/sysbench

This example runs Performa tool with scenario 'sb/sysbench'. It uses MongoDB located at localhost and database named 'performa'. The scenario is executed against remote host 192.168.20.20 which can be accessed with user 'developer'. The report is stored into 'doc/source/test_results/db/sysbench' folder.