August 2006 - saga-rg - lists.ogf.org

Reminder: Next SAGA conf call - Wednesday 30 August
by Shantenu Jha 02 Sep '06

02 Sep '06

[Note slightly different time from previous weeks.] Date: Wednesday 30 August, 2006 2:30 pm London Time: 3:30 pm Amsterdam 8:30 am Baton Rouge 10:30 pm Tokyo Number: 0844.888.8888 (UK) 01805.004.102 (Germany) +44.870.088.5706 (Others) Access Code: 84714 Agenda: - V1.0 Document - feedback - issue list - next steps - AOB

2 3

RE: [drmaa-wg] Aug 22 Meeting Minutes
by Rajic, Hrabri 29 Aug '06

29 Aug '06

Andre, Joel, Our needs are taken care of. Thanks a lot! Regards Hrabri >-----Original Message----- >From: Andre Merzky [mailto:andre@merzky.net] >Sent: Tuesday, August 29, 2006 1:36 PM >To: Joel Replogle >Cc: Rajic, Hrabri; DRMAA Working Group; Andre Merzky; Simple API for Grid >Applications WG >Subject: Re: [drmaa-wg] Aug 22 Meeting Minutes > >For what its worth, the new DRMAA archive is at >http://www.ogf.org/pipermail/drmaa-wg/ > >Please be aware that the URL might change, and that the >archive is a snapshot from a couple of weeks ago (end July) >- so I am not sure if it helps you much. > >As Joel said, we hope to have the migration completed before >GGF18. > >Cheers, Andre. > > >Quoting [Joel Replogle] (Aug 29 2006): >> Cc: DRMAA Working Group <drmaa-wg(a)gridforum.org>, >> Andre Merzky <andre(a)merzky.net>, >> Simple API for Grid Applications WG <saga-rg(a)ggf.org> >> From: Joel Replogle <replogle(a)ggf.org> >> Subject: Re: [drmaa-wg] Aug 22 Meeting Minutes >> Date: Tue, 29 Aug 2006 13:45:25 -0400 >> To: "Rajic, Hrabri" <hrabri.rajic(a)intel.com> >> >> All - The web-accessible email archives did indeed stop in mid-June, >> when GGF servers were moved from Argonne (where continued hosting of >> them became cost-prohibitive) to a new location. Email lists, >> however, continued to be hosted and archived at Argonne, but their >> archives were no longer available through the web. >> >> The intent was that email lists would quickly be migrated and hosted >> on GGF servers as well, restoring the web-access to the archives. >> This migration, however, has taken longer than we anticipated. >> >> Andre Merzky has been hard at work getting the email server set up >> and lists migrated over. I believe we are very close (perhaps a few >> days away) to having everything functional on the new servers and >> accessible again. The email archives from June, July & August will >> be included in what is migrated over. >> >> My apologies for this delay. >> >> Thank you for your patience and understanding. >> >> Joel >> >> >> >> On Aug 29, 2006, at 1:11 PM, Rajic, Hrabri wrote: >> >> >DRMAA-WG is not alone in this. SAGA-RG also has incomplete e-mail >> >archive. >> > >> >The [old?] links from main GridForge pages point to possibly old e- >> >mail >> >repositories or it could be that the e-mail archiving is broken since >> >June. >> > >> >Andre, SAGA-RG co-chair has been involved in the new GridForge >> >redesign, >> >so he might be able to shed the light what is going on and who could >> >help. I am also copying Joel Replogle who administrates many GGF >> >day to >> >day activities. >> > >> >Hrabri >> > >> >[ .. ] >> >>The email archive that is linked off the new DRMAA home page does not >> >go >> >>past June 2006. Is there anything we can do about that? >> >> >> >>Daniel >> >> >> > >> >> ------------------------------------------------------------------------ >> ----------- >> Joel Replogle - Manager of Standards, Global Grid Forum >> replogle(a)ggf.org http://www.ggf.org >> > > > >-- >"So much time, so little to do..." -- Garfield

1 0

RE: [drmaa-wg] Aug 22 Meeting Minutes
by Rajic, Hrabri 29 Aug '06

29 Aug '06

