Etienne Urbah on 2010-04-13

• Propose requirement with title  'If functions provided by one Endpoint have different GLUE properties, then the Endpoint MUST be split in different Endpoints, each one having homogeneous properties'

Etienne Urbah's position on 2010-04-13

• The GLUE model clearly establishes the concept of Endpoint, that is a network location which a Client can contact to access functionalities
• The GLUE model permits to associate any number of Endpoints to a set of one or several Shares
• So, if functions provided by one Endpoint have different GLUE properties (such as vector limits), the GLUE model makes it easy to split the Endpoint into different Endpoints (pointing to the same set of Shares), each one having homogeneous GLUE properties (such as vector limits), and this split MUST be performed
• I vote FOR this requirement

Morris, Balazs and Etienne on 2010-04-21

• Spreadsheet ID = 3

Amsterdam meeting on 2010-04-28

• At the end of the title, add  'Heterogeneous resources can NOT be described with one GLUE Endpoint'
• Open  (clear, but NO agreement found yet)

Chicago meeting on 2010-06-22

• Change title to 'A GLUE Computing Endpoint can describe only 1 Job submission interface (for example BES).
  Job submission interfaces which have different properties (for example vector limits) MUST have different GLUE Computing Endpoints'
• Agreed YES