Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 634092

Summary:	grid: need configuration parameter settings for Job Server
Product:	Red Hat Enterprise MRG	Reporter:	Jan Sarenik <jsarenik>
Component:	Management_Console_Installation_Guide	Assignee:	Alison Young <alyoung>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jan Sarenik <jsarenik>
Severity:	high	Docs Contact:
Priority:	medium
Version:	beta	CC:	iboverma, jsarenik, matt, pmackinn, rrati, tmckay, tross
Target Milestone:	2.0
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	631477	Environment:
Last Closed:	2011-06-24 01:37:31 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	631477, 652506
Bug Blocks:	660531

Description Jan Sarenik 2010-09-15 08:18:10 UTC

This clone is made so the Job Server text may be included in the
documentation in later release, though the original 1.3 problem was
solved with a shorter paragraph.

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

Section 3.2

<New subsection -> Job Server configuration>

A Job Server must be configured in the Grid pool in order for cumin to show job submissions and details. The Job Server can be configured in one of two modes:

1) as a feature of the Schedd plugin that can provide job data for jobs in the Schedd job queue log
2) as a dedicated daemon process with the same ability as #1 plus is able to provide data for jobs that have been moved to history files

The decision between using one mode over the other is purely a deployment choice. Mode #2 can provide historical job submission data (which mode #1 cannot) while offloading the processing of this data from the Schedd. However, it requires more configuration than the simpler plug-in mode.

For mode #1, add the following parameter to the same configuration as the Schedd plug-in:

	QMF_PUBLISH_SUBMISSIONS = True

For mode #2, use these settings:

	QMF_PUBLISH_SUBMISSIONS = False
	HISTORY	= $(SPOOL)/history
	JOB_SERVER = $(SBIN)/condor_job_server
	JOB_SERVER_ARGS = -f
	JOB_SERVER.JOB_SERVER_LOG = $(LOG)/JobServerLog
	JOB_SERVER.JOB_SERVER_ADDRESS_FILE = $(LOG)/.job_server_address
	JOB_SERVER.SCHEDD_NAME = <the name assigned to the scheduler>
	DAEMON_LIST = $(DAEMON_LIST) JOB_SERVER
	DC_DAEMON_LIST = + JOB_SERVER

Optionally add or modify these settings:

	HISTORY_INTERVAL = 60 (default is 120 seconds)
	JOB_SERVER.JOB_SERVER_DEBUG = D_FULLDEBUG (for detailed logging)

--- Additional comment from lbrindle on 2010-09-14 00:09:32 EDT ---

This was covered in a previous BZ:

<para>
	If a JobServer daemon will be used, also add the following line:
</para>
				 
<programlisting>
QMF_PUBLISH_SUBMISSIONS = FALSE
</programlisting>

LKB

--- Additional comment from jsarenik on 2010-09-15 04:15:29 EDT ---

I suppose this shortened mention of JobServer is sufficient for 1.3
but the detailed description written by Pete should be included in
future versions - so I am duplicating this bug and setting target
to 1.4.

Verified in Revision 3.4, as of Wed Sep 15 2010.

--- Additional comment from jsarenik on 2010-09-15 04:16:23 EDT ---

I meant "cloning this bug".

Comment 3 Pete MacKinnon 2011-02-24 16:33:05 UTC

Alison,

I'm a little confused about where the previous job server content has gone. I'm referring to:

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.3/html/Management_Console_Installation_Guide/index.html

All that is listed under 1.3.2 at that site are the Release Notes. What am I missing?

\Pete

Comment 4 Robert Rati 2011-02-24 16:58:32 UTC

Can we get information on the changes to this section?  The missing data was verified on version 3.4, but since then I've see a number of bzs that look to be point at/modifying that section (like bz632429).

Comment 7 Jan Sarenik 2011-03-09 13:13:21 UTC

Please remove text in brackets in the following configuration file
snippet:

HISTORY_INTERVAL = 60 (default is 120 seconds)
JOB_SERVER.JOB_SERVER_DEBUG = D_FULLDEBUG (for detailed logging)

Seen on Revision 5-2, Mon Feb 28 2011.

Comment 8 Jan Sarenik 2011-03-09 13:15:40 UTC

Note: the information contained in brackets is reprinted in
paragraph below the configuration file snippet, see section
4.1.1. Job Server Configuration.

Comment 9 Alison Young 2011-03-10 00:31:47 UTC

Noted, thanks.

Comment 10 Alison Young 2011-04-07 05:28:21 UTC

Change made in revision 5-3, build: Red_Hat_Enterprise_MRG-Management_Console_Installation_Guide-1.3-web-en-US-5-3.el5

Code snippet:
<programlisting>
HISTORY_INTERVAL = 60 
JOB_SERVER.JOB_SERVER_DEBUG = D_FULLDEBUG
</programlisting>

Comment 11 Jan Sarenik 2011-04-07 07:09:07 UTC

Verified in Revision 5-3 as of Thu Apr 07 2011. Thanks!