c2772c2984
This makes us gather a bunch of consistent statistics after we run tempest that can be use to measure the impact of a given change. These are stable metrics such as "number of DB queries made" and "how much memory is each service using after a tempest run." Note that this will always run after devstack to generate the JSON file, but there are two things that control its completeness: - MYSQL_GATHER_PERFORMANCE must be enabled to get per-db stats - Unless tls-proxy is enabled, we will only get API stats for keystone Change-Id: Ie3b1504256dc1c9c6b59634e86fa98494bcb07b1
26 lines
611 B
ReStructuredText
26 lines
611 B
ReStructuredText
Generate performance logs for staging
|
|
|
|
Captures usage information from mysql, systemd, apache logs, and other
|
|
parts of the system and generates a performance.json file in the
|
|
staging directory.
|
|
|
|
**Role Variables**
|
|
|
|
.. zuul:rolevar:: stage_dir
|
|
:default: {{ ansible_user_dir }}
|
|
|
|
The base stage directory
|
|
|
|
.. zuul:rolevar:: devstack_conf_dir
|
|
:default: /opt/stack
|
|
|
|
The base devstack destination directory
|
|
|
|
.. zuul:rolevar:: debian_suse_apache_deref_logs
|
|
|
|
The apache logs found in the debian/suse locations
|
|
|
|
.. zuul:rolevar:: redhat_apache_deref_logs
|
|
|
|
The apache logs found in the redhat locations
|