[saga-rg] Minutes from SAGA-CORE-WG at GGF17, 1st session

[Andre Merzky]

Hallo Thilo, 

ich hab die mail mit den notes zur zweiten WG-session nicht
mehr gefunden - kannst Du mir die nochmal forwarden?

Danke :-)

Andre.


Quoting [Thilo Kielmann] (May 29 2006):
> Date: Mon, 29 May 2006 18:52:09 +0200
> From: Thilo Kielmann <kielmann at cs.vu.nl>
> To: saga-rg at ggf.org
> Cc: office at ggf.org
> Subject: [saga-rg] Minutes from SAGA-CORE-WG at GGF17, 1st session
> 
> Meeting of SAGA-CORE-WG at GGF17
> 1st meeting, may 11, 3:45 - 5:15
> 
> Session chaired by Andre Merzky
> Notes taken by Shantenu Jha, Thilo Kielmann
> 
> Agenda:
> - agenda bashing
> - work on issue list for the SAGA1.0 spec
> 
> Andre opens the session, circulates the sign-up sheet, referring to
> GGF's IPR policy.
> 
> agenda bashing:
> ---------------
> 
> the agenda is accepted "as is" by the participants
> 
> 
> open issues from "the list":
> ----------------------------
> 
> job states
> ----------
> 
> the state diagram is revisited
> 
> Q: remove (or defer) job.checkpoint ? (->gridcpr)
> what about job.migrate ?
> 
> the discussion is leaning towards a 2 layer state model:
>   - a generic level
>   - detailed BES model
> 
> the differences revolve around "hold" states of jobs.
> Queueing systems do provide them, but applications seem to have little (no?)
> use of it. (see: SAGA use cases)
> How much should a SIMPLE API (-> "S"AGA) expose?
> 
> It is clear that SAGA states should be compatible with BES, however, possibly
> only have a proper subset in the generic level, and the full detail in the
> detailed level.
> 
> 
> action item : list the options, come to rough consensus
> have layered model
> Andre to place discussion both (bes and saga) mailing lists
> 
> 
> further issues from the issue list that were discussed:
> 
> 12, yes change
> 
> 29, see 2nd session (Stephan Hirmer's talk)
> 
> 30 ACLs
> 
>    Q: are all ACL systems equal?
>    e.g., NFS ACL vs WinFS vs Solaris AFS and will that cause problems?
> 
>    Andre agrees: SAGA has an omission - no provision for distinguished
>    names
> 
>   Line 81: strawman_namespaces   ACL_Admin ==> replace with ACL_Owner??
>   no! "admin" describes better the role of maintaining; these could be
>       multiple users, not just the single owner
> 
>   Use Base Case approach for security?
>          e.g. look at all the diff OS there is commonality and then
>          specific issues
> 
>   Andre: to post on the mailing list..
> 
> 36, language examples missing (not discussed)
> 
> 47, jsdl compliance and 88, clean up files
> 
>   JSDL has the notion of which files to get rid of after execution,
>   but support for this feature will be limited.
> 
>     JSDL: keep, remove, don't care (default)
> 
>   Andre: Add an attribute "clean_up"
> 
> 
> 55, references, not discussed
> 
> editing "only" comments skipped
> 
> 102, what classes need error handler
> 
>   ErrorHandle -- defined for languages like C - that do not have
>   an error interface.
> 
>   interface error_handle provides the ability to rethrow errors !
> 
>   provides guidelines for how procedural languages should handle errors.
> 
> check "has error type" ??? -> ask Tom
> -> add errorhandler interface to task
> 
> get_Error
> has_error
> 
> 
> 108 constness of operations
> do it in prosa, in/out/inout remain as in SIDL
> 
> 111 file constructors do open implicitly
> 
> agreed.
> 
> 132, bind resource manager to jobservice (in constructor)
> runjob needs to be discussed on the mailing list
> 
> Andre promises to buy beer for people willing to help writing/editing
> the spec doc. (From the note taker: it was not clear whether the beer
> should be paid before or after editiing the document.)
> 
> 
> At 5:15, the session is closed.



-- 
"So much time, so little to do..."  -- Garfield