x/browbeat
Code Issues Proposed changes
Performance monitoring and testing of OpenStack
80 Commits 1 Branch 0 Tags 23 MiB
Jinja 49.2%
Python 46.8%
Shell 3.7%
Dockerfile 0.3%
b76fb24200
Go to file
Joe Talerico b76fb24200 Added pass/fail
2015-11-09 15:37:27 -05:00
ansible Added pass/fail 2015-11-09 15:37:27 -05:00
connmon Update to Results directory 2015-10-28 13:10:44 -04:00
graphing Adjust rally graphing for directory changes. 2015-10-30 11:59:53 -04:00
keystone Fixed times in keystone-cc, adjusted concurrency of keystone tests, pad concurrency in task output log/html file. 2015-09-28 08:14:38 -04:00
neutron Adding Readme to directories 2015-09-23 10:01:59 -04:00
nova One more update 2015-09-24 15:49:43 -04:00
pbench Move install script to pbench folder. 2015-10-23 11:23:12 -04:00
browbeat-run-rally.sh Adding pbench to browbeat 2015-10-06 14:25:46 -04:00
browbeat.sh Post-process, however... I am not convinced it is needed. 2015-10-29 16:56:29 -04:00
README.md Fix 2015-09-29 07:39:09 -04:00

README.md

Browbeat

Scripts to help determine number of workers a given OpenStack service needs.

How to run Browbeat?

On the Red Hat OpenStack Director host, as the Stack user jump into a venv w/ Rally and you simply run:

./browbeat

What is necessary?

  • Red Hat OpenStack Director
    • Why? We use the keyless ssh to reach each controller node to maniuplate and check # of workers
  • OpenStack Rally
    • Why? We are using Rally to stress the control plane of the env.