March 2007 - saga-rg - lists.ogf.org

Fwd: [jsdl-wg] FINAL CALL on SPMDApplication
by Andre Merzky 04 Apr '07

04 Apr '07

Hi Folx, Attached is the current draft of the SPMD extension of JSDL (JSDL SPMD Application Extension, Version 1.0). The extension is fairly simple. Roughly spoken, the draft introduces three new elements(*) used to describe parallel applications. These elements are: NumberOfProcesses (integer) ProcessesPerHost (integer) ThreadsPerProcess (integer) SPMDVariation (MPI/GridMPI/...) The JSDL grop would certainly be happy about comments. Apart from that, we should consider to add these elements to our job description. Any opinion about that? Cheers, Andre. ----- Forwarded message from Andreas Savva <andreas.savva(a)jp.fujitsu.com> ----- > From: Andreas Savva <andreas.savva(a)jp.fujitsu.com> > To: Andre Merzky <andre(a)merzky.net> > Subject: [Fwd: [jsdl-wg] FINAL CALL on SPMDApplication (was [Fwd: > SPMDApplication draft 6 and request for parallel application names])] > > Hi Andre, > > I think at OGF19 I promised to send you an email when the parallel > application extension went to final call within the jsdl group. > > Comments welcome. > Andreas > From: Andreas Savva <andreas.savva(a)jp.fujitsu.com> > To: Mailing List for JSDL-WG <jsdl-wg(a)ogf.org> > Subject: [jsdl-wg] FINAL CALL on SPMDApplication (was [Fwd: SPMDApplication > draft 6 and request for parallel application names]) > > Hi, > > I have not received any comments on the draft posted last week and there > are no outstanding issues. As we discussed on the last call I am putting > this now in final call within the group. The plan is to submit it to the > OGF Editor for public comment at the end of the week (Friday 16). > > For those who may not be familiar with the process, after submission to > the OGF Editor this document will enter a public comment period of > 60-days so you will have plenty of time to comment later on. -- "So much time, so little to do..." -- Garfield

2 3

spec repository changes...
by Andre Merzky 31 Mar '07

31 Mar '07

Hi, I would like to rename a several files in the saga core spec cvs repository. In the (probably unlikely) case that anybody has outstanding changes, please commit them over the next 48 hours, to avoid conflicts. Thanks, Andre. -- "XML is like violence: if it does not help, use more."

1 0

Re: [SAGA-RG] SAGA/GridCPR Phone call (fwd)
by Andre Merzky 31 Mar '07

31 Mar '07

Short meeting notes: - callers: Pascal, Thilo, Shantenu, Andre - CPR documents are deemed ok for one week last call - ANDRE to send docs to list - docs will go to the editor after Friday next week - Resource Discovery: a group in Texas, collaborating with CCT, expressed interest in driving that part of the specification - Shantenu/Ole are to get in contact with them, and to ask for intented scope and appraoch - other topics postponed Cheers, Andre. > ---------- Forwarded message ---------- > > Hi all, > > we again scheduled a SAGA phone call for tom^H^H^H today > 14:00 UTC, which is: > > UTC 29-03-2007 14:00 > HST Pacific/Honolulu 29-03-2007 4:00 > AKDT America/Anchorage 29-03-2007 6:00 > PDT America/Los_Angeles 29-03-2007 7:00 > CDT America/Chicago 29-03-2007 9:00 > EDT America/New_York 29-03-2007 10:00 > BST Europe/London 29-03-2007 15:00 > CEST Europe/Berlin 29-03-2007 16:00 > MSD Europe/Moscow 29-03-2007 18:00 > CT Asia/Shanghai 29-03-2007 22:00 > JT Asia/Tokyo 29-03-2007 23:00 > EST Australia/Melbourne 30-03-2007 0:00 > > The call details are: > > Date: 28 March 2007 > Time: 4:00 PM CEST > Number: 0844.888.8888 (UK) > 01805.004.102 (Germany) > +44.870.088.5706 (outside UK) > Code: 808044 > > Agenda: > > - progress on CPR doc changes > - service discovery API (depending on Steve calling in) > - resource discovery API (short) > > > FWIW, some short notes from last call: > > - calling in: Nathan, Derek, Andre, Thilo, Shantenu > - discussed public comments of CPR docs > - TODO NATHAN: apply comments to architecture doc > - TODO ANDRE: apply comments to usecase doc > - synchronize March 28 > > Cheers, Andre. -- "So much time, so little to do..." -- Garfield

