I had not had the time to review all of this, but I like to suggest that a "task" has also the option to be suspended or resumed. you also need an introspector to actually find out if for example a particular feature has been implemented or not. You ma be in the need to define NonSuspendableTasks in which you for example do not have resume or suspend options. This has actually implications on how we intend to use this as part of future portal developments. Hers the "tasks" could encapsulate a lotincluding file transfers and job submissions ... As a file transfer as wll as a job could be suspended its important that both have at least the ability to be supported in that way. Gregor Andre Merzky wrote:
Nice, thanks!
To save everybody from the need to search GrodForge, here is the table from the document:
bes::job saga::task saga::job
New Pending Queued Pending Running Queued StagingIn Running PreExecution ExecutionPending Running PreExecution Running Running Running ExecutionComplete Running PostExecution StagingOut Running PostExecution CleaningUp Running PostExecution ShuttingDown Running PostExecution Suspended Running Suspend Suspended Running SuspendUser Suspended Running SuspendSystem NotKnown Unknown Unknown Other Unknown Unknown Done Done DoneOK Terminated Failed DoneFail Exception Failed DoneFail HoldSystem HoldUser Hold
In repspect to the original topic (task/job), these map fairly well to the task and job states we have, but are more detailed. I could not find an equivalent for Hold.
Are there other models defined in GGF, or is that _THE_ model?
Cheers, Andre.
Quoting [Steven Newhouse] (Feb 05 2006):
Date: Sun, 05 Feb 2006 07:04:28 +0000 From: Steven Newhouse
To: Andre Merzky CC: Simple API for Grid Applications WG Subject: Re: [saga-rg] job states... Hi Andre,
The Basic Execution Service WG has done some work on defining an activity state. You may want to have a look at that - there should be a copy on gridforge - somewhere!
Steven