Bug 1547685

Summary:	[RFE] dump all colonizer related logs in one standard location ideally in /var/log
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Nag Pavan Chilakam <nchilaka>
Component:	gluster-colonizer	Assignee:	Ramakrishna Reddy Yekulla <rreddy>
Status:	CLOSED DEFERRED	QA Contact:	Rahul Hinduja <rhinduja>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rhgs-3.3	CC:	rhs-bugs, rreddy
Target Milestone:	---	Keywords:	FutureFeature, RFE, Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-18 09:54:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nag Pavan Chilakam 2018-02-21 17:34:06 UTC

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

Comment 2 Dustin Black 2018-02-21 17:52:43 UTC

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.

Comment 3 Jeff Applewhite 2018-02-22 15:18:02 UTC

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

Comment 4 Nag Pavan Chilakam 2018-04-18 09:57:19 UTC

(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

Comment 7 Ramakrishna Reddy Yekulla 2018-11-20 04:32:26 UTC

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.

Comment 8 Yaniv Kaul 2019-04-18 09:54:43 UTC

Closing all Colonizer BZs (as DEFERRED) as we do not intend to work on them for the time being.