Bugzilla – Bug 3088
Default Job Environment
Last modified: 2012-09-05 11:42:35
You need to log in before you can comment on or make changes to this bug.
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.
Reassigning to current GRAM developer to close/fix as appropriate.
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