History

akrzos c34543f909 Transition to GrafYaml for Dashboard Storage Reasons to move from json, json.j2 to yaml/yaml.j2 + GrafYaml: * Yaml is less lines * Yaml allows comments * Yaml means less curly braces and quotes * GrafYaml manages panel ids and target refIds * GrafYaml defaults reduce number of lines stored * GrafYaml allows more easily cut/paste management of Dashboards Identified Downsides: * GrafYaml will be behind the Grafana Dashboard Model (Until code is updated) * Json will always allow full feature set * Installing Dashboards now requires GrafYaml New Dashboards/Features: * Templated Dashboards (Reduce line count in "static" dashboards) * Cloud Specific networks - all dashboard * Three Node Performance Food groups Enhanced * Networker Node added for Cloud Specific Dashboards and Total Memory Change-Id: I55ce9f9f6c28497c8b4ed7a19d42657a8eb14170		2018-02-27 10:20:18 -05:00
..
browbeat	Pike support for Nova allocation ratio adjustment playbook	2018-01-17 17:40:35 +00: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	Transition to GrafYaml for Dashboard Storage	2018-02-27 10:20:18 -05:00
oooq	Turned off log summaries until fixed	2018-01-31 22:05:44 -05:00
tune	convert remaining markdown to rst.	2016-06-22 09:57:01 +01:00
README.collectd-generic.rst	Small fixes/updates to collectd install	2017-01-12 10:04:49 -05:00
README.rst	Remove connmon	2017-10-11 10:47:30 -04:00
README.shaker-viz.rst	Adding Cloud Comparison Dashboard for Shaker	2017-01-18 13:42:23 -05:00
ansible.cfg	Disable host key checking in ansible.cfg	2018-01-16 17:37:11 -05:00
generate_tripleo_hostfile.sh	Playbook to adjust security parameters	2018-01-13 14:31:14 -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.