[tripleo][openstack-ansible] Integrating ansible-role-collect-logs in OSA
chkumar246 at gmail.com
Fri Jun 28 11:00:17 UTC 2019
With os_tempest project, TripleO and Openstack Ansible projects
started collaborating together to reuse the tools
developed by each other to avoid duplicates and enable more collaboration.
During Denver Train 2019 PTG, we decided to unifying the CI logs for
both the projects
by providing a unified experience to the developers while browsing the
CI logs making sure we have a similar
logs structure for both the projects, so that one can easily navigate
through the logs without scratching the
heads and also the logs tree structure should say what logs are present where.
In TripleO, we have ansible-role-collect-logs[1.] role for the same
and in OSA we have logs_collect.sh[2.] script for
the same. But once the logs gets collected at each other projects, It
is very hard to navigate and find out where
is the respective files.
A little about ansible-role-collect-logs roles:
* A role for aggregating logs from different nodes
* Provide a list for files to collect at one places in playbook 
* Hyperlink the logs with description about log files
* Once logs collection is done, it pushes to a particular log server
For example, tempest.html or stestr_results.html is the common file
for viewing tempest results. In TripleO, we keep it
under logs folder but in OSA
logs/openstack/aio1-utility/stestr_results.html. If a new user
contributes to another project,
he tries to follow the same pattern for find logs as he seen in
current project. By Keeping the same structure at all places
It would be easier.
So moving ahead what we are going to do:
* Refactor collect-logs role to pass defaults list of files at one place
* Pass the list of different logs files based on deployment tools
* Put system/containers related commands at one place
* Replace the collect_logs.sh script with playbook in OSA and replace it.
Thanks for reading, We are looking for the comments on the above suggestion.
More information about the openstack-discuss