Morris, Balazs and Etienne on 2010-04-23

• Original title of this requirement dated 2010-03-20 was :
  'The Execution Service SHOULD accept vectors of simple Activities as input parameter for several operations.
  For example: creating more than one Activity by one WS call; changestate as well with vector. Activity status monitoring, cancelation of Activities, purge of Activities
  The Execution Service processes each vector element independently, and reports failure only for failed vector elements.
  Thus the vector operation does neither define a 'grouping of activities' nor 'transaction of activities'.
  Hence, the service satisfies each vector element as best as possible while failed independent vector elements will be reported in a fault as response to the vector operation.'
• Change title to :
  'The Execution Service SHOULD accept vectors of simple Activities as input parameter for several operations such as Create(), ChangeState(), ActivityStatus(), Cancel(), Purge() (implementation aspect longly discussed in Munich - worth to keep)'
• Source = Draft Spec
• Spreadsheet ID = 56

Amsterdam meeting on 2010-04-29

• vectors of simple Activities as input parameter --> bulk operations

Chicago meeting on 2010-06-22

• Improve title
• Agreed YES

PGI telcon on 2010-10-14

• Why --> major communities from HTC submit a high number of jobs (in vectors), EGI is an HTC infrastructure, therefore important, performance expectations are important
• Andrew: Vector just one example, but performance is what matters!
• Oxana: Not necessary, but bulk submission is important
• Andrew: parameter sweep another idea, but GENESIS not against