Ah, I see. Interesting. Yes. TeraGrid capability kits are relatively high-level and not fine grained features. So, do OGSA, GLUE, and SAGA use this terminology consistently: High-level (kit) doesn't exist in OGSA, GLUE, or SAGA? Medium-level service Lower-level capabilities/features offered by services Lower-level endpoint(s) used to access service Are there other important entities in the hierarchy? You didn't mention the Reference Model. Does it also use the same terms? Seems like a Storage Element or Compute Element in GLUE terms approximates what a TeraGrid capability kit is, although we have capability kits that aren't storage or (remote) compute related. Thanks for the clarification, JP p.s. clarifying what we mean with terms is a useful aspect of OGF! On Jul 8, 2009, at 6:40 PM, Steve Fisher wrote:
JP,
I think this is different to the meaning of capability as used in OGSA, GLUE and SAGA. We see a capability as something that a service may have. It may be seen as a "feature" or literally what a service is capable of doing. A hammer is capable of driving nails but is also capable of holding down a pile of papers. A nail gun is also capable of driving nails. You example shows a capability as a set of related services - kit may be a better word for this concept.
Steve
2009/7/8 JP Navarro <navarro@mcs.anl.gov>:
~2 years ago in the TeraGrid we had to define a capability schema to address new requirements. I've been planning to present these requirements to the GLUE2 team hoping they would resonate with other grids and could be integrated into a new revision of GLUE2.
For TeraGrid, the relationships described below are true. A given Capability can include any number of Services (web and non-web). Services have a Type/implementation, Version, and a Name that differentiates identical services supporting different use cases.
For example, the "TeraGrid Data Movement Server" (a.k.a. the data-movement-server.teragrid.org capability) advertises the availability of GridFTP, RFT, and GSI OpenSSH SCP w/ HPN patches. This is what a deployed capability registration looks like:
http://info.teragrid.org/web-apps/html/kit-reg-v1/data-movement-servers.tera...
The terms "Kit" and "Capability" are interchangeable.
JP On Jul 8, 2009, at 5:47 AM, Burke, S (Stephen) wrote:
glue-wg-bounces@ogf.org
[mailto:glue-wg-bounces@ogf.org] On Behalf Of Wilson, AJ (Antony) said: Has anyone done any mapping of current services to capabilities?
Not that I'm aware of - if you want to do it, feel free :) Bear in mind that Services in glue 1 become Endpoints in glue 2, and a glue 2 Service is a bundle of Endpoints, so the mapping gets a bit more complicated. We haven't yet really addressed the question of defining glue 2 Service types, let alone capabilities.
Stephen -- Scanned by iCritical. _______________________________________________ glue-wg mailing list glue-wg@ogf.org http://www.ogf.org/mailman/listinfo/glue-wg
_______________________________________________ glue-wg mailing list glue-wg@ogf.org http://www.ogf.org/mailman/listinfo/glue-wg