[glue-wg] ATLAS, GLUE and JSON

[Navarro, JP]

Paul,

We have a lot of distributed knowledge and experience in the glue-wg. How about if the join the glue-wg list and start the discussion there?  If they could post a summary of their requirements and examples of their storage documents I’m sure several people will respond with ideas on whether they could leverage GLUE, or where GLUE may need to grow to satisfy their needs.

JP


> On Oct 12, 2016, at 5:25 PM, Paul Millar <paul.millar at desy.de> wrote:
> 
> Hi everyone,
> 
> <background>
> 
> A little while ago, the WLCG VO ATLAS started investigating how to do storage accounting in a platform neutral fashion (i.e., not depending on SRM).
> 
> Their idea was that a site would "somehow" ensure that their storage system always has a file containing the necessary information.  The file would be stored in a standard location.  ATLAS could then read this file using whichever protocol is easiest.
> 
> The plan was for this file would be encoded as JSON.  They also put together a rough description of how this file should look like.
> 
> I suggested that they investigate GLUE 2 and the GLUE-JSON binding, rather than coming up with their own proprietary solution.
> 
> </background>
> 
> So, ATLAS are asking for some information:
> 
>  o	people with whom they can discuss how to use
> 	GLUE2 and GLUE-JSON.
> 
>  o	tools that parse GLUE-JSON.  I guess this would be mostly
> 	from XSEDE guys.
> 
> So, does anyone want to help them evaluate GLUE 2?
> 
> Cheers,
> 
> Paul.
> _______________________________________________
> glue-wg mailing list
> glue-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/glue-wg

-------------- 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/20161013/282dec08/attachment.pgp>