nova GMR doesn't provide option to specify log_dir path

[Divya K Konoor]

oslo_report https://github.com/openstack/oslo.reports/blob/master/oslo_reports/guru_meditation_report.py#L109 gives a provision to specify a log directory that could be used to save GMR when user sends signal to a processes. When the log_dir is not specified, the report gets dumped into stderr .

Currently, nova (and other services that support GMR) doesn't have a provision to specify a log dir . Due to this, GMR gets dumped to stderr and often gets lost along with thousands of other log statements. As GMR is used primarily for debug purposes, it makes a lot of sense to have a separate file/directory that captures the report . This way, it's also much easier to share the output of GMR and keep it archived for later reference if required. This problem can be fixed by providing a new section in the respective service conf files something like the below:

[oslo_report]
log_dir = /home/abc/gmr

[Markus Zoeller (markus_z) (mzoeller)]

@Divya K Konoor (dikonoor):

This sounds more like a change request than an actual bug. Change requests are done via "blueprints" in Launchpad [1] and their design get reviewed in "spec files" in Gerrit [2]. The process is described in [3]. The current "Liberty" cycle has reached "feature freeze" [4], this means you can propose this change for the next "Mitaka" release and use [5] for that. Since I consider this not a bug, I close it and ask you do create a blueprint. Maybe Arun Mani can help you with the implementation of the blueprint.

[1] https://blueprints.launchpad.net/nova
[2] https://git.openstack.org/cgit/openstack/nova-specs/
[3] https://wiki.openstack.org/wiki/Blueprints
[4] https://wiki.openstack.org/wiki/Nova/Liberty_Release_Schedule#Feature_Freeze
[5] https://git.openstack.org/cgit/openstack/nova-specs/tree/specs/mitaka-template.rst