browbeat/ansible
akrzos 97bc7bc21e Small fixes/updates to collectd install
+ Fix installing collectd on cephstorage host type
+ Remove old collectd configuration documentation
+ Have check playbook run against cephstorage hosts (previously it was just ceph)

Change-Id: Ic53351da1a6fd9951984301ec16ba75fdd0fe1c7
2017-01-12 10:04:49 -05:00
..
browbeat Add var for pacemaker 2016-12-07 13:04:07 +00:00
check Small fixes/updates to collectd install 2017-01-12 10:04:49 -05:00
gather Make metadata robust to missing services 2016-12-15 12:47:11 +00:00
install Small fixes/updates to collectd install 2017-01-12 10:04:49 -05:00
oooq Update API workload 2017-01-05 13:44:26 -05: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 Adding ObjectStorage Node type 2017-01-03 16:15:10 -05: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 Visualizations and Dashboard for Shaker 2016-11-29 12:29:32 -05:00

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.