1 0

Announcement: first SAGA C++ Release
by 'Andre Merzky' 30 Mar '07

30 Mar '07

--------------------------------------------------------- Our excuses if you receive multiple copies of this mail --------------------------------------------------------- We are proud to announce the first beta releas of our SAGA C++ implementation! (available at http://saga.cct.lsu.edu/) The implementation tries to strictly implement the SAGA Core API specification, and is designed to allow bindings to multiple Grid middlewares, by using a plugin mechanism (adaptors). At the moment, only bindings to local functionality is included by default, but we are working on providing bindings to the following Grid systems: - Globus Pre-WS - Globus WS (http://www.globus.org/) - OMII-OK (GridSam & Co.) (http://www.omii.ac.uk/) - XtreemOS (http://www.xtreemos.eu/) Nevertheless, this release is functional on its own and can be used for application development and testing in local environments. The goal of this release is twofold: Firstly, we want to use this release for a number of tutorials over the next months, to allow grid application developers to familiarize themself with the SAGA C++ API bindings. Secondly, we would like to involve grid middleware developers as early as possible, to plan for adaptor development for their middleware. The release has a number of known shortcomings (approximate timelines for release fixes are given): - the documentation, for both end users and adaptor developers, is minimal - for questions/feedback, please use the mailinglist at saga-users(a)cct.lsu.edu - end user documentation is expected by October 2007 - only few examples are included - we are working on tutorial material and examples, which should be available by June 2007 - remote adaptors will be released separately, with most of the ones mentioned above by Fall 2007 Having said that: the release IS fully functional, and has been tested on Linux, Windows and MacOS-X (build environments for all three platforms are included). We would appreciate feedback and bugreports, on the mailing list at saga-users(a)cct.lsu.edu and on the bug tracker at http://fortytwo.cct.lsu.edu:8000/SAGA Best regards, Harmut Kaiser (CCT/LSU) Andre Merzky (VU) Ole Weidner (CCT/LSU)

1 0

Re: [SAGA-RG] [GRIDCPR-WG] CPR Document - final call
by Thilo Kielmann 29 Mar '07

29 Mar '07

All, I am not sure what to do with this comment. (And I am not sure if we can do this, formally, at this stage of the process.) Anyway, just for doing something reasonable, I am in favour of adding this use case. Thilo On Thu, Mar 29, 2007 at 03:23:58PM +0200, Eduardo Huedo Cuesta wrote: > From: Eduardo Huedo Cuesta <ehuedo(a)fdi.ucm.es> > To: Andre Merzky <andre(a)merzky.net> > Cc: gridcpr-wg(a)ogf.org, SAGA RG <saga-rg(a)ogf.org> > Subject: Re: [GRIDCPR-WG] CPR Document - final call > > Dear All, > > From the GridWay team, we would like to propose another consumer > use-case that we think is within the scope of GridRPC. See below. > > Best Regards, > > Eduardo Huedo. > > -------------------------------------------------------------------- > > GridWay Metascheduler > ================= > > The GridWay Metascheduler [1, 2], now a Globus project, adapts job > execution to changing grid conditions by providing fault recovery > mechanisms, dynamic scheduling, migration on-request and opportunistic > migration [3]. Migration is implemented by restarting the job on the new > candidate host, therefore the job should generate restart files at > regular intervals in order to continue execution from a given point. If > checkpointing files are not provided, the job is restarted from the > beginning. GridWay periodically retrieves to the client machine or a > checkpoint server (GridFTP URL) the restart architecture-independent files. > > Jobs submitted with GridWay could benefit from GridCPR systems providing > standard and uniform APIs and services for portable checkpoint > generation and storage. > > Functional requirements > . API for application state writing and reading. > . Services for failure notification. > . Services for checkpoint data management. > > [1] GridWay Metascheduler. http://www.gridway.org/. > [2] E. Huedo, R.S. Montero and I.M. Llorente: A framework for adaptive > execution on grids. Software - Practice and Experience 34 (7): 631-651, > 2004. > [3] E. Huedo, R. S. Montero, I. M. Llorente: Evaluating the reliability > of computational grids from the end user's point of view. Journal of > Systems Architecture 52(12): 727-736, 2006. > > Andre Merzky escribió: > > Hi groups, > > > > as discussed earlier, we put some effort into the GridCPR > > documents, to get them back into the editor pipeline. > > Thanks to Nathan and others, both the CPR usecase and the > > cpr architecture document have now all public comments > > addressed, and are to be submitted to the OGF editor. > > > > The docs are supposed to represent groups consensus after > > submission, so, this mail is a one week final call on the > > mailing list: please review the documents, and comment on > > them! "speak now or forever hold your peace ..." :-) > > > > Cheers, Andre. > > > > > > ------------------------------------------------------------------------ > > > > -- > > gridcpr-wg mailing list > > gridcpr-wg(a)ogf.org > > http://www.ogf.org/mailman/listinfo/gridcpr-wg > > -- > > GridWay, Meta-scheduling Technologies for the Grid! http://www.gridway.org > > ************************************************** > > Dr. Eduardo Huedo Cuesta > Departamento de Arquitectura de Computadores > y Automática > Facultad de Informática > Universidad Complutense de Madrid > C/ Prof. García Santesmases s/n > 28040 Madrid > Spain > > Tel: +34 91 394 76 03 > Fax: +34 91 394 75 27 > Email: ehuedo(a)fdi.ucm.es > > ************************************************** > > -- > gridcpr-wg mailing list > gridcpr-wg(a)ogf.org > http://www.ogf.org/mailman/listinfo/gridcpr-wg -- Thilo Kielmann http://www.cs.vu.nl/~kielmann/

2 2

CPR Document - final call
by Andre Merzky 29 Mar '07

29 Mar '07

Hi groups, as discussed earlier, we put some effort into the GridCPR documents, to get them back into the editor pipeline. Thanks to Nathan and others, both the CPR usecase and the cpr architecture document have now all public comments addressed, and are to be submitted to the OGF editor. The docs are supposed to represent groups consensus after submission, so, this mail is a one week final call on the mailing list: please review the documents, and comment on them! "speak now or forever hold your peace ..." :-) Cheers, Andre. -- "So much time, so little to do..." -- Garfield

