Bug 5852 - Make use of default factory resource in job submission with globusrun-ws
: Make use of default factory resource in job submission with globusrun-ws
Status: RESOLVED FIXED
: GRAM
wsrf gram clients
: alpha
: Macintosh All
: P2 normal
: 4.2
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2008-02-06 12:08 by
Modified: 2008-02-06 13:46 (History)


Attachments


Note

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


Description From 2008-02-06 12:08:08
see bug 5744.

A job can be submitted without specifying a factory resource in 4.2.
In this case it will be submitted to the factory resource specified
as the default in the JNDI configuration of Gram.

globusrun-ws should replace it's current behavior and not submit
to Fork by default but just not specify a factory resource at all
if a user does not specify it explicitely.
------- Comment #1 From 2008-02-06 12:43:27 -------
Committed change to the ws-gram-bug5247. Might need support in the Factory
service to properly dispatch Multi jobs based on the job input element.
------- Comment #2 From 2008-02-06 13:46:50 -------
committed the following change to ws-gram-bug5247:
a client does not need to provide reference parameters for multijobs.
Regardless of what is configured as default local resource manager: multi
jobs will always go to Multi. The subjobs don't need to specify reference
parameters, but can.
Also: An admin must not configure Multi as default factory. This will result
in an error message in container startup and an error message per submitted
job.