On Thu, Oct 7, 2010 at 6:08 AM, Andre Merzky <andre@merzky.net> wrote:
Quoting [Sylvain Reynaud] (Oct 05 2010):
Hi Andre,
How much time should we spend on each set of demos ?
I think that 15 to 30 minutes would be sensible. We do have enough session time scheduled though to go beyond that time limit, if required (see separate mail).
Thank you for clarification on this. Regarding on this, we, KEK would give a demonstration at OGF30. We would much appreciate if you could assign us to appropriate session 1-4. We are okay to show up either session. For a moment we are planing to take a 30 mins for demo, that can be arranged either longer or shorter though. Regards, Go
In our set of demos, we would like to show how we can use two implementations of SAGA into the same application (SAGA-Cpp/JSAGA with Python, and if technically possible Java-SAGA/JSAGA with Java).
Sounds great! :-D
-> is there any URL where we can download the PySAGA wrapper for SAGA-Cpp (even if it is not yet finished)?
AFAIK, http://gforge.cs.vu.nl/gf/project/pysaga/scmsvn/?action=browse&path=%2Fimpl%2F points to the svn repository containing the relevant sources.
-> can we use SAGA-Cpp Service Discovery API extension from Python ?
The SD package is available, see https://svn.cct.lsu.edu/repos/saga/bindings/python/trunk/packages/sd I do not know how well tested that package is. Hartmut, any input?
Best, Andre.
Cheers, Sylvain
Andre Merzky a écrit :
Quoting [Sylvain Reynaud] (Aug 12 2010):
I can answer for JSAGA : Job management : WMS, CREAM, (LCG-CE not achived) Data management: SRM (DPM and dCache supported), LFC Security: VOMS, MyProxy
...but as I said in my previous mail, for the demo I think it is more interesting to show that SAGA implementations can complement each other rather than showing that they can do the same thing!
That is likely true. Also, it seems unlikely that we get a set of resources which are accessible by all implementation groups.
The most sensible (and also easiest) way forward would then be, IMHO, that each group is preparing their own set of demos, against the set of backends they use anyway, and we run one demo after the other, presentation style.
For some backends we could also consider to set up a demo resource via AWS, bu preparing an image which runs globus, glite, etc. But the effort for that is hart to estimate (for me). Is there a need/use for that? Any volonteers who could help with setup?
Best, Andre.
Cheers, Sylvain
Cheers, Ole
bes (all?)
Infrastructures local institutions teragrid loni naregi What about European Grids?
Again, is there something I miss?
PySAGA appears to be a great integration point, and SAGA-C++ intents to support it very soon, too - but it is not sure that we manage to do that before OGF30.
A simple interop demo would be to submit the same job (NOT /bin/date) to a set of resources in the various infrastructures discovered via SD, from various tools. A job submitted via python for example should be monitorable from C++ tools, and output could be reaped via PySAGA-over-JSAGA, etc.
The above is just an initial input, to get the discussion and planning started. Please feed back, and complete the item lists above. Once we have those lists complete, we should be able to come up with some more or less realistic scenario.
I'll mirror thiss list on our wiki at GridForge, so that we can edit things in place. Feel free to discuss on the list though, I'll try to keep the thread in sytnc with the wiki.
Best, Andre.
-- Nothing is ever easy. -- saga-rg mailing list saga-rg@ogf.org http://www.ogf.org/mailman/listinfo/saga-rg
-- saga-rg mailing list saga-rg@ogf.org http://www.ogf.org/mailman/listinfo/saga-rg
-- Nothing is ever easy. -- saga-rg mailing list saga-rg@ogf.org http://www.ogf.org/mailman/listinfo/saga-rg