x/browbeat
Code Issues Proposed changes
d96c8d5f7c
browbeat/ansible
History
Jenkins ca37793bc2 Merge "Add var for pacemaker"
2016-12-07 13:21:50 +00:00
..
browbeat Add var for pacemaker 2016-12-07 13:04:07 +00:00
check Merge "Fix logic to check for partitions" 2016-10-10 19:14:16 +00:00
gather Add Glance metadata parsing 2016-10-12 08:10:05 -04:00
install Add sshd dns toggle to speed up Ansible 2016-12-06 18:59:43 +00:00
oooq Add oooq Ansible Role Support 2016-11-30 20:34:31 +00:00
tune convert remaining markdown to rst. 2016-06-22 09:57:01 +01:00
ansible.cfg Add oooq Ansible Role Support 2016-11-30 20:34:31 +00:00
generate_tripleo_hostfile.sh Fix generate_tripleo_hostfile.sh 2016-09-21 19:58:19 -04:00
README.cfme-allinone.rst Remove CFME collectd/dashboarding. 2016-06-28 10:16:41 -04:00
README.collectd-generic.rst Remove CFME collectd/dashboarding. 2016-06-28 10:16:41 -04:00
README.rst Kibana visuals and dashboards for OpenStack 2016-09-09 14:57:16 -04:00
README.shaker-viz.rst Adding Visualizations and Dashboard for Shaker 2016-11-29 12:29:32 -05:00

README.shaker-viz.rst

Shaker Data Plane Performance Dashboard

The 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).

You can filter based on browbeat_uuid and shaker_uuid to view results from a specific run only.