DRMAA-WG is not alone in this. SAGA-RG also has incomplete e-mail archive. The [old?] links from main GridForge pages point to possibly old e-mail repositories or it could be that the e-mail archiving is broken since June. Andre, SAGA-RG co-chair has been involved in the new GridForge redesign, so he might be able to shed the light what is going on and who could help. I am also copying Joel Replogle who administrates many GGF day to day activities. Hrabri [ .. ] >The email archive that is linked off the new DRMAA home page does not go >past June 2006. Is there anything we can do about that? > >Daniel >

3 2

Re: SAGA Core API - last call for comments
by Andre Merzky 19 Aug '06

19 Aug '06

BTW, the mail went to: SAGA RG <saga-rg(a)ggf.org> DRMAA WG <drmaa-wg(a)gridforum.org> GridRPC WG <gridrpc-wg(a)ggf.org> Gabriele Allen <gallen(a)cct.lsu.edu> Malcom Atkinson <mpa(a)nesc.ac.uk> Henri Bal <bal(a)cs.vu.nl> Alexander Beck-Ratzka <alexander.beck-ratzka(a)aei.mpg.de> Chiaq Dekate <cdekate(a)cct.lsu.edu> Ian Foster <foster(a)mcs.anl.gov> Andrew Grimshaw <grimshaw(a)cs.virginia.edu> Stephan Hirmer <shirmer(a)cct.lsu.edu> Dayong Huang <dayong(a)csc.lsu.edu> Felix Hupfeld <hupfeld(a)zib.de> Andrei Hutanu <ahutanu(a)cct.lsu.edu> Keith Jacksin <krjackson(a)lbl.gov> Ceriel Jacobs <ceriel(a)cs.vu.nl> Konrad Karczewski <xeno(a)icis.pcz.pl> Hiro Kishimoto <hiro.kishimoto(a)jp.fujitsu.com> Dieter Kranzlmueller <dk(a)gup.jku.at> Lukasz Kuczynski <neron(a)icis.pcz.pl> Craig Lee <craig(a)rushg.aero.org> Jason Maasen <jason(a)cs.vu.nl> Satoshi Matsuoka <matsu(a)is.titech.ac.jp> Jon McLaren <maclaren(a)cct.lsu.edu> Reagan Moore <moore(a)sdsc.edu> Steven Newhouse <s.newhouse(a)omii.ac.uk> Ana Oprescu <aoprescu(a)few.vu.nl> Stephen Pickles <Stephen.Pickles(a)manchester.ac.uk> Thomas Radke <tradke(a)aei.mpg.de> Thorsten Schuett <schuett(a)zib.de> Ed Seidel <eseidel(a)cct.lsu.edu> John Shalf <jshalf(a)ncsa.uiuc.edu> Raul Sirvent <rsirvent(a)ac.upc.edu> Chris Smith <csmith(a)platform.com> David Snelling <David.Snelling(a)UK.Fujitsu.com> Osamu Tatebe <o.tatebe(a)aist.go.jp> Rob van Nieuwpoort <rob(a)cs.vu.nl> Gregor von Laszewski <gregor(a)mcs.anl.gov> Obviously, most won't answer, but if you know someone I forgot, please forward. Cheers, Andre. ----- Forwarded message from Andre Merzky <andre(a)merzky.net> ----- > Date: Fri, 18 Aug 2006 17:15:53 +0200 > From: Andre Merzky <andre(a)merzky.net> > To: SAGA RG <saga-rg(a)ggf.org> > Subject: [gridrpc-wg] SAGA Core API - last call for comments > > Hi folks, > > attached is the release candidate 1 of the SAGA Core API > specification. We want to ask you for final comments and > corrections before we submit the document to the editor. > > Please note that several FIXME's are still in the text, and > please note also that Appendix B contains a list of known > open issues -- there is no need to report these issues back, > as we are working on those already (of course, > additions/comments/corrections to the issues are welcome). > > We would like to ask you for feedback in respect to the > following points: > > - do you consider your use case implementable in that API? > - is the API simple? > - is it correct? > - is the semantic what you would expect? > - is the syntax what you would expect? > - is the description detailed enough? > - would you be able to implement the SAGA API with the > spec? > - any other comments? > > The SAGA spec is by now a proud 213 page document. We don't > expect everybody to read the whole lot (although that would > be great ;-). So please feel free to pick those section you > are interested in, and feel most comfortable with commenting > on. We would like to recommend to read the General Design > section though, or at least skim through it. > > We would like to submit the spec into the editor pipeline in > about two weeks from now - for tat reason, we would > appreciate feedback in the next 10 days (deadline: Sunday, > August 27th). Of course you will have the ooportunity to > comment later as well, as the document will enter the 60 day > public comment -- however, we wouold like to catch critical > errors before that. > > Please feel free to forward this request for feedback to > whomever it may concern. Fedback is best given on the > SAGA-RG mailing list (saga-rg(a)ggf.org) you'll have to > subscribe to post though. Alternatively you can send email > to me or the other authors (emails are given in the doc). > > Many thanks for your time, > > Andre and the other SAGA-RG/SAGA-CORE-WG chairs. > > > PS.: if you are don't know what SAGA is all about, have a > look at our requirement document (GFD.71) at > http://forge.ggf.org/sf/docman/do/downloadDocument/projects.saga-rg/docman.… -- "So much time, so little to do..." -- Garfield

