[saga-rg] JobService.submitJob() query

Graeme Pound G.E.POUND at soton.ac.uk
Mon Feb 20 10:24:32 CST 2006


Andre,


 > 'SAGA_HostList' is on the job, and read only - it gives
 > information on where the job _is_ running, not where it
 > _should_ run.

I do not follow you here. 'SAGA_HostList' is an attribute of 
JobDefinition (not JobInfo), therefore it should not be read only.

Graeme


Andre Merzky wrote:
> Uhm, I think you got us there.  I don't see any way to
> specify the resource either, so its left completely up to
> the backend to schedule the job.  I am not sure if that was
> intended.
> 
> Chris, are we missing something?  Did we intend to leave
> resource specification out?  Can't really be, as we have it
> in run_job as Graeme points out...
> 
> 'SAGA_HostList' is on the job, and read only - it gives
> information on where the job _is_ running, not where it
> _should_ run.
> 
> Andre.
> 
> 
> Quoting [Graeme Pound] (Feb 20 2006):
>> Hi,
>>
>> Can anybody clear up this issue for me? I may be missing something in 
>> the spec.
>>
>> Thanks,
>>   Graeme
>>
>>
>>  -3.31 How is the resource manager endpoint for JobService.submitJob() 
>> specified?
>>
>> The endpoint is specified by an argument of JobService.runJob(), but is 
>> not _obvious_ for submitJob(). Is the endpoint a property of the 
>> instance of JobService (with runJob() a 'static' method of the class), 
>> or is the endpoint specified as an attribute of JobDefinition?
>>
>> I assume that the contents of the JobDefinition attribute 
>> 'SAGA_HostList' is intended to be passed to the resource manager (rather 
>> than specify the resource manager itself); for example mapping to the 
>> 'CandidateHosts' element of a JSDL document. Is an additional attribute 
>> within JobDefinition required to specify the endpoint?
> 
> 
> 





More information about the saga-rg mailing list