Morris, Balazs, Luigi, Johannes and all, Concerning the 'Requirements Wiki' containing Requirements tables at http://forge.gridforum.org/sf/wiki/do/viewPage/projects.pgi-wg/wiki/Requirem... : Correcting my preceding mail, I have NOT re-proposed IS10. I have re-proposed following requirements with improved title : - IS2 Each Service MUST publish its properties (Name, Type, Endpoints, ...) and the properties of its Endpoints in conformance with GLUE recommendations - IS8 For not yet finished Activities, the Information functionality MUST accept requests querying the Activity Status, and MUST return this Status with different levels of verbosity (basic, detailed, more detailed) - IS9 For already finished Activities, the Information functionality SHOULD accept requests querying the Activity Status, but MAY return an error - IS13 For requests querying Activity Status, the Information functionality SHOULD support query languages - Ac1 The global Accounting functionality consolidates Accounting data at the grid level, securely keeps accounting data as persistent, implements complex accounting queries, and support the corresponding CPU load. Therefore, those Accounting sub-functionalities MUST NOT be implemented by the Execution Service (which has performance requirements for Activity Management), but by a completely separate Accounting Service. 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 22/04/2010 20:19, Etienne URBAH wrote:
Morris, Balazs, Luigi, Johannes and all,
Concerning the 'Requirements Wiki' containing Requirements tables at http://forge.gridforum.org/sf/wiki/do/viewPage/projects.pgi-wg/wiki/Requirem... :
I have re-proposed following requirements with improved title :
- IS2 Each Service MUST publish its properties (Name, Type, Endpoints, ...) and the properties of its Endpoints in conformance with GLUE recommendations
- IS8 For not yet finished Activities, the Information functionality MUST accept requests querying the Activity Status, and MUST return this Status with different levels of verbosity (basic, detailed, more detailed)
- IS9 For already finished Activities, the Information functionality SHOULD accept requests querying the Activity Status, but MAY return an error
- IS10 For requests querying Activity Status, the Information functionality MUST accept, as input parameter, 1 Activity ID
- IS13 For requests querying Activity Status, the Information functionality SHOULD support query languages
- Ac1 The global Accounting functionality consolidates Accounting data at the grid level, securely keeps accounting data as persistent, implements complex accounting queries, and support the corresponding CPU load. Therefore, those Accounting sub-functionalities MUST NOT be implemented by the Execution Service (which has performance requirements for Activity Management), but by a completely separate Accounting Service.
Best regards.