Bug 1017410

Summary:	Configure Grinder when running on a CDS to log to it's own file.
Product:	Red Hat Update Infrastructure for Cloud Providers	Reporter:	Dan Macpherson <dmacpher>
Component:	Documentation	Assignee:	Megan Lewis <melewis>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Dan Macpherson <dmacpher>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.1.2	CC:	jmatthew, melewis, tsanders
Target Milestone:	---
Target Release:	2.1.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1017310	Environment:
Last Closed:	2014-01-23 23:59:42 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:
Bug Depends On:	1017310
Bug Blocks:

Description Dan Macpherson 2013-10-09 20:03:39 UTC

+++ This bug was initially created as a clone of Bug #1017310 +++

Description of problem:

We would like to see Grinder writing to it's own log file on a CDS during sync.

The proposed change is to modify how the CDS configures the python logging and use a logging configuration file similar to what pulp-server does.

--- Additional comment from John Matthews on 2013-10-09 11:40:56 EDT ---

Added a config entry to /etc/pulp/cds.conf to control what logging config file to load
   log_config_file = /etc/pulp/logging/cds.cfg

Introduced new logging configuration file:  /etc/pulp/logging/cds.cfg
   https://github.com/splice/pulp/blob/rhui/etc/pulp/logging/cds.cfg

To view the CDS logs, look at:
 /var/log/pulp-cds/pulp.log    <- Pulp specific (was gofer.log)
 /var/log/pulp-cds/grinder.log <- Grinder specific

Gofer log is still at:
  /var/log/gofer/agent.log


Associated commit:
https://github.com/splice/pulp/commit/438e944f22d35393497023fb07cce23e8e9bd366

Comment 3 Dan Macpherson 2013-11-15 07:00:09 UTC

Looking good, Megan. Probably a few minor things to rectify:

Procedure 3.2. View CDS Logs
- Make sure the log file paths/filenames are marked up with <filename>

Procedure 3.9. Add a New CDS Log
Step 1 - Make the "note" admonition and "important" one
Step 2 - In "Add a new entry to keys under [loggers] for the new log.", mark [loggers] as a <literal>
Step 3 - Make mention that the new logger section needs to start with "logger_"
Step 5 - Mark up each value with <parameter>

But you've pretty much captured what's required. Excellent :)

Comment 5 Dan Macpherson 2013-12-02 01:53:22 UTC

Looks good. Verified.

Comment 6 Dan Macpherson 2014-01-23 23:59:42 UTC

This documentation issue has been fulfilled and pushed live to access.redhat.com