2 1

Phone con - late notice!
by Andre Merzky 28 Mar '07

28 Mar '07

---- sorry for crossposting ---- Hi all, there have been several proposals to resume the weekly telephone calls for the SAGA groups, and we want to start that this week, and, in fact, today. I am really sorry for the extremely short notice, that completely my fault; but several people have the slot already blocked for the call, so we can't really move it. Todays topic is CPR, so this invitation goes to the GridCPR list, too. Anyway, we would like to propose to have the call weekle, as said, at the following time: UTC 21-03-2007 15:00 HST Pacific/Honolulu 21-03-2007 5:00 AKDT America/Anchorage 21-03-2007 7:00 PDT America/Los_Angeles 21-03-2007 8:00 CDT America/Chicago 21-03-2007 10:00 EDT America/New_York 21-03-2007 11:00 GMT Europe/London 21-03-2007 15:00 CET Europe/Berlin 21-03-2007 16:00 MSK Europe/Moscow 21-03-2007 18:00 CT Asia/Shanghai 21-03-2007 23:00 JT Asia/Tokyo 22-03-2007 0:00 EST Australia/Melbourne 22-03-2007 2:00 That is kind of stretching it for Pascal and other folx in Asia, for sure, so we should consider to move it one or two hours, if nobody from the west coast plans to call in. The topics for the next calls are: - today: CPR - March 28: Service Discovery - April 4: Message Bus API Rest assured: topics after that will be plenty ;-) Suggestions are welcome, also if call timing is a problem for you. The details for todays call are: Date: 21 March 2007 Start: 4:00 PM Central Europe Time (conversion see above) Number: 0844.888.8888 (UK) 01805.004.102 (Germany) +44.870.088.5706 (International) Code: 808044 Cheers, Andre. -- "So much time, so little to do..." -- Garfield

