x/browbeat
Code Issues Proposed changes
d00d2c41de
browbeat/ansible
History
Sai Sindhur Malleni d00d2c41de Remove unused shaker vars & make img configurable 
This commit removes unused vars for shaker install. Some vars are not
needed due to https://review.openstack.org/#/c/490967/. Also, this
commit makes the image name configurable (user can choose between
centos7 and ubuntu).

Change-Id: I46114fb66064804cb4f00056eebe945a51270af6
2017-10-03 11:01:30 -04:00
..
browbeat Remove Grafana Snapshot 2017-09-13 15:25:20 -06:00
check Update tox.ini with Ansible linting and Browbeat config linting 2017-03-29 07:35:34 -04:00
gather Initial refactor 2017-09-14 13:11:50 -06:00
install Remove unused shaker vars & make img configurable 2017-10-03 11:01:30 -04:00
oooq Move bml repo pointer back to jkilpatr 2017-09-26 11:49:31 +00:00
tune convert remaining markdown to rst. 2016-06-22 09:57:01 +01:00
ansible.cfg Playbooks to help with Telemetry testing. 2017-07-17 14:49:17 -04:00
generate_tripleo_hostfile.sh Sort Controllers in Ansible Inventory file 2017-08-22 10:48:46 -04:00
README.collectd-generic.rst Small fixes/updates to collectd install 2017-01-12 10:04:49 -05:00
README.rst Kibana visuals and dashboards for OpenStack 2016-09-09 14:57:16 -04:00
README.shaker-viz.rst Adding Cloud Comparison Dashboard for Shaker 2017-01-18 13:42:23 -05:00

README.shaker-viz.rst

Shaker Data Plane Performance Dashboards

Two dashboards have been provided with Browbeat for Shaker.

Browbeat Shaker Scenarios with Throughput vs Concurrency -------------------------------------------------------This Shaker dashboard aims to present data plane performance of OpenStack VMs connected in different network topologies in a summarized form. Three distinct visulizations representing L2, L3 E-W and L3 N-S topologies along with the corrensponding markdown to exaplain each visualization make the "Browbeat Shaker Scenarios with Throughput vs Concurrency" dashboard. For each network topology, average throughput for TCP download and upload in Mbps is expressed vs the VM conccurency (number of pairs of VMs firing traffic at any given moment). For example, in the L2 scenario if the average throughput is 4000 Mbps at a concurrency of 2, it means that each pair of VMs involved average at 4000 Mbps for the duration of the test, bringing the total throughput to 8000 Mbps(avg throughput*concurrency).

Browbeat Shaker Cloud Performance Comparison

This Shaker dashboard lets you compare network performance results from various clouds. This dashboard is ideal if you want to compare data plane performance with different neutron configurations in different clouds. For each topology, a visualization comparing tcp_download and tcp_upload per cloud name and a visualization comparing ping latency per cloud name is generated in the dashboard along with instructions in markdown for advanced filtering and querying.

Note

You can filter based on browbeat_uuid and shaker_uuid to view results from a specific run or shaker scenario only and record.concurrency and record.accommodation to filter based on the subest of the test results you want to view.