264d2a2e5f
process-stackviz role currently defined in Tempest repo[1] and used in tempest jobs. Issue with having it in branchless Tempest is that any fix in that role cannot be backported to older Tempest. Also stackviz is not Tempest things it is only used by Tempest jobs. Stackviz can be considered as a service similar to Tempest so inatlling it in Devstack side make sense. Also that will give us advantage to handle the branch specific fixes or backpoting the fixes. This can solve the current issues we are facing on rocky branch - https://zuul.opendev.org/t/openstack/build/c1e2da80537448bfb24331fb4198a931/console#4/0/29/controller [1] https://opendev.org/openstack/tempest/src/branch/master/roles/process-stackviz Change-Id: I0ba1fd05c6391cd8bb978119ecfbb891def2d497
23 lines
550 B
ReStructuredText
23 lines
550 B
ReStructuredText
Generate stackviz report.
|
|
|
|
Generate stackviz report using subunit and dstat data, using
|
|
the stackviz archive embedded in test images.
|
|
|
|
**Role Variables**
|
|
|
|
.. zuul:rolevar:: devstack_base_dir
|
|
:default: /opt/stack
|
|
|
|
The devstack base directory.
|
|
|
|
.. zuul:rolevar:: stage_dir
|
|
:default: "{{ ansible_user_dir }}"
|
|
|
|
The stage directory where the input data can be found and
|
|
the output will be produced.
|
|
|
|
.. zuul:rolevar:: zuul_work_dir
|
|
:default: {{ devstack_base_dir }}/tempest
|
|
|
|
Directory to work in. It has to be a fully qualified path.
|