Meeting of SAGA-RG at GGF17 1st meeting, may 10, 1:45 - 3:15 Session chaired by Shantenu Jha Notes taken by Andre Merzky, Thilo Kielmann Agenda: - agenda bashing - group progress - requirements document Shantenu opens the session, circulates the sign-up sheet, referring to GGF's IPR pollicy. agenda bashing: --------------- the agenda is accepted "as is" by the participants group progress: --------------- SAGA-RG's Use case document has been published as GFD.70 SAGA-RG's Requirements documents is now in public comments period requirements document: ---------------------- Shantenu is summarizing the findings of the requirements document, asking for comments and proposals to approach the missing pieces of the intended scope of SAGA 1.0. - monitoring: - comment: globus is giving insufficient info on job status - answer: is backend problem, not API problem - comment: what do you mean by steering - answer: track and change parameters of running applications - RPC: - not covered, but needed, in work -> have a design team - bulk: - comment: what means bulk - more than 2? - answer: bulk is just optimization, and API should not hinder optimized implementations - comment: replace 'saga version 2' with 'future saga versions' - resource discovery/information - comment (Michael Russell): Res. Discovery crucial for portal centered use cases, and probably for interactive usage in general - comment (Dieter, others): why handle security at all, if no general paradigm can be defined/found? - answer: why indeed :-) That is why we limit ourself to minimal approach (context), and use only paradigms as available and acknowledged (ACL) - CPR: - no resources to advance docs/API - want/need feedback from API - take offline time in Tokyo and draft API - circulate docs as are on the SAGA list - prioritize - 5 items identified, with no clear priority - RPC (rpc-wg) - CPR (Derek, Thilo, Shantenu) - InfoService (Andre) - Message (Andrei, Andre) - resource discovery (simple) At 3:15 the session is closed.