x/browbeat
Code Issues Proposed changes
37548ba704
browbeat/ansible
History
venkata anil 37548ba704 set right config path for containers 
Containers use configuration files from the path
/var/lib/config-data/puppet-generated/<service/
and not from /var/lib/config-data/<service>/

Change-Id: I1e5c4935b72fcabd5256d0bf8014cae3beb314a4
2018-08-31 17:05:57 +05:30
..
bootstrap Allow bootstrap.py tripleo to work with Older OSP releases 2018-07-02 13:59:09 -04:00
browbeat Enable linter test for ANSIBLE0013 2018-08-10 14:28:36 +00:00
check Enable linter test for ANSIBLE0013 2018-08-10 14:28:36 +00:00
gather set right config path for containers 2018-08-31 17:05:57 +05:30
install Merge "Simplify package installs" 2018-08-16 15:00:33 +00:00
logs Add .gz extension to logs archive 2018-07-30 10:26:25 +05:30
oooq Add changes to enable running in CI 2018-08-01 15:33:24 +00:00
tune convert remaining markdown to rst. 2016-06-22 09:57:01 +01:00
ansible.cfg Disable host key checking in ansible.cfg 2018-01-16 17:37:11 -05:00
bootstrap.py Python ssh-config+Ansible Inventory Generator 2018-05-25 11:28:47 -04:00
generate_tripleo_hostfile.sh Add changes to enable running in CI 2018-08-01 15:33:24 +00: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

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.