Hey folks, So as part of the capture-environment-status-and-logs blueprint[0], I'm working on adding a single command to perform status and log collection of the overcloud nodes via the tripleoclient that can be used on the undercloud. I would like to bring up switching over to this as part of our CI log collection activities as many of the relevant logs we want are already captured via the sosreport tool. Additionally this is the way many operators are collecting and reporting their logs when submitting issues.
I think this would benefit us to switch as sosreports also capture additional status of the services at the time of the report and we can improve sosreports via plugins to help diagnose frequent service related problems. I believe we're duplicating some of the items already covered via sosreport in tripleo-quickstart-extras[1] and I think it would be beneficial to not continue to duplicate this work but rather use already available tooling. For CI once we have these sosreport bundles, it would be fairly straight forward to only extract relevant information for debugging use. If you have some time, please review the outstanding reviews[2] and provide concerns around possibly switching over to relying on sosreport for our log collection. Thanks, -Alex [0] https://blueprints.launchpad.net/tripleo/+spec/capture-environment-status-and-logs [1] https://github.com/openstack/tripleo-quickstart-extras/tree/31dd4b5756b8811a9e2cb9aa0aad81bcceacd653/roles/collect-logs [2] https://review.openstack.org/#/q/topic:bp/capture-environment-status-and-logs __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev