OGF21, Seattle
Wednesday, October 17th, 2007
SAGA Session #2 -- Service and Resource Discovery
-------------------------------------------------

Part I: Service Discovery
-------------------------

  - Notetaker: AM

  - SF walks audience through the document proposal.

  - discussion of Glue 1.3 versus Glue 2.0
  - SF: they different, but essential attribs are present.
  - SF: only different is service self reference, we are 
    trying to get that back in.

  - AM: shouldn't there be a proper reference to Glue?
  - SF: yep, probably should, we add that (TODO)

  - AM: is there a way to how to query for default VOs 
        (e.g. take the session contexts' VOs)
  - SF: maybe, we will think of something... (TODO)

  - ??: results for non authorized backends are silently discarded?
  - SF: yes

  - AM: question about value definitions, e.g. for 'type == RB' versus 
       'type = Resource Broker'
  - SF: type values are not defined by GLUE, use '*' to look around 
        what is there.


  - some discussion about the current C++ implementation, adaptor
    selection, and the ability combine results from multiple adaptors
  - AM/SJ will raise that topic with the SAGA C++ developers
    - SF: want to have control over adaptor selection
    - AM: shortcut: exception 'TryAgain' and store results in CPI
          state?

  - summary:
    - Steven to edit according to comments (TODO)
    - after that, submit to editor for public comment (TODO)


Part II: Resource Discovery
---------------------------

  - Notetaker: TK

  - Q: what covers resource discovery in use cases?
  - A: discover compute resources
    
  - Q: use case details? what do people want? through a service?
  - A: basically only finding hostnames at the moment.
    
  - Q: qhat is the information model?
  - Q: what is the query language? sql? xpath?
  - Q: could we use an extension of the advert service interface?
    
  - GL: cog uses condor matchmaking
    
  - ??: wsrf has discovery mechanism built in
    
  - SJ: go back and collect use cases!
    
  - SF: look at the glue use cases! 
    TODO: Steve searches references
    DONE: https://forge.gridforum.org/sf/go/doc14621?nav=1
    
  - GL: gridway must have an api for res. discovery
    TODO: Andre to check
    
  - ??: express the glue schema as classads?
  - ?? just pass strings? would that bind to certain providers 
    (e.g., SQL vs. MDS)?

  - Summary
    no conclusions on open questions, first check out the mentioned
    use cases.


SF: Steve Fisher
AM: Andre Merzky
SJ: Shantenu Jha
TK: Thilo Kielmann
GK: Gregor von Laszewski
??: can't remember who