1 0

SAGA Core API - last call for comments
by Andre Merzky 18 Aug '06

18 Aug '06

Hi folks, attached is the release candidate 1 of the SAGA Core API specification. We want to ask you for final comments and corrections before we submit the document to the editor. Please note that several FIXME's are still in the text, and please note also that Appendix B contains a list of known open issues -- there is no need to report these issues back, as we are working on those already (of course, additions/comments/corrections to the issues are welcome). We would like to ask you for feedback in respect to the following points: - do you consider your use case implementable in that API? - is the API simple? - is it correct? - is the semantic what you would expect? - is the syntax what you would expect? - is the description detailed enough? - would you be able to implement the SAGA API with the spec? - any other comments? The SAGA spec is by now a proud 213 page document. We don't expect everybody to read the whole lot (although that would be great ;-). So please feel free to pick those section you are interested in, and feel most comfortable with commenting on. We would like to recommend to read the General Design section though, or at least skim through it. We would like to submit the spec into the editor pipeline in about two weeks from now - for tat reason, we would appreciate feedback in the next 10 days (deadline: Sunday, August 27th). Of course you will have the ooportunity to comment later as well, as the document will enter the 60 day public comment -- however, we wouold like to catch critical errors before that. Please feel free to forward this request for feedback to whomever it may concern. Fedback is best given on the SAGA-RG mailing list (saga-rg(a)ggf.org) you'll have to subscribe to post though. Alternatively you can send email to me or the other authors (emails are given in the doc). Many thanks for your time, Andre and the other SAGA-RG/SAGA-CORE-WG chairs. PS.: if you are don't know what SAGA is all about, have a look at our requirement document (GFD.71) at http://forge.ggf.org/sf/docman/do/downloadDocument/projects.saga-rg/docman.… -- "So much time, so little to do..." -- Garfield

1 0

RE: [saga-cvs] "SAGA-RG/Strawman job_states.eps job_states.figjob_states.pdf job_states.png job_states_bes.epsjob_states_bes.pdf job_states_new.eps job_states_new.figjob_states_new.pdf job_states_new.png states.eps states.figstates.pdf states.png strawman
by Hartmut Kaiser 17 Aug '06

17 Aug '06

Some (or all) of the images are not checked in as binaries. Could you please re-add them with -kb? Regards Hartmut > -----Original Message----- > From: saga-cvs-bounces(a)cct.lsu.edu > [mailto:saga-cvs-bounces@cct.lsu.edu] On Behalf Of Andre Merzky > Sent: Thursday, August 17, 2006 6:43 AM > To: saga-cvs(a)cct.lsu.edu > Subject: [saga-cvs] "SAGA-RG/Strawman job_states.eps > job_states.figjob_states.pdf job_states.png > job_states_bes.epsjob_states_bes.pdf job_states_new.eps > job_states_new.figjob_states_new.pdf job_states_new.png > states.eps states.figstates.pdf states.png strawman_job > > Update of /projects/SAGA-RG/Strawman > In directory asylum.cct.lsu.edu:/tmp/cvs-serv18911 > > Modified Files: > job_states.eps job_states.fig job_states.pdf job_states.png > job_states_bes.eps job_states_bes.pdf job_states_new.eps > job_states_new.fig job_states_new.pdf job_states_new.png > states.eps states.fig states.pdf states.png strawman_job.tex > strawman_stream.tex strawman_tasks.tex stream_states.eps > stream_states.fig stream_states.pdf stream_states.png > task_states.eps task_states.fig task_states.pdf > task_states.png > Log Message: > more work on states. Thilo, _now_ you can criticise the > images :-P Please note that dvi preview is different from the > ps/pdf result. Fonts should actually be embedded in the > eps/pdf files which I commited. > > Finished work on job section, more or less. Needs review, > and sanity check (really!). > > A. > > > _______________________________________________ > saga-cvs mailing list > saga-cvs(a)cct.lsu.edu > https://mail.cct.lsu.edu/mailman/listinfo/saga-cvs >

