x/browbeat
Code Issues Proposed changes
Performance monitoring and testing of OpenStack
142 Commits 1 Branch 0 Tags 23 MiB
Jinja 49.4%
Python 46.5%
Shell 3.7%
Dockerfile 0.4%
b17c61d4a5
Go to file
Joe Talerico b17c61d4a5 Organize the workload runners into their own subdir
2015-12-08 13:36:27 -05:00
ansible Ceph check was missing changed_when 2015-12-07 21:16:29 -05:00
graphing Allow matplotlib to run without a screen. 2015-11-14 09:32:19 -05:00
pbench Move install script to pbench folder. 2015-10-23 11:23:12 -04:00
rally Organize the workload runners into their own subdir 2015-12-08 13:36:27 -05:00
browbeat-config Organize the workload runners into their own subdir 2015-12-08 13:36:27 -05:00
browbeat-run-rally.sh Adding pbench to browbeat 2015-10-06 14:25:46 -04:00
browbeat.sh Organize the workload runners into their own subdir 2015-12-08 13:36:27 -05:00
README.md Update README.md 2015-11-25 18:30:50 -05: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.sh

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.
  • Ansible
    • Why? We started with using bash to make changes to the Overcloud, creating complex sed/awks that we get for free with Ansible (for the most part). If you prefer to not use Ansible, the older versions (no longer maintained) of the browbeat.sh can be found here.