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

Bug 631477

Summary: grid: need configuration parameter settings for Job Server
Product: Red Hat Enterprise MRG Reporter: Pete MacKinnon <pmackinn>
Component: Management_Console_Installation_GuideAssignee: Lana Brindley <lbrindle>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Sarenik <jsarenik>
Severity: high Docs Contact:
Priority: low    
Version: betaCC: iboverma, jsarenik, matt, mhideo, rrati, tross
Target Milestone: 1.3   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 634092 (view as bug list) Environment:
Last Closed: 2010-10-14 20:26:54 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:    
Bug Blocks: 634092    

Description Pete MacKinnon 2010-09-07 19:14:15 UTC
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)

Comment 1 Lana Brindley 2010-09-14 04:09:32 UTC
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

Comment 2 Jan Sarenik 2010-09-15 08:15:29 UTC
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.

Comment 3 Jan Sarenik 2010-09-15 08:16:23 UTC
I meant "cloning this bug".