[glue-wg] ATLAS, GLUE and JSON

[Navarro, JP]

Paul,

XSEDE’s implementation publishes these GLUE2 Entities:
  'ApplicationEnvironment’,
  'ApplicationHandle’,
  'AbstractService’,
  'Endpoint',
  'ComputingManager’,
  'ComputingShare’,
  ‘ComputingActivity',
  'ExecutionEnvironment’,
  ‘Location'

The only entities with storage relate information are AbstractService and Endpoint. XSEDE’s AbstractService and Endpoint information can be viewed here:

https://info1.dyn.xsede.org:443/wh1/glue2-db-api/v1/abstractservice/
https://info1.dyn.xsede.org:443/wh1/glue2-db-api/v1/endpoint/ <https://info1.dyn.xsede.org/wh1/glue2-db-api/v1/endpoint/>

Within this framework they could publish their storage dump (capacity_id) entries as abstract services with each of the paths as endpoints.  Attributes that XSEDE currently doesn’t support could be added if they exist in the GLUE2 model, and if not included in Extensions as specified by GLUE2.

JP

> On Oct 14, 2016, at 2:16 PM, Paul Millar <paul.millar at desy.de> wrote:
> 
> My reading of the situation is that they don't want to read all of GLUE2 and GLUE2-JSON binding documents and try to understand it all to evaluate whether GLUE2-JSON makes sense for them.
> 
> Instead, I believe they want to use us as consultants; in particular, they want some concrete GLUE2-JSON examples to look at.  Something like a template they can use.
> 
> The pre-GDB link includes some examples in their proprietary format:
> 
> https://indico.cern.ch/event/394833/#3-resource-reporting-proposal
> 
> Can we describe this information in GLUE2-JSON?
> 
>> Step 2 would then be to look at existing implementations, such as
>> XSEDE’s, and decide whether to extend that implementation with the
>> information they want, or to develop something new.  XSEDE is available
>> to discuss what it would take to add specific types of information if
>> they can identify what those are.
> 
> Yes, I explained (or tried to explain) that XSEDE's existing code-base might or might not be useful for them.
> 
>> Perhaps they could share documentation and examples on those files for
>> others to help with the above steps?
> 
> Examples of their proprietary format are available from within Alessandro's Pre-GDB presentation.
> 
> Cheers,
> 
> Paul.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/glue-wg/attachments/20161014/7c85efa8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.ogf.org/pipermail/glue-wg/attachments/20161014/7c85efa8/attachment.pgp>