[glue-wg] ATLAS, GLUE and JSON

[Navarro, JP]

My impression looking at the sample JSON documents was also that the information ATLAS wants to publish easily maps to GLUE2.

XSEDE is willing to assist in enhancing our open source implementation with these new storage entities by:
- giving a teleconference presentation developers and system administrators on the “ipf-xsede” package
- responding to e-mail from other developers who are enhancing it
- conducting independent testing of contributions/enhancements
- helping produce new releases and packages

We are also willing to rename the product from “ipf-xsede” to “ipf” (which stands for "information publishing framework") or ipf-<whatever> if someone can think of a better <whatever>.

Regards,

JP

> On Oct 15, 2016, at 3:17 AM, stephen.burke at stfc.ac.uk wrote:
> 
> glue-wg [mailto:glue-wg-bounces at ogf.org] On Behalf Of Navarro, JP said:
>> Within this framework they could publish their storage dump (capacity_id) entries as abstract services with
>> each of the paths as endpoints.
> 
> This information would use StorageShareCapacity, and perhaps the parent StorageShare. At a quick look the information is generally similar, although some things, e.g. number of files, would need to be OtherInfo/Extension.
> 
> Stephen
> 

-------------- 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/20161017/4e1922c3/attachment.pgp>