Performance monitoring and testing of OpenStack
Go to file
Joe Talerico 514f76e693 Adding example of Overcloud Check
Change-Id: If5de2cf7b074057719195f4a432c6006d6fcfe1a
2016-01-05 16:13:43 -05:00
ansible Adding example of Overcloud Check 2016-01-05 16:13:43 -05:00
graphing Fix issue when graphing with rallyplot on file without results. 2015-12-16 23:05:03 -05:00
pbench Move install script to pbench folder. 2015-10-23 11:23:12 -04:00
rally First set of Cinder workload(s) 2016-01-05 15:21:21 -05:00
.gitreview Adding GerritHub as our gitreview 2015-12-09 08:45:09 -05:00
browbeat-run-rally.sh Adding pbench to browbeat 2015-10-06 14:25:46 -04:00
browbeat.cfg First set of Cinder workload(s) 2016-01-05 15:21:21 -05:00
browbeat.sh First set of Cinder workload(s) 2016-01-05 15:21:21 -05:00
README.md Updating the README.md 2016-01-05 15:28:17 -05:00
requirements.txt Break out installers. 2015-12-22 15:14:48 -05:00

Table of Contents

Browbeat

This started as a project to help determine the number of database connections a given OpenStack deployment uses. It has since grown into a set of Ansible playbooks to help check deployments for known issues, install tools and change parameters of the overcloud.

Before running browbeat

  • Execute the ansible/gen_hostfile.sh script (builds the ssh config)
  • Install Tools (rally , shaker, connmon, etc)
  • Configure browbeat.cfg to match your tests

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 <test name>

What is necessary?

  • Red Hat OpenStack Director
    • Why? We use passwordless ssh to reach each controller instance and compute instance.
  • 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.

Detailed Install, Check and Run

Installing Browbeat and running the Overcloud checks can be performed either from your local machine or from the undercloud. The local machine install/check assumes you have ansible installed already.

Install Browbeat from your local machine

From your local machine:

$ ssh-copy-id stack@<undercloud-ip>
$ git clone https://github.com/jtaleric/browbeat.git
$ cd browbeat/ansible
$ ./gen_hostfile.sh <undercloud-ip> ~/.ssh/config
$ vi install/group_vars/all # Make sure to edit the dns_server to the correct ip address
$ ansible-playbook -i hosts install/browbeat.yml

(Optional) Install shaker:

$ ansible-playbook -i hosts install/shaker.yml

(Optional) Install connmon:

$ ansible-playbook -i hosts install/connmon.yml

(Optional) Install pbench:

$ ansible-playbook -i hosts install/connmon.yml
  • pbench install is under improvement at this time and likely requires additional setup to complete install.

Run Overcloud checks

$ ansible-playbook -i hosts check/site.yml

Your Overcloud check output is located in check/bug_report.log

Run performance stress tests through browbeat on the undercloud:

$ ssh undercloud-root
[root@ospd ~]# su - stack
[stack@ospd ~]$ screen -S browbeat
[stack@ospd ~]$ . browbeat-venv/bin/activate
(browbeat-venv)[stack@ospd ~]$ cd browbeat/
(browbeat-venv)[stack@ospd browbeat]$ vi browbeat.cfg # Edit browbeat.cfg to control how many stress tests are run.
(browbeat-venv)[stack@ospd browbeat]$ ./browbeat.sh test01
...
(browbeat-venv)[stack@ospd browbeat]$ ./graphing/rallyplot.py test01

Install Browbeat directly on undercloud:

From your undercloud:

$ ssh undercloud-root
[root@ospd ~]# su - stack
[stack@ospd ~]$ git clone https://github.com/jtaleric/browbeat.git
[stack@ospd ~]$ cd browbeat/ansible
[stack@ospd ansible]$ ./gen_hostfile.sh localhost ~/.ssh/config
[stack@ospd ansible]$ sudo easy_install pip
[stack@ospd ansible]$ sudo pip install ansible
[stack@ospd ansible]$ vi install/group_vars/all # Make sure to edit the dns_server to the correct ip address
[stack@ospd ansible]$ ansible-playbook -i hosts install/browbeat.yml

(Optional) Install shaker:

[stack@ospd ansible]$ ansible-playbook -i hosts install/shaker.yml

(Optional) Install connmon:

[stack@ospd ansible]$ ansible-playbook -i hosts install/connmon.yml

(Optional) Install pbench:

[stack@ospd ansible]$ ansible-playbook -i hosts install/connmon.yml
  • pbench install is under improvement at this time and likely requires additional setup to complete install.

Run Overcloud checks

[stack@ospd ansible]$ ansible-playbook -i hosts check/site.yml

Your Overcloud check output is located in check/bug_report.log

Run performance stress tests through browbeat:

[stack@ospd ansible]$ . ../../browbeat-venv/bin/activate
(browbeat-venv)[stack@ospd ansible]$ cd ..
(browbeat-venv)[stack@ospd browbeat]$ vi browbeat.cfg # Edit browbeat.cfg to control how many stress tests are run.
(browbeat-venv)[stack@ospd browbeat]$ ./browbeat.sh test01
...
(browbeat-venv)[stack@ospd browbeat]$ ./graphing/rallyplot.py test01