SourceForge : artf3049: (1799) State Model

Project: OGSA-BES Working Group Trackers > BES V1.0 > View Artifact

Artifact artf3049 : (1799) State Model

Tracker:	BES V1.0
Title:	(1799) State Model
Description:	[From Steve Newhouse:] The main difference (at first glance) is a distinct Hold state for each primary state - although BES records the proceeding state so the BES generic Hold is qualified with where it came from. Dave Snelling stated that the state model was still under discussion so no further comment will be made here. However, it appears to be clear that different state models may be associated with different activities - and in many cases may be simpler that either the BES or ESI document. Perhaps linking the state model to the JSDL application type (e.g. POSIX) may be a way forward? This would allow (say) a WebServiceApplication type in the JSDL document to have a very simple model (running/not running). .
Submitted By:	David Snelling
Submitted On:	04/28/2006 6:30 AM EDT
Last Modified:	08/24/2006 12:23 PM EDT
Closed:	08/24/2006 12:23 PM EDT

	Status / Comments		Change Log		Associations		Attachments

Status
Group: *
Status:*	Closed
Category: *
Customer: *
Priority: *	1
Assigned To: *	None
Reported in Release: *
Fixed in Release: *
Estimated Hours: *	0
Actual Hours: *	0

Comments

Andrew Grimshaw: 08/24/2006 12:23 PM EDT
	Comment:	This is taken care of by the new extensible state model as described in the document. ASG
	Action:	Update Closed set to 08/24/2006 Status changed from Open to Closed

David Snelling: 07/06/2006 3:28 PM EDT

Comment:

Consensus from Dave, Chris, and Darren Proposal:

Go with the current proposal.

Use this or something very like it.

<ActivityState BaseState="running">
    <SubState StateName="profile1:Stagingin>
        <SubState StateName="profile1:Held"/>
    </SubState>
</ActivityState>


Add Unkonwn to the base case state model.

Also, the proposed sub states are:


Done: Finished, Canceled, Failed.

Running (and any substate of running): Held, Suspended.

Running: StagingIn, Executing, StagingOut

For Pending: Held

Action:

Update

David Snelling: 06/21/2006 11:49 AM EDT

Comment:

At this point we have, I believe, to run with a sub state model and make the main top level state diagram fairly simple.

Proposal for closing this tracker:

1) Agree that we should define HELD and SUSPEND substates as agreed and include them in the document.

2) Devise the schema strategy for describing a substate, e.g. How do I tell a held state in execution from a held state in staging in?

3) Open other trackers about the details of what the substate models should look like.

Action:

Update

David Snelling: 04/28/2006 6:42 AM EDT

Comment:

On 2006-04-19:

We defined:

- HOLD means stop after you completed the current state then you move to a hold state. 
- SUSPEND attempts to suspend the current state. The implementation may or may not support  suspension. This should be adverstised as a capability of 
the BES.

We agreed:
 
To add a HELD state.

Clarify the SUSPENDED state. 

Clarify the state transition table with a table. 

Change the CreateActivityFromJSDL to allow holds on any/all states. (e.g. Don't proceed past the  specified states).

Action:

Update

David Snelling: 04/28/2006 6:42 AM EDT
	Action:	Update Priority changed from - to 1

David Snelling: 04/28/2006 6:30 AM EDT
	Action:	Create

Return

< Previous

Next >