Bug 3088 - Default Job Environment
: Default Job Environment
Status: RESOLVED WONTFIX
: GRAM
wsrf managed execution job service
: development
: Macintosh All
: P3 enhancement
: 4.2
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-04-06 12:16 by
Modified: 2012-09-05 11:42 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2005-04-06 12:16:48
There has been interest expressed in a way to allow the administrator to
specify default environment 
settings for jobs through the GRAM configuration files.  I'd recommend adding
this to the scheduler-
specific jndi-config.xml files as a simi-colon separated list of name/value
pairs as follows:

<parameter>
  <name>
    extraEnvironment
  </name>
  <value>
    GLOBUS_TCP_PORT_RANGE=1234,4321;GLOBUS_TCP_SOURCE_RANGE=5678,8765;
CONDOR_CONFIG=/fake/path/to/condor_config
  </value>
</parameter>

The GRAM code should user-supplied env vars in the job description over the
values specified in the 
config.
------- Comment #1 From 2007-09-19 11:37:54 -------
Reassigning to current GRAM developer to close/fix as appropriate.
------- Comment #2 From 2012-09-05 11:42:35 -------
Doing some bugzilla cleanup...  Resolving old GRAM3 and GRAM4 issues that are
no longer relevant since we've moved on to GRAM5.  Also, we're now tracking
issue in jira.  Any new issues should be added here:

http://jira.globus.org/secure/VersionBoard.jspa?selectedProjectId=10363