1 2

Re: [SAGA-RG] [saga-cvs] "SAGA-RG/CPR-Architecture cpr_architecture_components.tex"
by Andre Merzky 21 Mar '07

21 Mar '07

Hi Nathan, what was the problem with the figure? Seemed to work for me (tm), and your fix actually breaks the dvi build, as png's work only for pdflatex, not for the normal latex... Cheers, Andre. Quoting [Nathan Stone] (Mar 21 2007): > > Modified Files: > cpr_architecture_components.tex > Log Message: > changed the filename of the figure, so that it builds correctly > > > _______________________________________________ > saga-cvs mailing list > saga-cvs(a)cct.lsu.edu > https://mail.cct.lsu.edu/mailman/listinfo/saga-cvs -- "So much time, so little to do..." -- Garfield

1 0

CPR documents...
by Andre Merzky 15 Mar '07

15 Mar '07

---------------------------------------------------- Sorry for crossposting. Followups should go to the GridCPR list only. ---------------------------------------------------- Hi all, the GridCPR WG had two documents in the GGF/OGF document pipeline (informational). Both are stuck in the pipeline, after already passing public comment, mostly for the reason that people left the CPR WG, and nobody addressed the comments, and finalized the documents. As the SAGA RG/WG use the documents to motivate the CPR API package in SAGA, some people felt motivated to pick up the CPR docs, and push them through the last stages of the pipeline. Now, for that purpose we re-created the documents, put them into the SAGA CVS, and started to address the public comments. However, as the documents are somewhat old by now, it seems appropriate to reconsider a number of elements in respect to new developments in OGF (e.g. data manegement and security can be more explicetly marked as external, as can the API). We would appreciate if people from both groups could read the documents once more, and provide in-group feedback. In particular the architecture document would benefit from that. The documents are attached. Please let us know if you want write access to CVS directly. The URLs for the public comments are: http://forge.ogf.org/short/EDITOR/doc-cpr-uc http://forge.ogf.org/short/EDITOR/doc-cpr-arch Cheers, Andre. -- "So much time, so little to do..." -- Garfield

1 0

OGF20 sessions - last call
by Andre Merzky 13 Mar '07

13 Mar '07

Hi folx, thanks for the feedback about sessions at OGF20, and sorry for the late follow-up... The draft session agendas below should cover the topics mentioned on the list, and also those topics we have to cover in respect to our document deadlines. We should have our Core API document back in the pipeline by then, so we won't discuss much about it. However, there are a number of biggish stumbling blocks open in the core, so in case we don't get that off the table by OGF20, we need to dedicate session time to them. Hence I introduce a half session as an emergency placeholder there, which we could re-dedicate as needed. In general, it is somewhat difficult to plan the sessions exactly: there are so many things/docs in flux, and a number of ongoing activities, that it is difficult to estimate in what state things will be by OGF20. Given the tight time constraints in Manchester, we should probably not ask for more sessions than the ones listed below, but we might consider to plan for additional time to spend on hot topics on Thursday. We'll cretainly find some space, and be it a nice british pub somewhere... ;-) 1) "SAGA Overview" - scheduled on Wednesday - to target both OGF and EGEE crowd - organized and led by Thilo, pure outreach session - material contribution welcome (implementations!) 2) WG: 90 min, SAGA Core, Language Bindings - discuss open issues in the SAGA Core API, if any - discuss the SAGA Java Language bindings (that work is slowly starting now, and there is potential for lots of discussions... ;-) - JSR? 3) RG: SAGA promotion plans, uptake, outreach - session is not supposed to DO these things, but to plan and coordinate - we should invide the non-standards councils - common repository for publications, tutorials, examples, ...? - work on users guide - vendor adoption - SAGA versus CoG / programming models 4) WG: SAGA extensions - the usual suspects: message bus API (yes, there is a renaming proposal! :-), service discovery, resource discovery, CPR - some of the respective docs should be close to publish comment by then - CPR: we are in the process fo refacturing the CPR documents - they need some polish, and should be pushed back into the pipeline, too. Lets polish that at OGF20. Thanks, Andre. -- "So much time, so little to do..." -- Garfield

1 0