Hi All, After a brief hiatus, we're ready to resume our regular conference calls. Suggested time for the next call is 2PM BST on Thursday 20th April, which translates to 8AM CST and 3PM in Amsterdam (and probably close to midnight in Tokyo. Sorry Pascal.) The agenda for the next call is: - Issue List - SAGA and GridRPC How to coordinate activities of GridRPC into SAGA. - SAGA and GridCPR - AOB ? Conference call details to come soon. If you'd like to join, but suggested time doesn't work for you, please let us know. Thanks.
Hi all, Good to see a new CC on the schedule. With the summer time in the EU it is only 7 hours difference with the mainland Europe, not to bad for me. Unfortunately tomorrow I'll be out so I'm not sure I can make it in time (10 pm for me). If I step in, you all know I'll did it :) Shantenu Jha wrote:
Hi All,
After a brief hiatus, we're ready to resume our regular conference calls.
Suggested time for the next call is 2PM BST on Thursday 20th April, which translates to 8AM CST and 3PM in Amsterdam (and probably close to midnight in Tokyo. Sorry Pascal.)
The agenda for the next call is: - Issue List - SAGA and GridRPC How to coordinate activities of GridRPC into SAGA. - SAGA and GridCPR - AOB ?
Conference call details to come soon.
If you'd like to join, but suggested time doesn't work for you, please let us know.
Thanks.
-- Best regards, Pascal Kleijer ---------------------------------------------------------------- HPC Marketing Promotion Division, NEC Corporation 1-10, Nisshin-cho, Fuchu, Tokyo, 183-8501, Japan. Tel: +81-(0)42/333.6389 Fax: +81-(0)42/333.6382
Hi folx, here are the call details: Date: 20 April 2006 2:00 pm London Time: 3:00 pm Amsterdam 8:00 am Baton Rouge 10:00 pm Tokyo Number: 0844.888.8888 (UK) 01805.004.102 (Germany) +44.870.088.5706 (Others) Code: 808044 Cheers, Andre. Quoting [Shantenu Jha] (Apr 18 2006):
Date: Tue, 18 Apr 2006 14:14:58 +0100 (BST) From: Shantenu Jha <s.jha@ucl.ac.uk> To: saga-rg@ggf.org Subject: [saga-rg] SAGA conference call
Hi All,
After a brief hiatus, we're ready to resume our regular conference calls.
Suggested time for the next call is 2PM BST on Thursday 20th April, which translates to 8AM CST and 3PM in Amsterdam (and probably close to midnight in Tokyo. Sorry Pascal.)
The agenda for the next call is: - Issue List - SAGA and GridRPC How to coordinate activities of GridRPC into SAGA. - SAGA and GridCPR - AOB ?
Conference call details to come soon.
If you'd like to join, but suggested time doesn't work for you, please let us know.
Thanks.
-- "So much time, so little to do..." -- Garfield
Hi folx, attached is the current version of the issue list. Cheers, Andre. Quoting [Andre Merzky] (Apr 19 2006):
Date: Wed, 19 Apr 2006 21:24:19 +0200 From: Andre Merzky <andre@merzky.net> To: Shantenu Jha <s.jha@ucl.ac.uk> Cc: saga-rg@ggf.org Subject: Re: [saga-rg] SAGA conference call
Hi folx,
here are the call details:
Date: 20 April 2006 2:00 pm London Time: 3:00 pm Amsterdam 8:00 am Baton Rouge 10:00 pm Tokyo Number: 0844.888.8888 (UK) 01805.004.102 (Germany) +44.870.088.5706 (Others)
Code: 808044
Cheers, Andre.
Quoting [Shantenu Jha] (Apr 18 2006):
Date: Tue, 18 Apr 2006 14:14:58 +0100 (BST) From: Shantenu Jha <s.jha@ucl.ac.uk> To: saga-rg@ggf.org Subject: [saga-rg] SAGA conference call
Hi All,
After a brief hiatus, we're ready to resume our regular conference calls.
Suggested time for the next call is 2PM BST on Thursday 20th April, which translates to 8AM CST and 3PM in Amsterdam (and probably close to midnight in Tokyo. Sorry Pascal.)
The agenda for the next call is: - Issue List - SAGA and GridRPC How to coordinate activities of GridRPC into SAGA. - SAGA and GridCPR - AOB ?
Conference call details to come soon.
If you'd like to join, but suggested time doesn't work for you, please let us know.
Thanks. -- "So much time, so little to do..." -- Garfield
Andre, Has there been any resolution about the issues raised in the thread "JobService.submitJob() query" (http://www-unix.gridforum.org/mail_archive/saga-rg/2006/03/maillist.html). I am a little out of the loop on this. Thanks, Graeme Andre Merzky wrote:
Hi folx,
attached is the current version of the issue list.
Cheers, Andre.
Quoting [Andre Merzky] (Apr 19 2006):
Date: Wed, 19 Apr 2006 21:24:19 +0200 From: Andre Merzky <andre@merzky.net> To: Shantenu Jha <s.jha@ucl.ac.uk> Cc: saga-rg@ggf.org Subject: Re: [saga-rg] SAGA conference call
Hi folx,
here are the call details:
Date: 20 April 2006 2:00 pm London Time: 3:00 pm Amsterdam 8:00 am Baton Rouge 10:00 pm Tokyo Number: 0844.888.8888 (UK) 01805.004.102 (Germany) +44.870.088.5706 (Others)
Code: 808044
Cheers, Andre.
Quoting [Shantenu Jha] (Apr 18 2006):
Date: Tue, 18 Apr 2006 14:14:58 +0100 (BST) From: Shantenu Jha <s.jha@ucl.ac.uk> To: saga-rg@ggf.org Subject: [saga-rg] SAGA conference call
Hi All,
After a brief hiatus, we're ready to resume our regular conference calls.
Suggested time for the next call is 2PM BST on Thursday 20th April, which translates to 8AM CST and 3PM in Amsterdam (and probably close to midnight in Tokyo. Sorry Pascal.)
The agenda for the next call is: - Issue List - SAGA and GridRPC How to coordinate activities of GridRPC into SAGA. - SAGA and GridCPR - AOB ?
Conference call details to come soon.
If you'd like to join, but suggested time doesn't work for you, please let us know.
Thanks.
------------------------------------------------------------------------
+-------------------------------------------------------------+
##### # # ##### ###### # # # # # # # ## # # # # # ##### # # # # # ##### # # # # # # # # # ## ##### # ###### # # ### # #### #### # # ###### #### # # # # # # # # #### #### # # ##### #### # # # # # # # # # # # # # # # # # ### #### #### #### ###### ####
+-------------------------------------------------------------+
12) change signature of read/write to have len_out as out param, and to return error code (== EAGAIN on unsucessful read) - DECIDED at GGF16 - is that _really_ the right way? - OPEN, URGENT
29) check if bulk operations can be done with task containers - explicit support needed/wanted for argument list generation? - consider parametrisable job descriptions for bulk jobs? - TODO STEPHAN
30) ACLs! - Later, after we get input from the security area and GFS - we actually got that input for files/name spaces, so that should be done! - OPEN, URGENT, MAJOR
36) - examples are not normative for language binding - provide one examples in various languages - TODO TOM: Fortran - TODO HARTMUT: Python
47) check JSDL compliance - TODO CHRIS/ANDRE, URGENT
55) check strawman for references - OPEN
60) add attributes to other objects? consistency model might be an option for replication, blocking/nonblocking for file I/O etc. - OPEN
70) describe task model verbosely in the spec, leave details to language bindings. As we have now job implementing the task interface, that should be reconsidered! - OPEN
76) add specs for literals (attribute and metric names), and add them like enums - OPEN, URGENT
77) add details for getURL and getName - TODO ANDRE, URGENT
81) document pattern and extended read/write - TODO ANDRE, URGENT
82) Explain sidl.SIDLException ! - OPEN, URGENT
83) Exceptions should go into the SIDL part! - would clutter the SIDL? - OPEN
88) for job: add clean_up (can also be called after termination) - OPEN, URGENT
90) exceptions missing in job! - OPEN, URGENT
93) introduction needs sanity checks in respect to the groups development (WG/RG split) - OPEN
95) Security on observables missing: need callout on metric read/write - sync with stream auth example - OPEN, URGENT
97) flags (and their inheritance) seems somewhat confusing - see name space, reuse values in file etc - TODO ANDRE
98) LogicalFiles/Directories: define attributes - TODO ANDRE
102) document what classes need to implement ErrorHandler (shouldn't that be all?) - OPEN
108) explain why we don't specify constness. Or should we? - OPEN, URGENT
109) Formatting should be more TeX like - TODO ANDRE
111) describe that file constructors etc. perform open - TODO ANDRE
112) monitoring needs detailed descriptions. - TODO ANDRE, URGENT
115) detailed description for name_space methods out of sync ns_entry methods are missing. - TODO ANDRE, URGENT
118) stream: detailed description out of sync - TODO ANDRE, URGENT
119) task: detailed description out of sync - TODO ANDRE, URGENT
125) monitoring as in streams ok, use in all objects, define available metrics - TODO ANDRE, URGENT
126) complete descriptions of available metrics - see 125 - TODO ANDRE, URGENT
130) clearify the error handler interface for async calls - OPEN, URGENT
131) clearify what a NULL string/object is we sometimes return - OPEN, URGENT
No, unfortunetly not. I added an issue in the issue list (forgot to do that before). I think that, if we don't find an agreement by GGF17 (in two weeks), we just decide on some approach, e.g. always refereing to the resource manager, until we know where that breaks. What would you preferred solution be? Sorry if I should know that from earlier mails, I left that issue resting as well *sigh* Cheers, Andre. Quoting [Graeme Pound] (Apr 20 2006):
Date: Thu, 20 Apr 2006 13:41:35 +0100 From: Graeme Pound <G.E.POUND@soton.ac.uk> To: Andre Merzky <andre@merzky.net> CC: Shantenu Jha <s.jha@ucl.ac.uk>, saga-rg@ggf.org Subject: Re: [saga-rg] SAGA conference call
Andre,
Has there been any resolution about the issues raised in the thread "JobService.submitJob() query" (http://www-unix.gridforum.org/mail_archive/saga-rg/2006/03/maillist.html).
I am a little out of the loop on this.
Thanks,
Graeme
Andre Merzky wrote:
Hi folx,
attached is the current version of the issue list.
Cheers, Andre.
Quoting [Andre Merzky] (Apr 19 2006):
Date: Wed, 19 Apr 2006 21:24:19 +0200 From: Andre Merzky <andre@merzky.net> To: Shantenu Jha <s.jha@ucl.ac.uk> Cc: saga-rg@ggf.org Subject: Re: [saga-rg] SAGA conference call
Hi folx,
here are the call details:
Date: 20 April 2006 2:00 pm London Time: 3:00 pm Amsterdam 8:00 am Baton Rouge 10:00 pm Tokyo Number: 0844.888.8888 (UK) 01805.004.102 (Germany) +44.870.088.5706 (Others)
Code: 808044
Cheers, Andre.
Quoting [Shantenu Jha] (Apr 18 2006):
Date: Tue, 18 Apr 2006 14:14:58 +0100 (BST) From: Shantenu Jha <s.jha@ucl.ac.uk> To: saga-rg@ggf.org Subject: [saga-rg] SAGA conference call
Hi All,
After a brief hiatus, we're ready to resume our regular conference calls.
Suggested time for the next call is 2PM BST on Thursday 20th April, which translates to 8AM CST and 3PM in Amsterdam (and probably close to midnight in Tokyo. Sorry Pascal.)
The agenda for the next call is: - Issue List - SAGA and GridRPC How to coordinate activities of GridRPC into SAGA. - SAGA and GridCPR - AOB ?
Conference call details to come soon.
If you'd like to join, but suggested time doesn't work for you, please let us know.
Thanks.
------------------------------------------------------------------------
+-------------------------------------------------------------+
##### # # ##### ###### # # # # # # # ## # # # # # ##### # # # # # ##### # # # # # # # # # ## ##### # ###### # # ### # #### #### # # ###### #### # # # # # # # # #### #### # # ##### #### # # # # # # # # # # # # # # # # # ### #### #### #### ###### ####
+-------------------------------------------------------------+
12) change signature of read/write to have len_out as out param, and to return error code (== EAGAIN on unsucessful read) - DECIDED at GGF16 - is that _really_ the right way? - OPEN, URGENT
29) check if bulk operations can be done with task containers - explicit support needed/wanted for argument list generation? - consider parametrisable job descriptions for bulk jobs? - TODO STEPHAN
30) ACLs! - Later, after we get input from the security area and GFS - we actually got that input for files/name spaces, so that should be done! - OPEN, URGENT, MAJOR
36) - examples are not normative for language binding - provide one examples in various languages - TODO TOM: Fortran - TODO HARTMUT: Python
47) check JSDL compliance - TODO CHRIS/ANDRE, URGENT
55) check strawman for references - OPEN
60) add attributes to other objects? consistency model might be an option for replication, blocking/nonblocking for file I/O etc. - OPEN
70) describe task model verbosely in the spec, leave details to language bindings. As we have now job implementing the task interface, that should be reconsidered! - OPEN
76) add specs for literals (attribute and metric names), and add them like enums - OPEN, URGENT
77) add details for getURL and getName - TODO ANDRE, URGENT
81) document pattern and extended read/write - TODO ANDRE, URGENT
82) Explain sidl.SIDLException ! - OPEN, URGENT
83) Exceptions should go into the SIDL part! - would clutter the SIDL? - OPEN
88) for job: add clean_up (can also be called after termination) - OPEN, URGENT
90) exceptions missing in job! - OPEN, URGENT
93) introduction needs sanity checks in respect to the groups development (WG/RG split) - OPEN
95) Security on observables missing: need callout on metric read/write - sync with stream auth example - OPEN, URGENT
97) flags (and their inheritance) seems somewhat confusing - see name space, reuse values in file etc - TODO ANDRE
98) LogicalFiles/Directories: define attributes - TODO ANDRE
102) document what classes need to implement ErrorHandler (shouldn't that be all?) - OPEN
108) explain why we don't specify constness. Or should we? - OPEN, URGENT
109) Formatting should be more TeX like - TODO ANDRE
111) describe that file constructors etc. perform open - TODO ANDRE
112) monitoring needs detailed descriptions. - TODO ANDRE, URGENT
115) detailed description for name_space methods out of sync ns_entry methods are missing. - TODO ANDRE, URGENT
118) stream: detailed description out of sync - TODO ANDRE, URGENT
119) task: detailed description out of sync - TODO ANDRE, URGENT
125) monitoring as in streams ok, use in all objects, define available metrics - TODO ANDRE, URGENT
126) complete descriptions of available metrics - see 125 - TODO ANDRE, URGENT
130) clearify the error handler interface for async calls - OPEN, URGENT
131) clearify what a NULL string/object is we sometimes return - OPEN, URGENT
-- "So much time, so little to do..." -- Garfield
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 Andre Merzky wrote:
No, unfortunetly not. I added an issue in the issue list (forgot to do that before). I think that, if we don't find an agreement by GGF17 (in two weeks), we just decide on some approach, e.g. always refereing to the resource manager, until we know where that breaks.
What would you preferred solution be? Sorry if I should know that from earlier mails, I left that issue resting as well *sigh*
Cheers, Andre.
Quoting [Graeme Pound] (Apr 20 2006):
Date: Thu, 20 Apr 2006 13:41:35 +0100 From: Graeme Pound <G.E.POUND@soton.ac.uk> To: Andre Merzky <andre@merzky.net> CC: Shantenu Jha <s.jha@ucl.ac.uk>, saga-rg@ggf.org Subject: Re: [saga-rg] SAGA conference call
Andre,
Has there been any resolution about the issues raised in the thread "JobService.submitJob() query" (http://www-unix.gridforum.org/mail_archive/saga-rg/2006/03/maillist.html).
I am a little out of the loop on this.
Thanks,
Graeme
Andre Merzky wrote:
Hi folx,
attached is the current version of the issue list.
Cheers, Andre.
Quoting [Andre Merzky] (Apr 19 2006):
Date: Wed, 19 Apr 2006 21:24:19 +0200 From: Andre Merzky <andre@merzky.net> To: Shantenu Jha <s.jha@ucl.ac.uk> Cc: saga-rg@ggf.org Subject: Re: [saga-rg] SAGA conference call
Hi folx,
here are the call details:
Date: 20 April 2006 2:00 pm London Time: 3:00 pm Amsterdam 8:00 am Baton Rouge 10:00 pm Tokyo Number: 0844.888.8888 (UK) 01805.004.102 (Germany) +44.870.088.5706 (Others)
Code: 808044
Cheers, Andre.
Quoting [Shantenu Jha] (Apr 18 2006):
Date: Tue, 18 Apr 2006 14:14:58 +0100 (BST) From: Shantenu Jha <s.jha@ucl.ac.uk> To: saga-rg@ggf.org Subject: [saga-rg] SAGA conference call
Hi All,
After a brief hiatus, we're ready to resume our regular conference calls.
Suggested time for the next call is 2PM BST on Thursday 20th April, which translates to 8AM CST and 3PM in Amsterdam (and probably close to midnight in Tokyo. Sorry Pascal.)
The agenda for the next call is: - Issue List - SAGA and GridRPC How to coordinate activities of GridRPC into SAGA. - SAGA and GridCPR - AOB ?
Conference call details to come soon.
If you'd like to join, but suggested time doesn't work for you, please let us know.
Thanks.
------------------------------------------------------------------------
+-------------------------------------------------------------+
##### # # ##### ###### # # # # # # # ## # # # # # ##### # # # # # ##### # # # # # # # # # ## ##### # ###### # # ### # #### #### # # ###### #### # # # # # # # # #### #### # # ##### #### # # # # # # # # # # # # # # # # # ### #### #### #### ###### ####
+-------------------------------------------------------------+
12) change signature of read/write to have len_out as out param, and to return error code (== EAGAIN on unsucessful read) - DECIDED at GGF16 - is that _really_ the right way? - OPEN, URGENT
29) check if bulk operations can be done with task containers - explicit support needed/wanted for argument list generation? - consider parametrisable job descriptions for bulk jobs? - TODO STEPHAN
30) ACLs! - Later, after we get input from the security area and GFS - we actually got that input for files/name spaces, so that should be done! - OPEN, URGENT, MAJOR
36) - examples are not normative for language binding - provide one examples in various languages - TODO TOM: Fortran - TODO HARTMUT: Python
47) check JSDL compliance - TODO CHRIS/ANDRE, URGENT
55) check strawman for references - OPEN
60) add attributes to other objects? consistency model might be an option for replication, blocking/nonblocking for file I/O etc. - OPEN
70) describe task model verbosely in the spec, leave details to language bindings. As we have now job implementing the task interface, that should be reconsidered! - OPEN
76) add specs for literals (attribute and metric names), and add them like enums - OPEN, URGENT
77) add details for getURL and getName - TODO ANDRE, URGENT
81) document pattern and extended read/write - TODO ANDRE, URGENT
82) Explain sidl.SIDLException ! - OPEN, URGENT
83) Exceptions should go into the SIDL part! - would clutter the SIDL? - OPEN
88) for job: add clean_up (can also be called after termination) - OPEN, URGENT
90) exceptions missing in job! - OPEN, URGENT
93) introduction needs sanity checks in respect to the groups development (WG/RG split) - OPEN
95) Security on observables missing: need callout on metric read/write - sync with stream auth example - OPEN, URGENT
97) flags (and their inheritance) seems somewhat confusing - see name space, reuse values in file etc - TODO ANDRE
98) LogicalFiles/Directories: define attributes - TODO ANDRE
102) document what classes need to implement ErrorHandler (shouldn't that be all?) - OPEN
108) explain why we don't specify constness. Or should we? - OPEN, URGENT
109) Formatting should be more TeX like - TODO ANDRE
111) describe that file constructors etc. perform open - TODO ANDRE
112) monitoring needs detailed descriptions. - TODO ANDRE, URGENT
115) detailed description for name_space methods out of sync ns_entry methods are missing. - TODO ANDRE, URGENT
118) stream: detailed description out of sync - TODO ANDRE, URGENT
119) task: detailed description out of sync - TODO ANDRE, URGENT
125) monitoring as in streams ok, use in all objects, define available metrics - TODO ANDRE, URGENT
126) complete descriptions of available metrics - see 125 - TODO ANDRE, URGENT
130) clearify the error handler interface for async calls - OPEN, URGENT
131) clearify what a NULL string/object is we sometimes return - OPEN, URGENT
Andre, I saw that SAGA JSDL compliance was an issue on your issue list. Here are the mappings that I am using between JobDefinition attributes and JSDL elements. I am using these mappings to provide a SAGA compliant interface to the GridSAM service for the OMII. This doc is a little old. The 'SAGA_*' attributes have now lost this prefix. The 'JSDL_' prefix indicates that an attribute is specific to the implementation and is not part of the SAGA spec. Graeme /** * A simple builder for a JSDL document. * * This utility produces JSDL documents based upon JSDL Specification (version 1.0, draft 28). * <pre> * ##jsdl:Application -> jsdl-posix:POSIXApplication * SAGA_JobCmd -> jsdl-posix:Executable * SAGA_JobArgs[] -> jsdl-posix:Argument * SAGA_JobEnv[] -> jsdl-posix:Environment * SAGA_JobCwd -> jsdl-posix:WorkingDirectory * SAGA_JobStdin -> jsdl-posix:Input * SAGA_JobStdout -> jsdl-posix:Output * SAGA_JobStderr -> jsdl-posix:Error * SAGA_WallclockHardLimit -> jsdl-posix:WallTimeLimit * SAGA_Cputime -> jsdl-posix:CPUTimeLimit * * ##jsdl:DataStaging * SAGA_FileTransfer[] -> Maps to operations in jsdl:DataStaging * JSDL_DeleteOnTermination -> jsdl:DeleteOnTermination * * ##jsdl:Resources * SAGA_NumCpus -> jsdl:TotalCPUCount * SAGA_Memory -> jsdl:TotalPhysicalMemory * SAGA_ProcessorType -> jsdl:CPUArchitecture * [of enumeration jsdl:ProcessorArchitectureEnumeration or other] sparc A SPARC architecture processor powerpc A PowerPC architecture processor x86 An Intel Architecture processor derived from the 8086 chip set x86_32 An x86 processor capable of 32-bit processing mode x86_64 An x86 processor capable of 64-bit processing mode parisc A PARISC architecture processor mips A MIPS architecture processor ia64 An Intel Architecture 64-bit processor arm An ARM processor other A value not defined by this enumeration * SAGA_OperatingSystem -> jsdl:OperatingSystemType * [of enumeration jsdl:OperatingSystemTypeEnumeration or other] Unknown other Not_Applicable AIX ASERIES ATTUNIX BeOS BS2000 BSDUNIX Caldera_Open_UNIX DC_OS DECNT Dedicated DGUX EPOC FreeBSD GNU_Hurd HP_MPE HPUX Inferno Interactive_UNIX IxWorks JavaVM LINUX Lynx MACH_Kernel MACOS MiNT MSDOS MVS NCR3000 NetBSD NetWare NextStep OpenBSD OpenVMS OS_2 OS_390 OS400 OS9 OSF PalmPilot QNX Reliant_UNIX Rhapsody SCO_OpenServer SCO_UnixWare Sequent Solaris SunOS TandemNSK TandemNT TPF Tru64_UNIX U6000 VM VSE VxWorks WIN3x WIN95 WIN98 WINCE Windows_2000 Windows_R_Me Windows_XP WINNT XENIX z_OS * SAGA_HostList[] -> jsdl:CandidateHosts * * ##jsdl:JobIdentification * SAGA_JobName -> jsdl:JobName * JSDL_Description -> jsdl:Description * JSDL_JobAnnotation -> jsdl:JobAnnotation * JSDL_JobProject -> jsdl:JobProject * * SAGA_JobState -> NOT SUPPORTED * SAGA_JobInteractive -> NOT SUPPORTED * SAGA_JobContact[] -> NOT SUPPORTED * SAGA_JobNotification -> NOT SUPPORTED * SAGA_JobNative -> NOT SUPPORTED * SAGA_WallclockSoftLimit -> NOT SUPPORTED * SAGA_JobStartTime -> NOT SUPPORTED * SAGA_Deadline -> NOT SUPPORTED * SAGA_Queue -> NOT SUPPORTED * </pre> */
Great! That list is definitely helpful :-) Thanks, Andre. Quoting [Graeme Pound] (Apr 20 2006):
Date: Thu, 20 Apr 2006 14:29:34 +0100 From: Graeme Pound <G.E.POUND@soton.ac.uk> To: Andre Merzky <andre@merzky.net> CC: Shantenu Jha <s.jha@ucl.ac.uk>, saga-rg@ggf.org Subject: SAGA to JSDL mappings
Andre,
I saw that SAGA JSDL compliance was an issue on your issue list.
Here are the mappings that I am using between JobDefinition attributes and JSDL elements. I am using these mappings to provide a SAGA compliant interface to the GridSAM service for the OMII.
This doc is a little old. The 'SAGA_*' attributes have now lost this prefix. The 'JSDL_' prefix indicates that an attribute is specific to the implementation and is not part of the SAGA spec.
Graeme
/** * A simple builder for a JSDL document. * * This utility produces JSDL documents based upon JSDL Specification (version 1.0, draft 28). * <pre> * ##jsdl:Application -> jsdl-posix:POSIXApplication * SAGA_JobCmd -> jsdl-posix:Executable * SAGA_JobArgs[] -> jsdl-posix:Argument * SAGA_JobEnv[] -> jsdl-posix:Environment * SAGA_JobCwd -> jsdl-posix:WorkingDirectory * SAGA_JobStdin -> jsdl-posix:Input * SAGA_JobStdout -> jsdl-posix:Output * SAGA_JobStderr -> jsdl-posix:Error * SAGA_WallclockHardLimit -> jsdl-posix:WallTimeLimit * SAGA_Cputime -> jsdl-posix:CPUTimeLimit * * ##jsdl:DataStaging * SAGA_FileTransfer[] -> Maps to operations in jsdl:DataStaging * JSDL_DeleteOnTermination -> jsdl:DeleteOnTermination * * ##jsdl:Resources * SAGA_NumCpus -> jsdl:TotalCPUCount * SAGA_Memory -> jsdl:TotalPhysicalMemory * SAGA_ProcessorType -> jsdl:CPUArchitecture * [of enumeration jsdl:ProcessorArchitectureEnumeration or other] sparc A SPARC architecture processor powerpc A PowerPC architecture processor x86 An Intel Architecture processor derived from the 8086 chip set x86_32 An x86 processor capable of 32-bit processing mode x86_64 An x86 processor capable of 64-bit processing mode parisc A PARISC architecture processor mips A MIPS architecture processor ia64 An Intel Architecture 64-bit processor arm An ARM processor other A value not defined by this enumeration * SAGA_OperatingSystem -> jsdl:OperatingSystemType * [of enumeration jsdl:OperatingSystemTypeEnumeration or other] Unknown other Not_Applicable AIX ASERIES ATTUNIX BeOS BS2000 BSDUNIX Caldera_Open_UNIX DC_OS DECNT Dedicated DGUX EPOC FreeBSD GNU_Hurd HP_MPE HPUX Inferno Interactive_UNIX IxWorks JavaVM LINUX Lynx MACH_Kernel MACOS MiNT MSDOS MVS NCR3000 NetBSD NetWare NextStep OpenBSD OpenVMS OS_2 OS_390 OS400 OS9 OSF PalmPilot QNX Reliant_UNIX Rhapsody SCO_OpenServer SCO_UnixWare Sequent Solaris SunOS TandemNSK TandemNT TPF Tru64_UNIX U6000 VM VSE VxWorks WIN3x WIN95 WIN98 WINCE Windows_2000 Windows_R_Me Windows_XP WINNT XENIX z_OS
* SAGA_HostList[] -> jsdl:CandidateHosts * * ##jsdl:JobIdentification * SAGA_JobName -> jsdl:JobName * JSDL_Description -> jsdl:Description * JSDL_JobAnnotation -> jsdl:JobAnnotation * JSDL_JobProject -> jsdl:JobProject * * SAGA_JobState -> NOT SUPPORTED * SAGA_JobInteractive -> NOT SUPPORTED * SAGA_JobContact[] -> NOT SUPPORTED * SAGA_JobNotification -> NOT SUPPORTED * SAGA_JobNative -> NOT SUPPORTED * SAGA_WallclockSoftLimit -> NOT SUPPORTED * SAGA_JobStartTime -> NOT SUPPORTED * SAGA_Deadline -> NOT SUPPORTED * SAGA_Queue -> NOT SUPPORTED * </pre> */
-- "So much time, so little to do..." -- Garfield
47) check JSDL compliance - TODO CHRIS/ANDRE, URGENT Graeme sent today the message included below, which addresses these issues. As the saga attribute names have been coined before JSDL was finalized, it is not surprising that names deviate. I propose to update the names to reflect the JSDL names (they are well chosen I think). Also, SAGA supports a number of attributes, which have no equivalent in JSDL: * SAGA_JobState -> NOT SUPPORTED * SAGA_JobInteractive -> NOT SUPPORTED * SAGA_JobContact[] -> NOT SUPPORTED * SAGA_JobNotification -> NOT SUPPORTED * SAGA_JobNative -> NOT SUPPORTED * SAGA_WallclockSoftLimit -> NOT SUPPORTED * SAGA_JobStartTime -> NOT SUPPORTED * SAGA_Deadline -> NOT SUPPORTED * SAGA_Queue -> NOT SUPPORTED I am positive that we have use cases for specifying queue and contact information. I am not so sure about the others. Unless someone objects, I would propose to remove those attributes which have no JSDL equivalent, and we have no explicit use cases for. OTOH, Graeme points out that some JSDL attributes are unsupported: * JSDL_Description -> jsdl:Description * JSDL_JobAnnotation -> jsdl:JobAnnotation * JSDL_JobProject -> jsdl:JobProject * JSDL_DeleteOnTermination -> jsdl:DeleteOnTermination Again, I think we have no use cases for those, so I think they should be left out. Summary: We have following options: (A) leave stuff as is, and map in the implementation (B) update naming to reflect JSDL, and introduce the respective enums (C) remove attribs w/o JSDL pendant, unless we have an explicit use case I vote vor (B) and (C). Cheers, Andre. Quoting [Graeme Pound] (Apr 20 2006):
Andre,
I saw that SAGA JSDL compliance was an issue on your issue list.
Here are the mappings that I am using between JobDefinition attributes and JSDL elements. I am using these mappings to provide a SAGA compliant interface to the GridSAM service for the OMII.
This doc is a little old. The 'SAGA_*' attributes have now lost this prefix. The 'JSDL_' prefix indicates that an attribute is specific to the implementation and is not part of the SAGA spec.
Graeme
/** * A simple builder for a JSDL document. * * This utility produces JSDL documents based upon JSDL Specification (version 1.0, draft 28). * <pre> * ##jsdl:Application -> jsdl-posix:POSIXApplication * SAGA_JobCmd -> jsdl-posix:Executable * SAGA_JobArgs[] -> jsdl-posix:Argument * SAGA_JobEnv[] -> jsdl-posix:Environment * SAGA_JobCwd -> jsdl-posix:WorkingDirectory * SAGA_JobStdin -> jsdl-posix:Input * SAGA_JobStdout -> jsdl-posix:Output * SAGA_JobStderr -> jsdl-posix:Error * SAGA_WallclockHardLimit -> jsdl-posix:WallTimeLimit * SAGA_Cputime -> jsdl-posix:CPUTimeLimit * * ##jsdl:DataStaging * SAGA_FileTransfer[] -> Maps to operations in jsdl:DataStaging * JSDL_DeleteOnTermination -> jsdl:DeleteOnTermination * * ##jsdl:Resources * SAGA_NumCpus -> jsdl:TotalCPUCount * SAGA_Memory -> jsdl:TotalPhysicalMemory * SAGA_ProcessorType -> jsdl:CPUArchitecture * [of enumeration jsdl:ProcessorArchitectureEnumeration or other] sparc A SPARC architecture processor powerpc A PowerPC architecture processor x86 An Intel Architecture processor derived from the 8086 chip set x86_32 An x86 processor capable of 32-bit processing mode x86_64 An x86 processor capable of 64-bit processing mode parisc A PARISC architecture processor mips A MIPS architecture processor ia64 An Intel Architecture 64-bit processor arm An ARM processor other A value not defined by this enumeration * SAGA_OperatingSystem -> jsdl:OperatingSystemType * [of enumeration jsdl:OperatingSystemTypeEnumeration or other] Unknown other Not_Applicable AIX ASERIES ATTUNIX BeOS BS2000 BSDUNIX Caldera_Open_UNIX DC_OS DECNT Dedicated DGUX EPOC FreeBSD GNU_Hurd HP_MPE HPUX Inferno Interactive_UNIX IxWorks JavaVM LINUX Lynx MACH_Kernel MACOS MiNT MSDOS MVS NCR3000 NetBSD NetWare NextStep OpenBSD OpenVMS OS_2 OS_390 OS400 OS9 OSF PalmPilot QNX Reliant_UNIX Rhapsody SCO_OpenServer SCO_UnixWare Sequent Solaris SunOS TandemNSK TandemNT TPF Tru64_UNIX U6000 VM VSE VxWorks WIN3x WIN95 WIN98 WINCE Windows_2000 Windows_R_Me Windows_XP WINNT XENIX z_OS
* SAGA_HostList[] -> jsdl:CandidateHosts * * ##jsdl:JobIdentification * SAGA_JobName -> jsdl:JobName * JSDL_Description -> jsdl:Description * JSDL_JobAnnotation -> jsdl:JobAnnotation * JSDL_JobProject -> jsdl:JobProject * * SAGA_JobState -> NOT SUPPORTED * SAGA_JobInteractive -> NOT SUPPORTED * SAGA_JobContact[] -> NOT SUPPORTED * SAGA_JobNotification -> NOT SUPPORTED * SAGA_JobNative -> NOT SUPPORTED * SAGA_WallclockSoftLimit -> NOT SUPPORTED * SAGA_JobStartTime -> NOT SUPPORTED * SAGA_Deadline -> NOT SUPPORTED * SAGA_Queue -> NOT SUPPORTED * </pre> */
-- "So much time, so little to do..." -- Garfield
An hi again, below are the (short) meeting notes from todays call. We would like to have the next call in exctly one week and 30 minutes (i.e. next week, same day, 30 minutes later). Cheers, Andre. Meeting Notes ------------- SAGA RG/WG conference call April 20, 2006 Participants: - Stephan Hirmer - Shantenu Jha - Thilo Kielmann - Andre Merzky Topics: - issue list - topics marked as URGENT should be resolved before GGF if possible, at GGF latest - TODO ANDRE: send separate emails for issues to list, with proposals for resolution, or wikth call for such proposal - issues still open next week get discussed at call - stramwan dosucment status - apart from the issues (above), the doc needs editing (consistency, layout, typosetc. We split the doc in three parts: TODO Thilo: intro, object, session, context, error, task TODO Andre: monitoring, attribs, name space, files TODO Shantenu: logical files, jobs, streams More helpers would be VERY welcome (Tom? Hartmut? Pascal? Others?) - synchronization point: Thursday, April 27 (potentiall call on Friday). - SAGA and GridCRP: - got no input from GridCPR - acute concern is potential conflict with SAGA monitoring model - approach: check CPR use cases for monitoring conflicts, but leave CPR semantic (== new calls) for later - TODO Shantenu: ping Tom, otherwise review CPR use cases - TODO ANDRE: add issue for that point - SAGA and GridRPC: - some progress on mailing list - two potential point of conflict with current GridRPC API - config file exposes implementation on API level - varargs are used, which we did not consider yet (SIDL?) - these issues should be addressed at GGF17 - apart from that, a RPC package (outside strawman) should be feasable between GGF17 and GGF18 - TODO ANDRE: create CVS dir, set up package and issue list - note: RPC sata handles not yet considered - note: relation to web services need clarification (there are SAGA use cases for that) - AOB: - TODO ANDRE: check how the GGF17 workshop agenda can be updated online - the 4th GGF session should dedicate some time to planning of tutorial and cookbook material Comments/corrections welcome! Quoting [Andre Merzky] (Apr 20 2006):
Hi folx,
attached is the current version of the issue list.
Cheers, Andre.
Quoting [Andre Merzky] (Apr 19 2006):
Date: Wed, 19 Apr 2006 21:24:19 +0200 From: Andre Merzky <andre@merzky.net> To: Shantenu Jha <s.jha@ucl.ac.uk> Cc: saga-rg@ggf.org Subject: Re: [saga-rg] SAGA conference call
Hi folx,
here are the call details:
Date: 20 April 2006 2:00 pm London Time: 3:00 pm Amsterdam 8:00 am Baton Rouge 10:00 pm Tokyo Number: 0844.888.8888 (UK) 01805.004.102 (Germany) +44.870.088.5706 (Others)
Code: 808044
Cheers, Andre.
Quoting [Shantenu Jha] (Apr 18 2006):
Date: Tue, 18 Apr 2006 14:14:58 +0100 (BST) From: Shantenu Jha <s.jha@ucl.ac.uk> To: saga-rg@ggf.org Subject: [saga-rg] SAGA conference call
Hi All,
After a brief hiatus, we're ready to resume our regular conference calls.
Suggested time for the next call is 2PM BST on Thursday 20th April, which translates to 8AM CST and 3PM in Amsterdam (and probably close to midnight in Tokyo. Sorry Pascal.)
The agenda for the next call is: - Issue List - SAGA and GridRPC How to coordinate activities of GridRPC into SAGA. - SAGA and GridCPR - AOB ?
Conference call details to come soon.
If you'd like to join, but suggested time doesn't work for you, please let us know.
Thanks.
-- "So much time, so little to do..." -- Garfield
All, sorry for not being able to attend the call. here are some comment on GridRPC. Andre Merzky wrote:
- SAGA and GridRPC: - some progress on mailing list - two potential point of conflict with current GridRPC API - config file exposes implementation on API level
what is the canonical way in SAGA to path optional configuration information to a binary? a specific-named file in the current working directory might work as well.
- varargs are used, which we did not consider yet (SIDL?)
To have single argument array might be the easiest solution.
- these issues should be addressed at GGF17 - apart from that, a RPC package (outside strawman) should be feasable between GGF17 and GGF18 - TODO ANDRE: create CVS dir, set up package and issue list - note: RPC sata handles not yet considered
what is 'sata' handle?
- note: relation to web services need clarification (there are SAGA use cases for that)
-hidemoto
Quoting [Hidemoto Nakada] (Apr 21 2006):
All,
sorry for not being able to attend the call. here are some comment on GridRPC.
No problem - we realise it was on short notice.
Andre Merzky wrote:
- SAGA and GridRPC: - some progress on mailing list - two potential point of conflict with current GridRPC API - config file exposes implementation on API level what is the canonical way in SAGA to path optional configuration information to a binary?
The spec is silent about configuration :-(. The SAGA approach however would be to move that responsibility away from end user level, to the administrator level. For example, environment specific configurations should be performed by the administrator who installes SAGA, not by the programmer who uses SAGA.
a specific-named file in the current working directory might work as well.
That is probably convenient and useful - but should, IMHO, the last resort. A search for configuration in some other predefined places, such as $INSTALL_ROOT/share/saga.ini /etc/saga.ini ~/.saga.ini `pwd`/saga.ini (that at last) would, as described above, allow the administrator to configure SAGA We also have to keep in mind that we might need configuration for not only RPC, but for other parts of SAGA as well. Multiple config files are probably not a good option, or at least not in multiple formats. So just including the RPC config handling as is is, unfortunately, not advisable IMHO.
- varargs are used, which we did not consider yet (SIDL?)
To have single argument array might be the easiest solution.
Right, but you loose type conversion that way. I originally thought you use an array of strings - and only realised by looking at the implementations that varargs are used. The good thing about that is that it looks VERY simple from end user side. At least for C programmers, its also very familiar. For Java it might be impossible. So, one approach would be to define a single arg array, as you propose, in the spec, but allow the language bindings to implement that with varargs. Does that make sense?
- these issues should be addressed at GGF17 - apart from that, a RPC package (outside strawman) should be feasable between GGF17 and GGF18 - TODO ANDRE: create CVS dir, set up package and issue list - note: RPC sata handles not yet considered
what is 'sata' handle?
Oops, sorry - 'data handles'. That refers to the remote data handles you folx consider as an extension to the first GridRPC spec.
- note: relation to web services need clarification (there are SAGA use cases for that)
-hidemoto
Thanks for your feedback, Andre. -- "So much time, so little to do..." -- Garfield
Andre, Andre Merzky wrote:
Quoting [Hidemoto Nakada] (Apr 21 2006):
All,
sorry for not being able to attend the call. here are some comment on GridRPC.
No problem - we realise it was on short notice.
Andre Merzky wrote:
- SAGA and GridRPC: - some progress on mailing list - two potential point of conflict with current GridRPC API - config file exposes implementation on API level what is the canonical way in SAGA to path optional configuration information to a binary?
The spec is silent about configuration :-(. The SAGA approach however would be to move that responsibility away from end user level, to the administrator level. For example, environment specific configurations should be performed by the administrator who installes SAGA, not by the programmer who uses SAGA.
a specific-named file in the current working directory might work as well.
That is probably convenient and useful - but should, IMHO, the last resort. A search for configuration in some other predefined places, such as
$INSTALL_ROOT/share/saga.ini /etc/saga.ini ~/.saga.ini `pwd`/saga.ini (that at last)
would, as described above, allow the administrator to configure SAGA
We also have to keep in mind that we might need configuration for not only RPC, but for other parts of SAGA as well. Multiple config files are probably not a good option, or at least not in multiple formats. So just including the RPC config handling as is is, unfortunately, not advisable IMHO.
I agree. Do you think you will specify a specific configuration format for SAGA API, like Java specifies properties file format? In our experience, Java properties syntax is not powerful enough for our config files.
- varargs are used, which we did not consider yet (SIDL?)
To have single argument array might be the easiest solution.
Right, but you loose type conversion that way. I originally thought you use an array of strings - and only realised by looking at the implementations that varargs are used.
The good thing about that is that it looks VERY simple from end user side. At least for C programmers, its also very familiar. For Java it might be impossible.
Note that in C varargs, type check will not happen in anytime. Java, from JDK1.5, provides automatic conversion from vararg type call to Object array and automatic primitive type boxing. with them we can use effectively same notation in Java. in Java, you can type check at execution time.
So, one approach would be to define a single arg array, as you propose, in the spec, but allow the language bindings to implement that with varargs.
-hidemoto
Hi Folx, below are the details for tomorrows call. Cheers, Andre date: 27 April 2006 time: 8:30 AM Baton Rouge time: 3:30 PM Amsterdam 2:30 PM London 10:30 PM Tokyo time: 3:30 PM CEST number: 0844.888.8888 (UK) 01805.004.102 (Germany) +44.870.088.5706 (Others) code: 808044 agenda: - responses to posted issues - progress on doc editing? - AOB Quoting [Andre Merzky] (Apr 20 2006):
Date: Thu, 20 Apr 2006 16:12:04 +0200 From: Andre Merzky <andre@merzky.net> To: Shantenu Jha <s.jha@ucl.ac.uk> Cc: saga-rg@ggf.org Subject: Re: [saga-rg] SAGA conference call
An hi again,
below are the (short) meeting notes from todays call. We would like to have the next call in exctly one week and 30 minutes (i.e. next week, same day, 30 minutes later).
Cheers, Andre.
Meeting Notes -------------
SAGA RG/WG conference call April 20, 2006
Participants: - Stephan Hirmer - Shantenu Jha - Thilo Kielmann - Andre Merzky
Topics: - issue list - topics marked as URGENT should be resolved before GGF if possible, at GGF latest - TODO ANDRE: send separate emails for issues to list, with proposals for resolution, or wikth call for such proposal - issues still open next week get discussed at call
- stramwan dosucment status - apart from the issues (above), the doc needs editing (consistency, layout, typosetc. We split the doc in three parts:
TODO Thilo: intro, object, session, context, error, task TODO Andre: monitoring, attribs, name space, files TODO Shantenu: logical files, jobs, streams
More helpers would be VERY welcome (Tom? Hartmut? Pascal? Others?) - synchronization point: Thursday, April 27 (potentiall call on Friday).
- SAGA and GridCRP: - got no input from GridCPR - acute concern is potential conflict with SAGA monitoring model - approach: check CPR use cases for monitoring conflicts, but leave CPR semantic (== new calls) for later - TODO Shantenu: ping Tom, otherwise review CPR use cases - TODO ANDRE: add issue for that point
- SAGA and GridRPC: - some progress on mailing list - two potential point of conflict with current GridRPC API - config file exposes implementation on API level - varargs are used, which we did not consider yet (SIDL?) - these issues should be addressed at GGF17 - apart from that, a RPC package (outside strawman) should be feasable between GGF17 and GGF18 - TODO ANDRE: create CVS dir, set up package and issue list - note: RPC sata handles not yet considered - note: relation to web services need clarification (there are SAGA use cases for that)
- AOB: - TODO ANDRE: check how the GGF17 workshop agenda can be updated online - the 4th GGF session should dedicate some time to planning of tutorial and cookbook material
Comments/corrections welcome!
Quoting [Andre Merzky] (Apr 20 2006):
Hi folx,
attached is the current version of the issue list.
Cheers, Andre.
Quoting [Andre Merzky] (Apr 19 2006):
Date: Wed, 19 Apr 2006 21:24:19 +0200 From: Andre Merzky <andre@merzky.net> To: Shantenu Jha <s.jha@ucl.ac.uk> Cc: saga-rg@ggf.org Subject: Re: [saga-rg] SAGA conference call
Hi folx,
here are the call details:
Date: 20 April 2006 2:00 pm London Time: 3:00 pm Amsterdam 8:00 am Baton Rouge 10:00 pm Tokyo Number: 0844.888.8888 (UK) 01805.004.102 (Germany) +44.870.088.5706 (Others)
Code: 808044
Cheers, Andre.
Quoting [Shantenu Jha] (Apr 18 2006):
Date: Tue, 18 Apr 2006 14:14:58 +0100 (BST) From: Shantenu Jha <s.jha@ucl.ac.uk> To: saga-rg@ggf.org Subject: [saga-rg] SAGA conference call
Hi All,
After a brief hiatus, we're ready to resume our regular conference calls.
Suggested time for the next call is 2PM BST on Thursday 20th April, which translates to 8AM CST and 3PM in Amsterdam (and probably close to midnight in Tokyo. Sorry Pascal.)
The agenda for the next call is: - Issue List - SAGA and GridRPC How to coordinate activities of GridRPC into SAGA. - SAGA and GridCPR - AOB ?
Conference call details to come soon.
If you'd like to join, but suggested time doesn't work for you, please let us know.
Thanks.
-- "So much time, so little to do..." -- Garfield
Hi, these are short meeting notes from todays call. Next call will be scheduled next Thursday, 3pm CEST. Most important point: posted issues will be discussed/finalized on next weeks call. Cheers, Andre. - Participants: - Shantenu Jha - Andre Merzky - Pascal Kleijer - Thilo Kielmann - SAGA and Naregi: - since Pascal joined, we chatted about NAREGI and the MW stack - SAGA uptake in NAREGI seems unlikely unless the NAREGI stack is supported. Otherwise, only for parts not conflicting with the stack, e.g. streaming - the current SAGA implementations (OMII and VU/LSU) should make it simple to support the NAREGI stack - TODO: SHANTENU,ANDRE: approach Satoshis about commitment for NAREGI bindings for the SAGA implemenations, at GGF - Document Business - Andre: did not follow up yet with the latest response from Greg about the UC doc - TODO - no response yet from Greg about the REQ doc - need to be followed up - editing the API doc slowly progressing, discuss at next weeks call - open issues - apart from Graeme no responses - TODO ANDRE: follow up with the issues Graeme answered - discuss/finalize posted issues during next call - AOB - we discussed the workshop organization for GGF17 - some TODOs distributed for following up with speakers etc - see separate mail - next call will be scheduled for next Thursday, 3:00 PM CEST Cheers, Andre. Quoting [Andre Merzky] (Apr 26 2006):
Date: Wed, 26 Apr 2006 14:36:48 +0200 From: Andre Merzky <andre@merzky.net> To: saga-rg@ggf.org Subject: Re: [saga-rg] SAGA conference call
Hi Folx,
below are the details for tomorrows call.
Cheers, Andre
date: 27 April 2006 time: 8:30 AM Baton Rouge time: 3:30 PM Amsterdam 2:30 PM London 10:30 PM Tokyo time: 3:30 PM CEST number: 0844.888.8888 (UK) 01805.004.102 (Germany) +44.870.088.5706 (Others) code: 808044
agenda: - responses to posted issues - progress on doc editing? - AOB
Quoting [Andre Merzky] (Apr 20 2006):
Date: Thu, 20 Apr 2006 16:12:04 +0200 From: Andre Merzky <andre@merzky.net> To: Shantenu Jha <s.jha@ucl.ac.uk> Cc: saga-rg@ggf.org Subject: Re: [saga-rg] SAGA conference call
An hi again,
below are the (short) meeting notes from todays call. We would like to have the next call in exctly one week and 30 minutes (i.e. next week, same day, 30 minutes later).
Cheers, Andre.
Meeting Notes -------------
SAGA RG/WG conference call April 20, 2006
Participants: - Stephan Hirmer - Shantenu Jha - Thilo Kielmann - Andre Merzky
Topics: - issue list - topics marked as URGENT should be resolved before GGF if possible, at GGF latest - TODO ANDRE: send separate emails for issues to list, with proposals for resolution, or wikth call for such proposal - issues still open next week get discussed at call
- stramwan dosucment status - apart from the issues (above), the doc needs editing (consistency, layout, typosetc. We split the doc in three parts:
TODO Thilo: intro, object, session, context, error, task TODO Andre: monitoring, attribs, name space, files TODO Shantenu: logical files, jobs, streams
More helpers would be VERY welcome (Tom? Hartmut? Pascal? Others?) - synchronization point: Thursday, April 27 (potentiall call on Friday).
- SAGA and GridCRP: - got no input from GridCPR - acute concern is potential conflict with SAGA monitoring model - approach: check CPR use cases for monitoring conflicts, but leave CPR semantic (== new calls) for later - TODO Shantenu: ping Tom, otherwise review CPR use cases - TODO ANDRE: add issue for that point
- SAGA and GridRPC: - some progress on mailing list - two potential point of conflict with current GridRPC API - config file exposes implementation on API level - varargs are used, which we did not consider yet (SIDL?) - these issues should be addressed at GGF17 - apart from that, a RPC package (outside strawman) should be feasable between GGF17 and GGF18 - TODO ANDRE: create CVS dir, set up package and issue list - note: RPC sata handles not yet considered - note: relation to web services need clarification (there are SAGA use cases for that)
- AOB: - TODO ANDRE: check how the GGF17 workshop agenda can be updated online - the 4th GGF session should dedicate some time to planning of tutorial and cookbook material
Comments/corrections welcome!
Quoting [Andre Merzky] (Apr 20 2006):
Hi folx,
attached is the current version of the issue list.
Cheers, Andre.
Quoting [Andre Merzky] (Apr 19 2006):
Date: Wed, 19 Apr 2006 21:24:19 +0200 From: Andre Merzky <andre@merzky.net> To: Shantenu Jha <s.jha@ucl.ac.uk> Cc: saga-rg@ggf.org Subject: Re: [saga-rg] SAGA conference call
Hi folx,
here are the call details:
Date: 20 April 2006 2:00 pm London Time: 3:00 pm Amsterdam 8:00 am Baton Rouge 10:00 pm Tokyo Number: 0844.888.8888 (UK) 01805.004.102 (Germany) +44.870.088.5706 (Others)
Code: 808044
Cheers, Andre.
Quoting [Shantenu Jha] (Apr 18 2006):
Date: Tue, 18 Apr 2006 14:14:58 +0100 (BST) From: Shantenu Jha <s.jha@ucl.ac.uk> To: saga-rg@ggf.org Subject: [saga-rg] SAGA conference call
Hi All,
After a brief hiatus, we're ready to resume our regular conference calls.
Suggested time for the next call is 2PM BST on Thursday 20th April, which translates to 8AM CST and 3PM in Amsterdam (and probably close to midnight in Tokyo. Sorry Pascal.)
The agenda for the next call is: - Issue List - SAGA and GridRPC How to coordinate activities of GridRPC into SAGA. - SAGA and GridCPR - AOB ?
Conference call details to come soon.
If you'd like to join, but suggested time doesn't work for you, please let us know.
Thanks.
-- "So much time, so little to do..." -- Garfield
participants (5)
-
Andre Merzky -
Graeme Pound -
Hidemoto Nakada -
Pascal Kleijer -
Shantenu Jha