Balazs, Morris, Luigi, Johannes and all, Inside the 'Requirements Wiki' containing Requirements tables at http://forge.gridforum.org/sf/wiki/do/viewPage/projects.pgi-wg/wiki/Requirem... : As of now, re-proposed and brand new requirements requirements are : - 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 - IS14 In order to prevent overloading the Execution Service (which has performance requirements for Activity Management), the Information functionality SHOULD be separated from the Execution Service - Ac0 In order to permit efficient Accounting, a grid infrastructure MUST provide an Accounting functionality (without real time requirements) which consolidates Accounting records at the grid level from various systems, securely keeps Accounting records even after Activities have finished, implements complex accounting queries, and supports the corresponding CPU load - Ac1 In order to prevent overloading the Execution Service (which has performance requirements for Activity Management), the Accounting functionality MUST be separated from the Execution Service - JM6.11 For all requests concerning Activities, the Execution Service functionality MUST accept, as input parameter, 1 Activity ID - JM11 The Execution Service MAY provide its functionalities to Clients through various protocols (RPC, Corba, ActiveMQ, ...), but MUST provide them to Clients through a Web Service As of now, requirements needing clarification are : - NF8 Clean specifications and interface definitions, don't keep obsolete and never used elements (by whom?) - NF15 Need to support high availability and reliability - NF16 Single global namespace for resources of all kind (storage devices, compute device), ... - NF17 Easier usage to get more users involved. How does it effects PGI?! A general rule like global namespaces (for example: path) - NF18 Potential re-use of PGI portTypes by other services (for example: information portType) 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 -----------------------------------------------------