This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/sfmain/do/go/doc15655?nav=1&selectedTab=versions at Sun, 06 Nov 2022 11:26:58 GMT SourceForge : Document Details

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Project: pgi-wg     Documents > Root Folder > Input Documents > Execution Service > State Model > Document Details
Document Details (Active Version)
Document Name: PGI Single Job State Model (ZARGO file)
Document ID: doc15655
Description: Proposal of Job State Model using UML :

ArgoUML is available at http://argouml.tigris.org/

The textual description is available at http://forge.gridforum.org/sf/go/doc15697
Version Comment: Following today's PGI session at OGF33, rename 'Submitted' as 'Pending' and 'Delegated' as 'Processing'.
Version Created By: Etienne URBAH - 09/21/2011 12:52 PM EDT
Status: Draft
Current Version: 57
Size: 48.24 KB
Lock:  Unlocked

Versions Associations Review  
  Active Version Version Comment Review Created By Status
Active Version 57 Following today's PGI session at OGF33, rename 'Submitted' as 'Pending' and 'Delegated' as 'Processing'. Etienne URBAH - 09/21/2011 Draft
Version 56 v12: 2 Use Cases : - CreateActivity performs minimal validation, quickly returns Jobids (but NO Stage-in information) and goes to 'Submitted:Incoming', - CreateValidatedActivity performs complete validation, may return Stage-in information, and goes directly to 'Submitted:Validated', at the expense of response time. Take into account that the Execution Service may be unable to provide one or both : - Notifications, - Output Sandboxes. (PNG drawing of the Big Diagram with Comments) Etienne URBAH - 02/10/2010 Draft
Version 55 v12: 2 Use Cases : - CreateActivity performs minimal validation, quickly returns Jobids (but NO Stage-in information) and goes to 'Submitted:Incoming', - CreateValidatedActivity performs complete validation, may return Stage-in information, and goes directly to 'Submitted:Validated', at the expense of response time. Take into account that the Execution Service may be unable to provide one or both : - Notifications, - Output Sandboxes. (PNG drawing of the Big Diagram) Etienne URBAH - 02/10/2010 Draft
Version 54 v12: 2 Use Cases : - CreateActivity performs minimal validation, quickly returns Jobids (but NO Stage-in information) and goes to 'Submitted:Incoming', - CreateValidatedActivity performs complete validation, may return Stage-in information, and goes directly to 'Submitted:Validated', at the expense of response time. Take into account that the Execution Service may be unable to provide one or both : - Notifications, - Output Sandboxes. (PNG drawing of the Medium Diagram) Etienne URBAH - 02/10/2010 Draft
Version 53 v12: 2 Use Cases : - CreateActivity performs minimal validation, quickly returns Jobids (but NO Stage-in information) and goes to 'Submitted:Incoming', - CreateValidatedActivity performs complete validation, may return Stage-in info rmation, and goes directly to 'Submitted:Validated', at the expense of response time. Take into account that the Execution Service may be unable to provide one or both : - Notifications, - Output Sandboxes. (PNG drawing of the Small Diagram) Etienne URBAH - 02/10/2010 Draft
Version 52 v12: 2 Use Cases : - CreateActivity performs minimal validation, quickly returns Jobids (but NO Stage-in information) and goes to 'Submitted:Incoming', - CreateValidatedActivity performs complete validation, may return Stage-in info rmation, and goes directly to 'Submitted:Validated', at the expense of response time. Take into account that the Execution Service may be unable to provide one or both : - Notifications, - Output Sandboxes. (XMI file readable by any UML tool) Etienne URBAH - 02/10/2010 Draft
Version 51 v12: 2 Use Cases : - CreateActivity performs minimal validation, quickly returns Jobids (but NO Stage-in information) and goes to 'Submitted:Incoming', - CreateValidatedActivity performs complete validation, may return Stage-in info rmation, and goes directly to 'Submitted:Validated', at the expense of response time. Take into account that the Execution Service may be unable to provide one or both : - Notifications, - Output Sandboxes. (ZARGO file created by ArgoUML) Etienne URBAH - 02/10/2010 Draft
Version 50 v11 : Exclude internal states. Second level Job states are also mandatory. Inside the 'Submitted' state : The Execution Service may already allocate resources - Rename 'Waiting' substate as 'Validated' - Add 'Hold' substate. (PNG drawing of the Big Diagram with Comments) Etienne URBAH - 12/17/2009 Draft
Version 49 v11 : Exclude internal states. Second level Job states are also mandatory. Inside the 'Submitted' state : The Execution Service may already allocate resources - Rename 'Waiting' substate as 'Validated' - Add 'Hold' substate. (PNG drawing of the Big Diagram) Etienne URBAH - 12/17/2009 Draft
Version 48 v11 : Exclude internal states. Second level Job states are also mandatory. Inside the 'Submitted' state : The Execution Service may already allocate resources - Rename 'Waiting' substate as 'Validated' - Add 'Hold' substate. (PNG drawing of the Medium Diagram) Etienne URBAH - 12/17/2009 Draft
Version 47 v11 : Exclude internal states. Second level Job states are also mandatory. Inside the 'Submitted' state : The Execution Service may already allocate resources - Rename 'Waiting' substate as 'Validated' - Add 'Hold' substate. (PNG drawing of the Small Diagram) Etienne URBAH - 12/17/2009 Draft
Version 46 v11 : Exclude internal states. Second level Job states are also mandatory. Inside the 'Submitted' state : The Execution Service may already allocate resources - Rename 'Waiting' substate as 'Validated' - Add 'Hold' substate. (XMI file readable by any UML tool) Etienne URBAH - 12/17/2009 Draft
Version 45 v11 : Exclude internal states. Second level Job states are also mandatory. Inside the 'Submitted' state : The Execution Service may already allocate resources - Rename 'Waiting' substate as 'Validated' - Add 'Hold' substate. (ZARGO file created by ArgoUML) Etienne URBAH - 12/17/2009 Draft
Version 44 v10 : Vector operations on Single Jobs do NOT imply Collection Jobs (which are out of scope). Any implementation of the PGI Execution Service MUST implement all first level Job states, exactly as described in this document. It MAY implement substates. If these substates correspond to substates described in this document, then these substates MUST be implemented exactly as described in this document. (PNG drawing of the Big Diagram with Comments) Etienne URBAH - 10/02/2009 Draft
Version 43 v10 : Vector operations on Single Jobs do NOT imply Collection Jobs (which are out of scope). Any implementation of the PGI Execution Service MUST implement all first level Job states, exactly as described in this document. It MAY implement substates. If these substates correspond to substates described in this document, then these substates MUST be implemented exactly as described in this document. (PNG drawing of the Big Diagram) Etienne URBAH - 10/02/2009 Draft
Version 42 v10 : Vector operations on Single Jobs do NOT imply Collection Jobs (which are out of scope). Any implementation of the PGI Execution Service MUST implement all first level Job states, exactly as described in this document. It MAY implement substates. If these substates correspond to substates described in this document, then these substates MUST be implemented exactly as described in this document. (PNG drawing of the Medium Diagram) Etienne URBAH - 10/02/2009 Draft
Version 41 v10 : Vector operations on Single Jobs do NOT imply Collection Jobs (which are out of scope). Any implementation of the PGI Execution Service MUST implement all first level Job states, exactly as described in this document. It MAY implement substates. If these substates correspond to substates described in this document, then these substates MUST be implemented exactly as described in this document. (PNG drawing of the Small Diagram) Etienne URBAH - 10/02/2009 Draft
Version 40 v10 : Vector operations on Single Jobs do NOT imply Collection Jobs (which are out of scope). Any implementation of the PGI Execution Service MUST implement all first level Job states, exactly as described in this document. It MAY implement substates. If these substates correspond to substates described in this document, then these substates MUST be implemented exactly as described in this document. (XMI file readable by any UML tool) Etienne URBAH - 10/02/2009 Draft
Version 39 - Vector operations on Single Jobs do NOT imply Collection Jobs (which are out of scope). - Any implementation of the PGI Execution Service MUST implement all first level Job states, exactly as described in this document. It MAY implement substates. If these substates correspond to substates described in this document, then these substates MUST be implemented exactly as described in this document. (ZARGO file created by ArgoUML) Etienne URBAH - 10/02/2009 Draft
Version 38 v9 : Write down that 'Cancellation' and 'Failure' can happen in any substate - Mention Time-out inside 'Delegated:Hold' (PNG drawing of the Big Diagram with Comments) Etienne URBAH - 07/29/2009 Draft
Version 37 v9 : Write down that 'Cancellation' and 'Failure' can happen in any substate - Mention Time-out inside 'Delegated:Hold' (PNG drawing of the Big Diagram) Etienne URBAH - 07/29/2009 Draft
Version 36 v9 : Write down that 'Cancellation' and 'Failure' can happen in any substate - Mention Time-out inside 'Delegated:Hold' (PNG drawing of the Medium Diagram) Etienne URBAH - 07/29/2009 Draft
Version 35 v9 : Write down that 'Cancellation' and 'Failure' can happen in any substate - Mention Time-out inside 'Delegated:Hold' (PNG drawing of the Small Diagram) Etienne URBAH - 07/29/2009 Draft
Version 34 v9 : Write down that 'Cancellation' and 'Failure' can happen in any substate - Mention Time-out inside 'Delegated:Hold' (XMI file readable by any UML tool) Etienne URBAH - 07/29/2009 Draft
Version 33 v9 : Write down that 'Cancellation' and 'Failure' can happen in any substate - Mention Time-out inside 'Delegated:Hold' (ZARGO file created by ArgoUML) Etienne URBAH - 07/29/2009 Draft
Version 32 v8 : Scope is Single Jobs only. This excludes Collection Jobs, Parameter Sweep Jobs, DAG Jobs, ... (PNG drawing of the Big Diagram with Comments) Etienne URBAH - 07/28/2009 Draft
Version 31 v8 : Scope is Single Jobs only. This excludes Collection Jobs, Parameter Sweep Jobs, DAG Jobs, ... (PNG drawing of the Big Diagram) Etienne URBAH - 07/28/2009 Draft
Version 30 v8 : Scope is Single Jobs only. This excludes Collection Jobs, Parameter Sweep Jobs, DAG Jobs, ... (PNG drawing of the Small Diagram) Etienne URBAH - 07/28/2009 Draft
Version 29 v8 : Scope is Single Jobs only. This excludes Collection Jobs, Parameter Sweep Jobs, DAG Jobs, ... (XMI file readable by any UML tool) Etienne URBAH - 07/28/2009 Draft
Version 28 v8 : Scope is Single Jobs only. This excludes Collection Jobs, Parameter Sweep Jobs, DAG Jobs, ... (ZARGO file created by ArgoUML) Etienne URBAH - 07/28/2009 Draft
Version 27 v7: State 'Delegated' : For substate 'Hold', add a transition from 'Incoming' and a transition to 'Outgoing' (PNG drawing of the Big Diagram with Comments) Etienne URBAH - 07/15/2009 Draft
Version 26 v7: State 'Delegated' : For substate 'Hold', add a transition from 'Incoming' and a transition to 'Outgoing' (PNG drawing of the Big Diagram) Etienne URBAH - 07/15/2009 Draft
Version 25 v7: State 'Delegated' : For substate 'Hold', add a transition from 'Incoming' and a transition to 'Outgoing' (PNG drawing of the Small Diagram) Etienne URBAH - 07/15/2009 Draft
Version 24 v7: State 'Delegated' : For substate 'Hold', add a transition from 'Incoming' and a transition to 'Outgoing' (XMI file readable by any UML tool) Etienne URBAH - 07/15/2009 Draft
Version 23 v7: State 'Delegated' : For substate 'Hold', add a transition from 'Incoming' and a transition to 'Outgoing' (ZARGO file created by ArgoUML) Etienne URBAH - 07/15/2009 Draft
Version 22 v6: Group 'Hold-*' substates inside second level 'Hold' substates - Add third level 'Suspended' substate inside each 'Hold' substate - Clearly separate 'Finished', 'Failed' and 'Cancelled' states - Add an 'Automatic Resubmission' transition to the 'Submitted' state only from the 'Failed' state (PNG drawing of the Big Diagram with Comments) Etienne URBAH - 07/14/2009 Draft
Version 21 v6: Group 'Hold-*' substates inside second level 'Hold' substates - Add third level 'Suspended' substate inside each 'Hold' substate - Clearly separate 'Finished', 'Failed' and 'Cancelled' states - Add an 'Automatic Resubmission' transition to the 'Submitted' state only from the 'Failed' state (PNG drawing of the Big Diagram) Etienne URBAH - 07/14/2009 Draft
Version 20 v6: Group 'Hold-*' substates inside second level 'Hold' substates - Add third level 'Suspended' substate inside each 'Hold' substate - Clearly separate 'Finished', 'Failed' and 'Cancelled' states - Add an 'Automatic Resubmission' transition to the 'Submitted' state only from the 'Failed' state (PNG drawing of the Small Diagram) Etienne URBAH - 07/14/2009 Draft
Version 19 v6: Group 'Hold-*' substates inside second level 'Hold' substates - Add third level 'Suspended' substate inside each 'Hold' substate - Clearly separate 'Finished', 'Failed' and 'Cancelled' states - Add an 'Automatic Resubmission' transition to the 'Submitted' state only from the 'Failed' state (XMI file readable by any UML tool) Etienne URBAH - 07/14/2009 Draft
Version 18 v6: Group 'Hold-*' substates inside second level 'Hold' substates - Add third level 'Suspended' substate inside each 'Hold' substate - Clearly separate 'Finished', 'Failed' and 'Cancelled' states - Add an 'Automatic Resubmission' transition to the 'Submitted' state only from the 'Failed' state (ZARGO file created by ArgoUML) Etienne URBAH - 07/14/2009 Draft
Version 17 v5: Move 'Hold' substates inside standard states - Create substates inside a global 'Finished' state (PNG drawing of the Big Diagram) Etienne URBAH - 07/01/2009 Draft
Version 16 v5: Move 'Hold' substates inside standard states - Create substates inside a global 'Finished' state (PNG drawing of the Medium Diagram) Etienne URBAH - 07/01/2009 Draft
Version 15 Move 'Hold' substates inside standard states - Create substates inside a global 'Finished' state (XMI file readable by any UML tool) Etienne URBAH - 07/01/2009 Draft
Version 14 v5: Move 'Hold' substates inside standard states - Create substates inside a global 'Finished' state (ZARGO file created by ArgoUML) Etienne URBAH - 07/01/2009 Draft
Version 13 v4: Define detailed internal states (PNG drawing of the Big Diagram) Etienne URBAH - 06/30/2009 Draft
Version 12 v4: Define detailed internal states (PNG drawing of the Medium Diagram) Etienne URBAH - 06/30/2009 Draft
Version 11 v4: Define detailed internal states (XMI file readable by any UML tool - Attention : All states and transitions belong to the Medium Model, but detailed internal states are shown only in the Big Diagram) Etienne URBAH - 06/30/2009 Draft
Version 10 v4: Define detailed internal states (ZARGO file created by ArgoUML - Attention : All states and transitions belong to the Medium Model, but detailed internal states are shown only in the Big Diagram) Etienne URBAH - 06/30/2009 Draft
Version 9 v3: Important internal states are exposed (PNG drawing) Etienne URBAH - 06/11/2009 Draft
Version 8 v3: Important internal states are exposed (XMI file readable by any UML tool) Etienne URBAH - 06/11/2009 Draft
Version 7 v3: Important internal states are exposed (ZARGO file created by ArgoUML) Etienne URBAH - 06/11/2009 Draft
Version 6 v2: PNG drawing Etienne URBAH - 05/27/2009 Draft
Version 5 v2: XMI file readable by any UML tool Etienne URBAH - 05/27/2009 Draft
Version 4 v2: ZARGO file created by ArgoUML Etienne URBAH - 05/27/2009 Draft
Version 3 Version 1 : PNG drawing Etienne URBAH - 05/27/2009 Draft
Version 2 Version 1 : XMI file readable by any UML tool Etienne URBAH - 05/27/2009 Draft
Version 1 Version 1 : ZARGO file created by ArgoUML Etienne URBAH - 05/27/2009 Draft



The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/sfmain/do/go/doc15655?nav=1&selectedTab=versions at Sun, 06 Nov 2022 11:27:01 GMT