Etienne Urbah's position on 2010-04-19

• The Execution Service MUST provide appropriate accounting data to the Accounting functionality
• But processing of Accounting requests of Clients requires to :
  - Consolidate Accounting data at the grid level from all other grid services
  - Securely keep accounting data, which MUST persist after any Activity has finished
  - Implement complex accounting queries
  - Support the corresponding CPU load
• The Execution Service already has to manage the complexity of Activity Management during the lifetime of each Activitiy
• Therefore, processing of Accounting requests of Clients MUST NOT be implemented by the Execution Service, but by a completely separate Accounting Service
• I strongly vote FOR this requirement

Morris, Balazs and Etienne on 2010-04-21

• This requirement was proposed on 2010-03-17
• dropped (rejected), because it assumes too much of a non-agreed architecture

Etienne Urbah's retry on 2010-04-23

• Original title of this requirement was  'The Accounting Service MUST be completely separate from the Execution Service.  Therefore specifications will NOT take into account Client requests concerning Accounting.'
• In order to remove the bad prerequisite, I suggest following improved title :
  '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'
• Change the requirement status from 'Rejected (Bad prerequisite on Information Service)' to 'Re-proposed'

PGI telcon on 2010-05-20

• Spreadsheet ID = 173
• Agreed YES