[glue-wg] Update from ATLAS evaluation of GLUE2

jens.jensen at stfc.ac.uk jens.jensen at stfc.ac.uk
Wed Jan 25 09:39:40 EST 2017


Say did anything else happen on this one? Any thoughts on Paul's proposal?

Thanks
--jens
________________________________________
From: glue-wg [glue-wg-bounces at ogf.org] on behalf of Paul Millar [paul.millar at desy.de]
Sent: 14 November 2016 11:10
To: glue-wg at ogf.org
Subject: [glue-wg] Update from ATLAS evaluation of GLUE2

Hi all,

Here's a update from ATLAS' evaluation of GLUE2.

The process is ongoing and not yet finalised.  ATLAS is currently
considering to take aspects of GLUE2 (trying to use the same attribute
names, for example) but at the moment they are considering a format that
would not be GLUE2 compliant.

The process has helped identify some sticking points, which I propose we
should address.

Here are two concrete proposals that would help ATLAS:

   P1.  add a StorageShare attribute that describes the number of
        files stored in this StorageShare.  This should
        be optional (mult: 0..1).

   P2.  adjust multiplicity of StorageShare#Path to 0..*

The other issue they identified was that StorageShare doesn't store
capacity information: that requires a whole new object (with IDs and
linkage).

Here's a concrete proposal (so people can disagree :-) on how we can fix
this:

   P3.  add the StorageShareCapacity usage metrics
        (TotalSize, FreeSize, UsedSize, ReservedSize) to
        StorageShare as optional attributes (mult: 0..1)

        These attributes MAY be used in situations where
        is clear which media is being used.  In such
        circumstances, the StorageShare SHOULD have at
        most one DataStore association.


   P4.  Rename StorageShareCapacity to DataStoreUsage,
        adding a required Association to a DataStore.

        This better reflects that StorageShareCapacity links
        a StorageShare to some corresponding hardware.

P1 and P2 are both rather trivial -- these should be fixed in GLUE v2.1.

P3 is also (technically) rather trivial -- if we want, this could go in
GLUE v2.1

P4 would not be backwards compatible, so we would have to be a little
careful how we roll it out.

Cheers,

Paul.


_______________________________________________
glue-wg mailing list
glue-wg at ogf.org
https://www.ogf.org/mailman/listinfo/glue-wg


More information about the glue-wg mailing list