Etienne Urbah on 2010-03-26

• Propose requirement with title  'For all requests, the Logging and Bookkeeping functionality MUST accept, as input parameter, complex queries on Activities expressed according to the GLUE2 model without explicit specification of the Activity IDs.  The Logging and Bookkeeping functionality MAY support multiple query languages in addition to the mandatory one.'

Etienne Urbah's position on 2010-04-09

• There is an absolute need to be able to query Activities by :
• The grid identity of the Activity submitter, in particular :
  - For all grid users :    What is the status of all the Activities which I submitted last week ?
  - For a VO manager :  Which grid resources were used by Activities submitted by one precise member of my VO ?
• The activity Status, in particular :
  - For all grid users :    What are the grid-level failure messages associated to failed Activities which I submitted last week, sorted by frequency ?
  - For a VO manager :  What are the top Applications, Grid resources, Grid-level failure messages, ... associated to failed Activities submitted by my VO ?
• This introduces complexity inside the grid component(s) implementing the Logging and Bookkeeping functionality, so that this requirement is NOT likely to be achievable by a grid service having already performance requirements
• Nevertheless, I vote FOR this requirement

Morris, Balazs and Etienne on 2010-04-21

• dropped (premature), because too implementation specific already

Etienne Urbah's retry on 2010-05-07

• This requirement can be compared to requirement JM6.15, which has been accepted for discussion
• Therefore, re-propose this requirement
• Change the requirement status from 'Premature (Detailed specification)' to 'Re-proposed'