Paul Millar wrote:
> In case this isn't obvious: a child VOInfo object advertises the ability of
> some end-user group (usually a VO) to *write* into the storage capacity
> represented by an SA.
IMHO nothing is obvious, because the GLUE spec says nothing about
writing. It is more a question about how WLCG reinterprets the GLUE
spec. But the world is bigger than WLCG, contrary to popular (at least
WLCG's) belief.
> An SA can have zero or more VOInfo objects; an SA with
> zero child VOInfo objects represents some capacity that people cannot write
> into (e.g., staging space for accessing files from tape).
This is another WLCG convention, but at least a documented one :-)
> GlueSAStateAvailableSpace is marked deprecated in Glue v1.3, but is required
> in Installed Capacity. For the time being, sites MUST (RFC-2119 again)
> publish this attribute, but this may change in the future.
True, but the tests critically depend on it!
>> Unfortunately, however there seems to be no reliable recipe of which
>> variables (or method srm v. bdii) to use for all sites and all VOs.
>
> This is sadly true, but only because some sites are not yet adhering to the
> Installed Capacity document.
Not just that. Also because the tests - and lcg-utils - depend on
undocumented "features" and deprecated ways of publishing.
> TotalOnlineSize = UsedOnlineSize + FreeOnlineSize
This one is the InstalledCapacity definition, so by construction at
least one of these numbers is a lie :-)
> ReservedOnlineSize is roughly like IOC, but has some more complex semantics,
> for backward comparability with existing clients. I'd recommend ignoring
> ReservedOnlineSize and use IOC.
Just for the record, CASTOR currently published ReservedOnlineSize but
not IOC. I will fix this, eventually.
Cheers
--jens
|