Bug 575150

Summary:	Need to be able to configure maximum cluster id
Product:	Red Hat Enterprise MRG	Reporter:	Scott Spurrier <spurrier>
Component:	condor	Assignee:	Erik Erlandson <eerlands>
Status:	CLOSED ERRATA	QA Contact:	Martin Kudlej <mkudlej>
Severity:	medium	Docs Contact:
Priority:	high
Version:	1.2	CC:	fnadge, jthomas, lbrindle, matt, mkudlej, tao
Target Milestone:	1.3
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	7.4.3-0.8	Doc Type:	Bug Fix
Doc Text:	This update adds the new parameter SCHEDD_CLUSTER_MAXIMUM_VALUE, which sets the maximum value of the cluster ID. The parameter defaults to 0, which results in the cluster ID being unbounded.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-10-14 16:06:48 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:	583993
Bug Blocks:

Description Scott Spurrier 2010-03-19 15:38:46 UTC

Description of problem:

The customers applications that use LSF cluster id's expect a maximum cluster id of 9999999 and their types are set up for that.  They would like to limit the maximum cluster id in condor to never exceed 9999999, where the cluster id rolls back over to a minimum value.

Comment 1 Erik Erlandson 2010-03-22 20:59:26 UTC

Added new parameter SCHEDD_CLUSTER_MAXIMUM_VALUE.  Default is 0 (no max).

Comment 5 Martin Kudlej 2010-07-29 14:32:55 UTC

I've tested this issue on RHEL 5.5/4.8 x i386/x86_64 with QMF/condor_submit/SOAP. Submitting over low-latency has no meaning. 
Basic feature functionality works. --> VERIFIED

Comment 7 Florian Nadge 2010-10-07 13:56:27 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, applications that use LSF cluster id's expected a maximum cluster id of 9999999 and their types were set up for this maximum.  This update adds the new parameter SCHEDD_CLUSTER_MAXIMUM_VALUE, which is by default set to 0 and not to the maximum.

Comment 8 Florian Nadge 2010-10-08 08:24:55 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-Previously, applications that use LSF cluster id's expected a maximum cluster id of 9999999 and their types were set up for this maximum.  This update adds the new parameter SCHEDD_CLUSTER_MAXIMUM_VALUE, which is by default set to 0 and not to the maximum.+This update adds the new parameter SCHEDD_CLUSTER_MAXIMUM_VALUE, with which the maximum value of cluster id. default is set to 0, which means the  value of the cluster id is unbounded.

Comment 9 Florian Nadge 2010-10-08 08:58:28 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-This update adds the new parameter SCHEDD_CLUSTER_MAXIMUM_VALUE, with which the maximum value of cluster id. default is set to 0, which means the  value of the cluster id is unbounded.+This update adds the new parameter SCHEDD_CLUSTER_MAXIMUM_VALUE, with which the maximum value of cluster id. default is set to 0. This means that  value of the cluster id is unbounded.

Comment 10 Lana Brindley 2010-10-12 02:08:35 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-This update adds the new parameter SCHEDD_CLUSTER_MAXIMUM_VALUE, with which the maximum value of cluster id. default is set to 0. This means that  value of the cluster id is unbounded.+This update adds the new parameter SCHEDD_CLUSTER_MAXIMUM_VALUE, which sets the maximum value of the cluster ID. The parameter defaults to 0, which results in the cluster id being unbounded.

Comment 11 Lana Brindley 2010-10-12 02:09:15 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-This update adds the new parameter SCHEDD_CLUSTER_MAXIMUM_VALUE, which sets the maximum value of the cluster ID. The parameter defaults to 0, which results in the cluster id being unbounded.+This update adds the new parameter SCHEDD_CLUSTER_MAXIMUM_VALUE, which sets the maximum value of the cluster ID. The parameter defaults to 0, which results in the cluster ID being unbounded.

Comment 13 errata-xmlrpc 2010-10-14 16:06:48 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0773.html