59ce1d902e
Currently we only export the devstack@ services, and then separately export the kernel & sudo logs to syslog.txt. This leaves a lot of logs potentially behind in the journal for various daemons. Just export the whole lot. Using this output is currently very opaque and makes use of systemd export tools that are very un-discoverable. Add a README that will appear alongside the journal explaining how to actually use it. This is a template as it would be nice to put into things like the list of services that are in the journal, or maybe other magic. Also make sure we export the logs since the start timestamp; currently during a full run we drop the initial logs. Change-Id: Id2626f9113d82c6d524039acda8a8ec74afb2081 |
||
|---|---|---|
| .. | ||
| defaults | ||
| tasks | ||
| templates | ||
| README.rst | ||
Export journal files from devstack services
This performs a number of logging collection services
- Export the systemd journal in native format
- For every devstack service, export logs to text in a file named
screen-*to maintain legacy compatability when devstack services used to run in a screen session and were logged separately. - Export a syslog-style file with kernel and sudo messages for legacy compatability.
Writes the output to the logs/ subdirectory of
stage_dir.
Role Variables