akrzos 56483b1222 Remove line stacking where it does not make sense
Mainly this improves the cloud specific log dashboard displaying
error messages across multiple nodes in a cloud. There was a few
other graphs that stacked lines unnecessarily include as well.

Change-Id: I4ec8136b532e8aa1c00dc19b0892c383f15c194d
2017-01-06 15:41:20 -05:00
..
2016-12-07 13:04:07 +00:00
2017-01-05 13:44:26 -05:00
2016-06-22 09:57:01 +01:00
2016-11-30 20:34:31 +00: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.