Next job management teleconference wednesday may 13

Dear all, the next PGI teleconference will be held on wednesday may 13th at 16:00 CET (duration: 1 hour). Call-in details as follow: via Skype call +9900827049931906 (free of charge) ordinary phone numbers (local rates) with the 9931906 conference number: Austria 0820 401 15470 Belgium 0703 57 134 France 0826 109 071 Germany +49 (0) 180 500 9527 Switzerland 0848 560 397 Agenda: 1) Actual definition of the execution service interface according to the requirements discussed so far. As a skeleton to support discussion we have prepared this document: http://forge.gridforum.org/sf/go/doc15628?nav=1 In its current form, this is not a full specification document but rather a slightly more precise definition of the interface for the execution service. Moreover, at this time some operations are only listed but not defined. If anybody has different proposals for the execution service interface, please upload them into gridforge, so we can add further agenda items for discussing them. Moreno. -- Moreno Marzolla INFN Sezione di Padova, via Marzolo 8, 35131 PADOVA, Italy EMail: moreno.marzolla@pd.infn.it Phone: +39 049 8277103 WWW : http://www.dsi.unive.it/~marzolla Fax : +39 049 8756233

Moreno, Concerning the PGI Execution Service : Thank you very much for the 'Strawman_rendering' based on the 'Execution Service Strawman'. Management of multiple activities --------------------------------- I have found that the 'JSDL Parameter Sweep Job Extension' document has been submitted to OGF Editor for publication, is now ready to publish, and is available at http://forge.gridforum.org/sf/go/doc14595?nav=1 Please check that the PGI 'Execution Service Strawman' and the 'Strawman_rendering' documents are compatible with this JSDL document, and that there is NOT too much overlapping between the 2 ways (Operation and JSDL) to manage multiple activities. 'Strawman_rendering' document ----------------------------- Chapter 6.2.1 'CreateActivity' of 'ogsa-bes-v38.doc' available at http://forge.gridforum.org/sf/go/doc15062?nav=1 defines an 'UnsupportedFeatureFault' explicitly related to JSDL parsing. Therefore, for the 'CreateActivity' operation, I suggest to require the execution service to parse the job description. I consider 'purging' of activities as pure house cleaning of already terminated activities, to be performed AFTER any potential client request to terminate the activity (before its normal ending). So, I suggest to replace the boolean 'terminate' input parameter of the 'PurgeActivity' operation by a boolean 'purge' input parameter of the 'TerminateActivity' operation. More precisely : For the 'TerminateActivity' operation, I suggest to add : - a boolean 'purge' parameter specifying if the activity should be immediately purged after termination, - a 'Terminated but not purged' fault as possible return value. For the 'PurgeActivity' operation, I do suggest to suppress the boolean 'terminate' input parameter. Besides, I am sorry, but I will probably NOT be able to attend the next PGI job management teleconference. Best regards. ----------------------------------------------------- Etienne URBAH LAL, Univ Paris-Sud, IN2P3/CNRS Bat 200 91898 ORSAY France Tel: +33 1 64 46 84 87 Skype: etienne.urbah Mob: +33 6 22 30 53 27 mailto:urbah@lal.in2p3.fr ----------------------------------------------------- On Mon, 11 May 2009, Moreno Marzolla wrote:
Dear all,
the next PGI teleconference will be held on wednesday may 13th at 16:00 CET (duration: 1 hour).
Call-in details as follow: via Skype call +9900827049931906 (free of charge) ordinary phone numbers (local rates) with the 9931906 conference number:
Austria 0820 401 15470 Belgium 0703 57 134 France 0826 109 071 Germany +49 (0) 180 500 9527 Switzerland 0848 560 397
Agenda:
1) Actual definition of the execution service interface according to the requirements discussed so far. As a skeleton to support discussion we have prepared this document:
http://forge.gridforum.org/sf/go/doc15628?nav=1
In its current form, this is not a full specification document but rather a slightly more precise definition of the interface for the execution service. Moreover, at this time some operations are only listed but not defined.
If anybody has different proposals for the execution service interface, please upload them into gridforge, so we can add further agenda items for discussing them.
Moreno.
participants (2)
-
Etienne URBAH
-
Moreno Marzolla