Description of problem: ====================== we are currently dumping different colonizer logs or outputs at different locations gluster-colonizer.log is being dumped in the $pwd from where colonizer script is deployed README.txt which contains final snippet of deployment details is dumped in default directory ie ~ or /root similarly are the perf results dumped in ~ or /root/ We must be dumping all logs in one location ideally, it can be /var/log/gluster-colonizer, as a best practice Version-Release number of selected component (if applicable): ========= 1.0.1-2
I chose not to put the main script log, gluster-colonizer.log, into the /var/log directory because it is not an ongoing service but a one-time utility. It seems reasonable to me for that reason that the main log output be placed into $pwd, but I'm willing to be persuaded otherwise. The other files you mention are not exactly logs. The readme file I don't think belongs under /var/log at all. It could also be placed in $pwd, but I felt personally that placing it in /root made more sense. The same goes for the performance script output. This file contains run results, not logs, and so I believe does not belong in /var/log. Again, /root seemed like the most logical place to me for this file to be placed.
I think a reasonable fix is to create a symlink to things going in the log dir in $pwd or in $home so that they appear easily for the user but are centrally logged
(In reply to Jeff Applewhite from comment #3) > I think a reasonable fix is to create a symlink to things going in the log > dir in $pwd or in $home so that they appear easily for the user but are > centrally logged +1
I have opened an upstream RFE issue for the same, the runtime logging can happen on $PWD but standard logging of colonizer as an application can be enabled.
Closing all Colonizer BZs (as DEFERRED) as we do not intend to work on them for the time being.