Munich meeting on 2010-03-19

• Propose requirement with title  'An easy way of launching applications or pre-configured /pre-installed software w/o specifying location details. The exposure of these installed/pre-configured ones should be exposed as well as part of the resource description.'

Etienne Urbah's position on 2010-04-08

• I understand this simply as a requirement for usage of Application Repositories
• GLUE 2.0 already addresses this with the 'ApplicationEnvironment' entity
• JSDL already provides the 'Application' element with the 'POSIXApplication' element extension, and has to be extended according to GLUE, for example with a 'RepositoryApplication' element in order to really implement this requirement
• An Execution Service is able to use an Application Repository only after :
  - This Application Repository has been created, and publishes the list of its Applications according to GLUE - JSDL has been extended according to GLUE so that a client is able to easily require an Application stored inside a Repository
• For clarity, I suggest to change the original title to
  'There MAY exist Application Repositories containing applications or pre-configured / pre-installed software, and publishing them according to GLUE.
  - JSDL SHOULD be extended according to GLUE so that a client is able to easily require an Application stored inside a Repository w/o specifying location details.
  - The Execution Service SHOULD then honor Job Descriptions referencing an Application stored inside a Repository.
  Specifications of the Execution Service SHOULD describe only how it retrieves the Application files from the Application Repository
  (but MUST NOT try to address ALL the aspects and implications of Application Repositories, in particular queries and rights to store Applications)'
• If there is agreement on the new title, and on submission in parallel to the JSDL working group, I vote FOR this requirement.

Morris, Balazs and Etienne on 2010-04-21

• Source = GIN
• Spreadsheet ID = 34

Amsterdam meeting on 2010-04-29

• Merge AR2 with this requirement
• Source = GIN, NSF 08-571
• Change title to  'An easy way of launching applications or pre-configured /pre-installed software w/o specifying location details.
  Installed/pre-configured ones should be exposed as well as part of the resource description.
  The available software should be exposed through the service and in turn be requestable for resource/applications statements in JSDL.
  E.g. extending the JSDL with "pre-configured sw pieces" and/or "software libraries", e.g. global namespace of this applications might be beneficial as well. , etc.'
• Agreed YES

Etienne Urbah's position on 2010-05-07

• The title has been changed WITHOUT studying my suggestion dated 2010-04-08, and is still too loosely formulated
• So, for clarity, I suggest again following improved title :
  'There MAY exist Application Repositories containing applications or pre-configured / pre-installed software, and publishing them according to GLUE.
  - JSDL SHOULD be extended according to GLUE so that a client is able to easily require an Application stored inside a Repository w/o specifying location details.
  - The Execution Service SHOULD then honor Job Descriptions referencing an Application stored inside a Repository.
  Specifications of the Execution Service SHOULD describe only how it retrieves the Application files from the Application Repository
  (but MUST NOT try to address ALL the aspects and implications of Application Repositories, in particular queries and rights to store Applications)'