01/21/2010 11:12 AM
post6139
|
Meeting on 2010-01-21, 16:00 (CET) Agenda, Notes
Participants:
Etienne, Morris, Johannes, Emannouil, Balazs, Oxana, Jules, Luigi
a)
>-Debrief minutes of last PGI TelCon
>-
>-(b)
>-Debrief PGI actions
>-
>-(c)
>-Very short: continue discussion animation ppt of PGI operation & state model
>-Re: Developer experience says MUST might be tough
>-
>-(d)
>-Debrief Steven Newhouse comments on the list
>-
>-(e)
>-Debrief Bernd Schuller comments on the list
>-
>-(f)
>-Debrief Etienne Comments on the list
>-
>-(g)
>-Next meeting
>-
>-(h)
>-AOB
Balazs:
two more points for discussion
shift meeting half an hour earlier
agreed to shift the meeing on Thursday 15:30 (CET)
how to edit the document
make the document more readable
notes in ppt - reference in document to ppt
Balazs will be editor of the document
remark changes
Morris will keep track of ppt working slides
identify tasks which should be done by certain people
ad a)
add action: nail down ppt
lot of comments
ad b)
updated version of action will be sent out after the meeting
ad c)
going through the slides, editing the slides
outcome of last weeks discussion:
approach A will be chosen
short overview of the "dropped" approaches
Morris:
questions: what do ARC people think about?
Balazs:
two operations mandatory?
Morris:
discuss now
Balazs:
requirement part in createActivity operation
you should put a limit in your server for vector operations
sees no problem
Morris:
one step approach
here you get everything back
maybe broken job ids or
job ids point to broken jobs, killed jobs etc...
Balazs:
will fail because not validated
both are vector operations
spec requires validation
Morris:
only steps 1,2,3 are mandatory
Balazs:
what is the initial stat the job gets to
Etienne:
createActivity -> validated substate
before createActivity previous substate has to be created
submitted validating
submitted validated
Morris:
state model with different starting points?
Etienne:
initial state without name inside the submitted state
action for Balazs:
integrate discussed points in document before next meeting
Etienne:
notification can be only used if supported by SOAP
Morris:
keep this first out of PGI space
Balazs:
how can session directory be handled?
Morris:
back to the client we have two options
A use of GLUE elements in ResourceInfo portType
B query job properties in the Execution portType
Balazs:
and we have
0 SOAP Response contains it
next meeting:
discuss comments by S. Newhouse and B. Schuller
these comments are integrated int he ppt
Morris:
very good conclusions
Balazs will check this with spec before next meeting - highlight points to be discussed
Etienne:
title of document change?
Balazs:
Etienne will edit document with track changes on
Etienne:
move chapter 5 before chapter 2
Balazs:
will be done
|
|
|