Documents / gridforge / Input Documents / Execution Service / State Model / PGI Single Job State Model - Textual description
Revisions
2011-09-21 12:50:05 by Redmine Admin
PGI Single Job State Model - Textual description
gridforge/Input Documents/Execution Service/State Model/PGI-Single-Job-State-Model.txt
Following today's PGI session at OGF33, rename 'Submitted' as 'Pending' and 'Delegated' as 'Processing'.
10.0
None
text/plain
22.8 kB
2010-02-04 09:09:30 by Redmine Admin
PGI Single Job State Model - Textual description
gridforge/Input Documents/Execution Service/State Model/PGI-Single-Job-State-Model.txt
Take into account that the Execution Service may be unable to provide one or both :
- Notifications,
- Output Sandboxes.
9.0
None
text/plain
22.8 kB
2010-02-03 13:17:08 by Redmine Admin
PGI Single Job State Model - Textual description
gridforge/Input Documents/Execution Service/State Model/PGI-Single-Job-State-Model.txt
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.
8.0
None
text/plain
22.6 kB
2009-12-17 16:30:36 by Redmine Admin
PGI Single Job State Model - Textual description
gridforge/Input Documents/Execution Service/State Model/PGI-Single-Job-State-Model.txt
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.
7.0
None
text/plain
19.2 kB
2009-10-02 09:59:21 by Redmine Admin
PGI Single Job State Model - Textual description
gridforge/Input Documents/Execution Service/State Model/PGI-Single-Job-State-Model.txt
- 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.
6.0
None
text/plain
18 kB
2009-07-28 15:09:47 by Redmine Admin
PGI Single Job State Model - Textual description
gridforge/Input Documents/Execution Service/State Model/PGI-Single-Job-State-Model.txt
Write down that 'Cancellation' and 'Failure' can happen in any substate - Mention Time-out inside 'Delegated:Hold'
5.0
None
text/plain
17.5 kB
2009-07-28 14:27:23 by Redmine Admin
PGI Single Job State Model - Textual description
gridforge/Input Documents/Execution Service/State Model/PGI-Single-Job-State-Model.txt
Scope is Single Jobs only. This excludes Collection Jobs, Parameter Sweep Jobs, DAG Jobs, ...
4.0
None
text/plain
17.1 kB
2009-07-14 12:01:53 by Redmine Admin
PGI Single Job State Model - Textual description
gridforge/Input Documents/Execution Service/State Model/PGI-Job-State-Model.txt
- Change first level 'Hold' states as second level substates
- Add third level 'Suspended' substates inside 'Hold' substates
- Clearly separate 'Finished', 'Failed' and 'Cancelled' states
- Add an 'Automatic Resubmission' transition to the 'Submitted' state only from the 'Failed' state"
3.0
None
text/plain
16.9 kB
2009-06-30 08:57:21 by Redmine Admin
PGI Single Job State Model - Textual description
gridforge/Input Documents/Execution Service/State Model/PGI-Job-State-Model.txt
Storage resources which are necessary for Stage-out must be allocated at the beginning of the 'Delegated' state.
2.0
None
text/plain
18 kB
2009-06-29 15:36:07 by Redmine Admin
PGI Single Job State Model - Textual description
gridforge/Input Documents/Execution Service/State Model/PGI-Job-State-Model.txt
To be thoroughly reviewed and criticized.
1.0
None
text/plain
18 kB
(1-10/10)