[SAGA-RG] planning for OGF-30 interop demo

[Ole Weidner]

Hi Andre,

On Aug 9, 2010, at 11:44 AM, Andre Merzky wrote:

> Hi all, 
> 
> as most of you should now by now, we plan a SAGA interop demo for
> OGF30 in Brussels (http://www.ogf.org/OGF30/).  In order to pull
> that off successfully, we need to start to define
> 
>  - participants
>  - scope
>  - implementations to be used
>  - interop demo scenario
> 
>> From the top of my head, I would think that the following parties
> might be interested to team up resources (endpoints, code, people)
> to get things in place:
> 
>  - VU Amsterdam
>  - IN2P3, France
>  - CCT, LSU
>  - KEK/Naregi
>  - RAL, UK
> 
> It would be great if each party could let us know explicitely if
> they are interested in participating!  Did I miss anybody?
> 
> We have the following bits and pieces which may, or may not, play a
> role in the interop demo
> 
>  implementations:
>    JavaSAGA
>    JSAGA
>    SAGA-C++
>    PySAGA (over JavaSAGA)
>    PySAGA (over JSAGA)
>    SAGA-Python (over SAGA-C++)
>    command line tools for most of the implementations
> 
>  functionality:
>    Job Submission (all)
>    Data transfer / access (all)
>    Advert Service (not JSAGA I think, not in PySAGA)
>    Replica Management (not JSAGA?)
>    Service Discovert (not in JSAGA?  not in PySAGA)
> 
>  backends:
>    local  (all)
>    globus (all)
>    ssh    (all)
>    aws    (all?)
>    glite  (all?)

We (as in LSU SAGA) currently support only gLite CREAM (job adaptor with X.509 contexts). What specific gLite components are you referring to? What do other SAGA implementations support? 

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 at ogf.org
>  http://www.ogf.org/mailman/listinfo/saga-rg