[glue-wg] capabilities

[JP Navarro]

~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.teragrid.org-4.2.0/ranger.tacc.teragrid.org

The terms "Kit" and "Capability" are interchangeable.

JP
On Jul 8, 2009, at 5:47 AM, Burke, S (Stephen) wrote:

> glue-wg-bounces at ogf.org
>> [mailto:glue-wg-bounces at 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 at ogf.org
> http://www.ogf.org/mailman/listinfo/glue-wg