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

[Mariusz Mamoński]

Hi Andre,

On 11 August 2010 11:04, Andre Merzky <andre at merzky.net> wrote:
> Quoting [Morris Riedel] (Aug 10 2010):
>>
>> Dear Andre, all,
>>
>> >--   backends:
>> >--     local  (all)
>> >--     globus (all)
>> >--     ssh    (all)
>> >--     aws    (all?)
>> >--     glite  (all?)
>> >--     bes    (all?)
>>
>> In terms of using ogsa-bes, we can provide you with an UNICORE
>> endpoint and I'm quite sure that I can get you an ARC, OMII-UK &
>> GENESIS endpoint also.
>>
>> Please contact me and Steve Crouch (cc) once you agree to use this
>> backend interface with SAGA.
>
> Hi Morris, Steve,
>
> BES would indeed be interesting, as it is OGF relevant, obviously.
> Alas, not all implementations support it, yet.
>
> We actually do have access to a unicore, gridsam and arc endpoints:
>
> https://zam1161v01.zam.kfa-juelich.de:8002/DEMO-SITE/services/BESFactory?res=default_bes_factory)
> https://gridsam-endpoint.oerc.ox.ac.uk:18443/gridsam/services/hpcbp
> https://interop.grid.niif.hu:2010/arex-x509

if you want you can add another endpoints for the SMOA Computing service:

https://grass1.man.poznan.pl:19001 (UsernameToken)
https://grass1.man.poznan.pl:8080 (X509)

there were already some interoperability tests conducted involving our
BES implementation:
http://forge.gridforum.org/sf/wiki/do/viewPage/projects.gin/wiki/GINOGF27
>
> It has been a while since the last testing though, so I'll need to
> confirm that those are still valid/accessible.  A Genesis endpoint
> would be very interesting for many reasons, so I'd appreciate if you
> guys could provide access to such one for the demo! :-)
>
> Best, Andre.
>
>
>
>> Take care,
>> Morris
>>
>>
>>
>> >-- -----Ursprüngliche Nachricht-----
>> >-- Von: saga-rg-bounces at ogf.org [mailto:saga-rg-bounces at ogf.org] Im Auftrag von Andre Merzky
>> >-- Gesendet: Montag, 9. August 2010 11:45
>> >-- An: SAGA RG
>> >-- Cc: Hartmut Kaiser; Julien Devemy
>> >-- Betreff: [SAGA-RG] planning for OGF-30 interop demo
>> >--
>> >-- 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?)
>> >--     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
>
>
>
>
>
> --
> Nothing is ever easy.
> --
>  saga-rg mailing list
>  saga-rg at ogf.org
>  http://www.ogf.org/mailman/listinfo/saga-rg
>


Best Regards,
-- 
Mariusz