Document Details (Active Version)
Document Name: PGI Single Job State Model - Textual description Document ID: doc15697 Description: Textual description of the PGI Single Job State Model designed with UML at http://forge.gridforum.org/sf/go/doc15655?nav=1 For each Job State, this textual description explains precisely : - why and how a job goes in and out of the state, - if notifications are sent to the User (if yes, describe the notification content), - which resources are decided by the Execution Service for the Job but not yet allocated, which are really allocated, and which are already deallocated. 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:50 PM EDT	Status: Draft Current Version: 10 Size: 22.78 KB Lock:  Unlocked

	Versions		Associations		Review

	Active	Version	Version Comment	Review	Created By	Status
		Version 10	Following today's PGI session at OGF33, rename 'Submitted' as 'Pending' and 'Delegated' as 'Processing'.		Etienne URBAH - 09/21/2011	Draft
		Version 9	Take into account that the Execution Service may be unable to provide one or both : - Notifications, - Output Sandboxes.		Etienne URBAH - 02/04/2010	Draft
		Version 8	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.		Etienne URBAH - 02/03/2010	Draft
		Version 7	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.		Etienne URBAH - 12/17/2009	Draft
		Version 6	- 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.		Etienne URBAH - 10/02/2009	Draft
		Version 5	Write down that 'Cancellation' and 'Failure' can happen in any substate - Mention Time-out inside 'Delegated:Hold'		Etienne URBAH - 07/28/2009	Draft
		Version 4	Scope is Single Jobs only. This excludes Collection Jobs, Parameter Sweep Jobs, DAG Jobs, ...		Etienne URBAH - 07/28/2009	Draft
		Version 3	- 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"		Etienne URBAH - 07/14/2009	Draft
		Version 2	Storage resources which are necessary for Stage-out must be allocated at the beginning of the 'Delegated' state.		Etienne URBAH - 06/30/2009	Draft
		Version 1	To be thoroughly reviewed and criticized.		Etienne URBAH - 06/29/2009	Draft

Return     Open Document     < Previous     Next >