Dan Smith c2772c2984 Gather performance data after tempest ... 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		2022-04-20 13:07:22 -07:00
..
tox	Fix: do not lose the tox_environment value in func tests	2020-10-11 21:59:07 +02:00
unit-tests	Add Zuul v3 native unit-tests	2018-02-04 21:42:00 +01:00
devstack.yaml	Enforce linear strategy for orchestrate-devstack	2018-03-11 11:17:42 +00:00
post.yaml	Gather performance data after tempest	2022-04-20 13:07:22 -07:00
pre.yaml	Decrease MTU to account for IPv6 header	2020-11-06 17:34:53 -05:00