132) when do we refer to target host name, and when to resource manager contact, on job submit/description? Se mail thread with Graeme/Chris "JobService.submitJob() query" - OPEN, URGENT See also the comment from Graeme to the list today below:
Andre,
The client must be able to specify the resource manager to which jobs are submitted, as a service URL or machine name. This should be a argument for either the JobService constructor, or the JobService.createJob() & JobService.runJob() methods.
I guess that conceptually I prefer specifying the resource manager during the construction of the JobService object. However in an earlier mail Chris Smith indicated that the 'host' argument of the runJob() method was originally intended to indicate the machine upon which the job should be run (mapping to an element of the SAGA_HostList attribute). This is confusing and the 'host' argument should be removed, or redefined to indicate the resource manager.
Graeme
I propose to go with Grames proposal unless there are opinions to do differently. I like the version to redefine the host arg better than to remove it altogether. Other opinions? Thanks, Andre. -- "So much time, so little to do..." -- Garfield
Andre, The document "Open Grid Services Architecture Glossary of Terms" may help resolve some of the semantic difficulties that we have been having with this topic. http://www.ggf.org/Public_Comment_Docs/Documents/Apr-2006/draft-ggf-ogsa-glo... The following terms correspond to my understanding of this subject, and are the level at which the SAGA API should operate (concealing the identity of back-end batch systems): Endpoint - A Web service endpoint to which a client may bind in order to consume a service. Job manager - In OGSA-EMS, a service that manages a set of one or more job instances, which may be structured (e.g. a workflow or dependence graph) or unstructured (e.g. an array of non-interacting jobs). Graeme Quoting Andre Merzky <andre@merzky.net>:
132) when do we refer to target host name, and when to resource manager contact, on job submit/description? Se mail thread with Graeme/Chris "JobService.submitJob() query" - OPEN, URGENT
See also the comment from Graeme to the list today below:
Andre,
The client must be able to specify the resource manager to which jobs are submitted, as a service URL or machine name. This should be a argument for either the JobService constructor, or the JobService.createJob() & JobService.runJob() methods.
I guess that conceptually I prefer specifying the resource manager during the construction of the JobService object. However in an earlier mail Chris Smith indicated that the 'host' argument of the runJob() method was originally intended to indicate the machine upon which the job should be run (mapping to an element of the SAGA_HostList attribute). This is confusing and the 'host' argument should be removed, or redefined to indicate the resource manager.
Graeme
I propose to go with Grames proposal unless there are opinions to do differently. I like the version to redefine the host arg better than to remove it altogether.
Other opinions?
Thanks, Andre.
-- "So much time, so little to do..." -- Garfield
Andre, BTW, is the broken job list problem [arising from the separation of submitJob() into createJob and run()] on the issue list? Thanks, Graeme Quoting G.E.POUND@soton.ac.uk:
Andre,
The document "Open Grid Services Architecture Glossary of Terms" may help resolve some of the semantic difficulties that we have been having with this topic.
http://www.ggf.org/Public_Comment_Docs/Documents/Apr-2006/draft-ggf-ogsa-glo...
The following terms correspond to my understanding of this subject, and are the level at which the SAGA API should operate (concealing the identity of back-end batch systems):
Endpoint - A Web service endpoint to which a client may bind in order to consume a service.
Job manager - In OGSA-EMS, a service that manages a set of one or more job instances, which may be structured (e.g. a workflow or dependence graph) or unstructured (e.g. an array of non-interacting jobs).
Graeme
Quoting Andre Merzky <andre@merzky.net>:
132) when do we refer to target host name, and when to resource manager contact, on job submit/description? Se mail thread with Graeme/Chris "JobService.submitJob() query" - OPEN, URGENT
See also the comment from Graeme to the list today below:
Andre,
The client must be able to specify the resource manager to which jobs are submitted, as a service URL or machine name. This should be a argument for either the JobService constructor, or the JobService.createJob() & JobService.runJob() methods.
I guess that conceptually I prefer specifying the resource manager during the construction of the JobService object. However in an earlier mail Chris Smith indicated that the 'host' argument of the runJob() method was originally intended to indicate the machine upon which the job should be run (mapping to an element of the SAGA_HostList attribute). This is confusing and the 'host' argument should be removed, or redefined to indicate the resource manager.
Graeme
I propose to go with Grames proposal unless there are opinions to do differently. I like the version to redefine the host arg better than to remove it altogether.
Other opinions?
Thanks, Andre.
-- "So much time, so little to do..." -- Garfield
Yes, refering to / using these definitions seems sensible. Good point. From the cited definitions I would assume that a 'Job Manager' has one (or more) 'Endpoints', right? A target host name would then be left out - that might (or might not) be represented by an Job Manager (e.g. gram gatekeeper). Thanks, Andre, Quoting [G.E.POUND@soton.ac.uk] (Apr 24 2006):
Andre,
The document "Open Grid Services Architecture Glossary of Terms" may help resolve some of the semantic difficulties that we have been having with this topic. http://www.ggf.org/Public_Comment_Docs/Documents/Apr-2006/draft-ggf-ogsa-glo...
The following terms correspond to my understanding of this subject, and are the level at which the SAGA API should operate (concealing the identity of back-end batch systems):
Endpoint - A Web service endpoint to which a client may bind in order to consume a service.
Job manager - In OGSA-EMS, a service that manages a set of one or more job instances, which may be structured (e.g. a workflow or dependence graph) or unstructured (e.g. an array of non-interacting jobs).
Graeme
Quoting Andre Merzky <andre@merzky.net>:
132) when do we refer to target host name, and when to resource manager contact, on job submit/description? Se mail thread with Graeme/Chris "JobService.submitJob() query" - OPEN, URGENT
See also the comment from Graeme to the list today below:
Andre,
The client must be able to specify the resource manager to which jobs are submitted, as a service URL or machine name. This should be a argument for either the JobService constructor, or the JobService.createJob() & JobService.runJob() methods.
I guess that conceptually I prefer specifying the resource manager during the construction of the JobService object. However in an earlier mail Chris Smith indicated that the 'host' argument of the runJob() method was originally intended to indicate the machine upon which the job should be run (mapping to an element of the SAGA_HostList attribute). This is confusing and the 'host' argument should be removed, or redefined to indicate the resource manager.
Graeme
I propose to go with Grames proposal unless there are opinions to do differently. I like the version to redefine the host arg better than to remove it altogether.
Other opinions?
Thanks, Andre.
-- "So much time, so little to do..." -- Garfield
-- "So much time, so little to do..." -- Garfield
That issue is closed now. Resolution, as discussed, is to use a RM contact on job_service creation, and the 'ExecutionHosts' as attrib on the job description. That also solves the list_jobs problem Graeme mentioned. Cheers, Andre. Quoting [Andre Merzky] (Apr 27 2006):
Date: Thu, 27 Apr 2006 15:14:11 +0200 From: Andre Merzky <andre@merzky.net> To: G.E.POUND@soton.ac.uk Cc: Andre Merzky <andre@merzky.net>, SAGA RG <saga-rg@ggf.org> Subject: Re: [saga-rg] ISSUE 132
Yes, refering to / using these definitions seems sensible. Good point.
From the cited definitions I would assume that a 'Job Manager' has one (or more) 'Endpoints', right?
A target host name would then be left out - that might (or might not) be represented by an Job Manager (e.g. gram gatekeeper).
Thanks, Andre,
Quoting [G.E.POUND@soton.ac.uk] (Apr 24 2006):
Andre,
The document "Open Grid Services Architecture Glossary of Terms" may help resolve some of the semantic difficulties that we have been having with this topic. http://www.ggf.org/Public_Comment_Docs/Documents/Apr-2006/draft-ggf-ogsa-glo...
The following terms correspond to my understanding of this subject, and are the level at which the SAGA API should operate (concealing the identity of back-end batch systems):
Endpoint - A Web service endpoint to which a client may bind in order to consume a service.
Job manager - In OGSA-EMS, a service that manages a set of one or more job instances, which may be structured (e.g. a workflow or dependence graph) or unstructured (e.g. an array of non-interacting jobs).
Graeme
Quoting Andre Merzky <andre@merzky.net>:
132) when do we refer to target host name, and when to resource manager contact, on job submit/description? Se mail thread with Graeme/Chris "JobService.submitJob() query" - OPEN, URGENT
See also the comment from Graeme to the list today below:
Andre,
The client must be able to specify the resource manager to which jobs are submitted, as a service URL or machine name. This should be a argument for either the JobService constructor, or the JobService.createJob() & JobService.runJob() methods.
I guess that conceptually I prefer specifying the resource manager during the construction of the JobService object. However in an earlier mail Chris Smith indicated that the 'host' argument of the runJob() method was originally intended to indicate the machine upon which the job should be run (mapping to an element of the SAGA_HostList attribute). This is confusing and the 'host' argument should be removed, or redefined to indicate the resource manager.
Graeme
I propose to go with Grames proposal unless there are opinions to do differently. I like the version to redefine the host arg better than to remove it altogether.
Other opinions?
Thanks, Andre.
-- "So much time, so little to do..." -- Garfield
-- "So much time, so little to do..." -- Garfield
participants (2)
-
Andre Merzky -
G.E.POUND＠soton.ac.uk