[openstack-dev] [all][infra] Upcoming changes in ARA Zuul job reports

David Moreau Simard dmsimard at redhat.com
Thu Mar 29 22:14:06 UTC 2018


By default, all jobs currently benefit from the generation of a static
ARA report located in the "ara" directory at the root of the log
Due to scalability concerns, these reports were only generated when a
job failed and were not available on successful runs.

I'm happy to announce that you can expect ARA reports to be available
for every job from now on -- including the successful ones !

You'll notice a subtle but important change: the report directory will
henceforth be named "ara-report" instead of "ara".

Instead of generating and saving a HTML report, we'll now only save
the ARA database in the "ara-report" directory.
This is a special directory from the perspective of the
logs.openstack.org server and ARA databases located in such
directories will be loaded dynamically by a WSGI middleware.

You don't need to do anything to benefit from this change -- it will
be pushed to all jobs that inherit from the base job by default.

However, if you happen to be using a "nested" installation of ARA and
Ansible (i.e, OpenStack-Ansible, Kolla-Ansible, TripleO, etc.), this
means that you can also leverage this feature.
In order to do that, you'll want to create an "ara-report" directory
and copy your ARA database inside before your logs are collected and

To help you visualize:
<logroot>/ara-report <-- This is the default Zuul report
<logroot>/logs/ara <-- This wouldn't be loaded dynamically
<logroot>/logs/ara-report <-- This would be loaded dynamically
<logroot>/logs/some/directory/ara-report <-- This would be loaded dynamically

For more details on this feature of ARA, you can refer to the documentation [1].

Let me know if you have any questions !

[1]: https://ara.readthedocs.io/en/latest/advanced.html

David Moreau Simard
Senior Software Engineer | OpenStack RDO

dmsimard = [irc, github, twitter]

More information about the OpenStack-dev mailing list