4969f31ce1
Updated ansible-lint to run via pre-commit only on ansible files. Moved config file to its standard location, repository root, which simplifies syncronization and usage. Contains bumping ansible-lint to current version which also required adding few more rule excludes. These excludes are going to be removed one by one in follow-up changes. This gradual approach allow us to improve code style without endless merge conflicts. Config settings mostly based on those used by tripleo repos. Bumping linters can now be done by running 'pre-commit autoupdate'. Pro-commit always locks versions so there is no chance that a newer linter (ansible-lint) would break CI. Some documentation can be found at https://github.com/openstack/tripleo-quickstart/blob/master/doc/source/contributing.rst and applies mostly to any project using pre-commit. Co-Authored-By: Sorin Sbarnea <ssbarnea@redhat.com> Change-Id: I05eb561c4e353b5fe0bc7c6d3ab2f8ea6c6ea2f4
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.