Performance monitoring and testing of OpenStack
Go to file
2015-11-24 15:47:42 -05:00
ansible Moved Performance check ansible plays to seperate folder 'check'. 2015-11-24 15:47:42 -05:00
connmon Update to Results directory 2015-10-28 13:10:44 -04:00
graphing Allow matplotlib to run without a screen. 2015-11-14 09:32:19 -05: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
rally-plugins Update the neutron plugin to create networks. 2015-11-22 14:49:11 -05:00
browbeat-run-rally.sh Adding pbench to browbeat 2015-10-06 14:25:46 -04:00
browbeat.sh Logic fix 2015-11-04 17:54:22 -05:00
README.md Fix 2015-09-29 07:39:09 -04:00

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.