1 0

Reminder: Next SAGA conf call - Wednesday 16 August
by Shantenu Jha 16 Aug '06

16 Aug '06

Just in case... Agenda: - Issue List - Discuss remaining issues related to getting SAGA V1.0 into the GGF editorial process - AOB Here are the next conf-call details: Date: Wednesday 16 August, 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) Access Code: 78838

1 0

Final call: GridRPC API for inclusion in SAGA 1.0
by Thilo Kielmann 13 Aug '06

13 Aug '06

Dear all, Hidemoto Nakada, Yusuke Tanimura, and myself have met and we have re-worked the pending proposal for a GridRPC module for inclusion in the upcoming SAGA spec. The only thing we have changed is the way in which parameters to an RPC invocation are passed. Now, it is an array of parameters, where a paramter is a struct, consisting of buffer, size, and, IN/OUT/INOUT mode. We have also modelled examples from the Ninf-G web page with this API. We think that this now has a "look and feel" of GridRPC. Attached please find the proposed text with API and examples. If this (or something similar) can be agreed upon quickly, then the GridRPC module can be included in the SAGA 1.0 spec. We see this API not as a competitor to the GridRPC API, as published in GFD-R.52. It is rather an alternative, embedded in the SAGA framework, to access existing GridRPC implementations, thus extending their user base. We are now doing the final call for comments for the two groups involved. If you have comments or questions, please post them TO BOTH MAILING LISTS. This final call is open until FRIDAY, AUGUST 18th. Comments and objections made by then will happily be included in the proposal. By this deadline, we will add this text (with all modifications we got) into the SAGA API document. Thanks to you all for your contributions. Thilo Kielmann -- Thilo Kielmann http://www.cs.vu.nl/~kielmann/

3 9

LSU CVS maintenance has deleted part of the repository updates :-(
by Thilo Kielmann 12 Aug '06

12 Aug '06

Seems like the CVS server @CCT.LSU.EDU now has a rather old content, at least w.r.t. the strawman spec. For what I can see, at least my work from thursday is completely lost :-( I have just put aside the state I had from my backup, so I might be able to merge things back manually, but is there a better solution??? (Andre: my snapshot is in hydra:/net/kielmann/CVS.CCT.LSU.EDU.tar.gz, if you want to use it, too.) Thilo -- Thilo Kielmann http://www.cs.vu.nl/~kielmann/

1 0

FW: [Cvs-users] CCT CVS server outage / migration
by Hartmut Kaiser 11 Aug '06

11 Aug '06

FYI... > -----Original Message----- > From: cvs-users-bounces(a)cct.lsu.edu > [mailto:cvs-users-bounces@cct.lsu.edu] On Behalf Of Matthew Eastman > Sent: Friday, August 11, 2006 12:59 PM > To: CCT CVS Users > Subject: [Cvs-users] CCT CVS server outage / migration > > As many of you have noticed, we have been experiencing > serious issues with the current CCT CVS server > (cvs.cct.lsu.edu / cvs.cactuscode.org) over the last few > days. It is currently down and we are in the process of > migrating to newer, more stable hardware. It is expected to > be up soon (within the next couple of hours), and we ask for > your patience. > > If you experience any issues such as permissions problems or > corrupted or missing files after the new server is running, > please feel free to contact us at cvs-consult(a)cct.lsu.edu. > > Thanks for your cooperation, > Matt Eastman > > -- > Matthew Eastman > Center for Computation & Technology > 230 Johnston Hall > Louisiana State University > +1 225 578 0816 > > _______________________________________________ > Cvs-users mailing list > Cvs-users(a)cct.lsu.edu > https://mail.cct.lsu.edu/mailman/listinfo/cvs-users >

1 0