[ogsa-bes-wg] Another Q about the BES document

[Ian Foster]

Also: I am looking at the definition of the "Suspended" state. I understand 
that one way to get there is for a client to request a transition to that 
state, either by an initial CreateInSuspendedState flag or by a 
RequestActivityStateChanges operation. Is there another way for this state 
to be reached? The document includes these words:

"If any staging action enters the Suspendedstate, then the whole activity 
enters the Suspendedstate."

That implies to me that there is some way for a staging action to enter the 
Suspended state independently of the activity as a whole. How does that happen?

Thanks -- Ian.


At 08:38 AM 6/20/2006 -0500, Ian Foster wrote:
>Hi,
>
>I am reviewing (and editing) the BES document, and have a question that 
>doesn't seem worth raising in a tracker.
>
>In the state discussion, there are sentences something like the following:
>
>a) An activity stays in the StagingOutstate until all staging out actions 
>have moved to a Terminalstate (Done, Exception, Terminated).
>
>b) If the terminal state of any staging out actions is Exceptionthen the 
>activity moves to a Exceptionstate.
>
>I interpret these two sentences to mean that we only enter the Exception 
>state when all staging out actions have completed. I.e., that if one stage 
>out fails, but others are still going, we wait until the others have 
>completed before moving to the Exception state. Is that correct?
>
>Thanks -- Ian.

_______________________________________________________________
    Ian Foster, Director, Computation Institute
Argonne National Laboratory & University of Chicago
Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439
Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637
Tel: +1 630 252 4619.  Web: www.ci.uchicago.edu.
       Globus Alliance: www.globus.org.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/ogsa-bes-wg/attachments/20060620/8819d144/attachment.html