This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.pgi-wg/wiki/ReqNF13 at Fri, 04 Nov 2022 17:47:35 GMT SourceForge : View Wiki Page: ReqNF13

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Wiki Pages Project: pgi-wg     Wiki > ReqNF13 > View Wiki Page
wiki2258: ReqNF13

Req. Nb ID Description Source Areas Dependencies Status Date
NF13 160 Execution Service MUST NOT try to provide ALL grid functionalities, but MUST have a well defined scope, and MUST work together with other grid services :  Security,  Accounting,  Data (Storage, Movement, Catalog, ...),  perhaps Information,  Logging and Bookkeeping Etienne Urbah Reuse Specs, Cost Conflicts with NF9 Agreed YES 2010-05-20

Etienne Urbah on 2003-03-23

  • Propose this requirement with title
    'Execution Service MUST NOT be a mammooth trying to provide ALL grid functionalities, but MUST work together with other grid services :  Security,  Accounting,  Data (Storage, Movement, Catalog, ...),  perhaps Information,  Logging and Bookkeeping'

Etienne Urbah's position on 2010-04-07

  • Inside computing grids, there already are separate services
  • The principle is 'divide and conquer' :  Each service focuses on one goal and performs it correctly
  • More deeply into the foundations :  Inside OGF, our work of defining the CONTENT of each service (which can be improved later) is less important than our work of capturing the DEPENDENCIES between services, and then defining the minimum required INTERFACES between services   (In particular, dependency graphs provided by David Wallom are very useful, and MUST be kept up to date and published on the OGF web site)
    This task goes well beyond Execution Service, and probably belongs to OGSA
  • Anyway, for the Execution Service : In order to permit success, specifications MUST focus on a target as narrow as possible, and delegate as many tasks as possible to other services
  • So I vote FOR this requirement

Morris, Balazs and Etienne on 2010-04-27

  • Dropped, because we can not make assumptions on architectures

Etienne Urbah's position on 2010-04-28

  • This does NOT make assumptions on architectures, but requires that the architecture is NOT too monolithic
  • Re-propose this requirement with following improved title :
    'Execution Service MUST NOT try to provide ALL grid functionalities, but MUST have a well defined scope, and MUST work together with other grid services :  Security,  Accounting,  Data (Storage, Movement, Catalog, ...),  perhaps Information,  Logging and Bookkeeping'
  • Change the requirement status from 'Rejected (Bad prerequisite on Architecture)' to 'Re-proposed'

Amsterdam meeting on 2010-04-28

  • Spreadsheet ID = 160
  • Open  (still unclear)

PGI telcon on 2010-05-20

  • Execution Service should be a well focused service (additional figures in the input document section)
  • Agreed YES
 



Versions Associations Attachments Back Links  
Version Version Comment Created By
Version 12 Etienne URBAH - 10/21/2010
Version 11 ! PGI telcon on 2010-05-20 * Execution Service should be a well focused service (additional figures in the input document section) * Agreed YES Etienne URBAH - 10/21/2010
Version 10 ! PGI telcon on 2010-05-20 * Agreed YES Etienne URBAH - 05/20/2010
Version 9 Still unclear Etienne URBAH - 05/05/2010
Version 8 ! Amsterdam meeting on 2010-04-28 * Spreadsheet ID = 160 * Open (clear, but NO agreement found yet) Etienne URBAH - 05/04/2010
Version 7 Etienne URBAH - 04/29/2010
Version 6 Etienne URBAH - 04/28/2010
Version 5 !Etienne Urbah's position on 2010-04-28 * Original title of this requirement dated 2010-03-23 was :\\ 'Execution Service MUST NOT be a mammooth trying to provide ALL grid functionalities, but MUST work together with other grid services :  Security,  Accounting,  Data (Storage, Movement, Catalog, ...),  perhaps Information,  Logging and Bookkeeping' * Re-propose this requirement with following improved title :\\ 'Execution Service MUST NOT try to provide ALL grid functionalities, but MUST have a well defined scope, and MUST work together with other grid services :  Security,  Accounting,  Data (Storage, Movement, Catalog, ...),  perhaps Information,  Logging and Bookkeeping' * Change the requirement status from 'Rejected (Bad prerequisite on Architecture)' to 'Re-proposed' Etienne URBAH - 04/28/2010
Version 4 Morris Riedel - 04/27/2010
Version 3 Move reference to non-agreed Information Service to the 'perhaps' part Etienne URBAH - 04/21/2010
Version 2 Etienne URBAH - 04/07/2010
Version 1 Etienne URBAH - 04/07/2010



The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.pgi-wg/wiki/ReqNF13 at Fri, 04 Nov 2022 17:47:42 GMT