Hi Paul,
> US-CMS don't use space tokens, so that will likely account for some of the
> sites that don't publish any space-tokens.
>
currently only atlas is using space tokens. All the other VOs (LHC
flavoured or not) are not using them. The VOs that don't use space
tokens are in a common space. Currently the way that is advertise is the
total common space is assigned to each VO which leads to obvious double
counting. The problem here is how to avoid this double counting.
> This is sadly true, but only because some sites are not yet adhering to the
> Installed Capacity document.
>
most site in the UK are using DPM and the info system coming with.
cheers
alessandra
> [...]
>
>> general way to get space usage for stuff that does not advertise iteself
>> in spacetokens.
>>
>
> The general method for determining storage usage per VO is with the installed-
> capacity property. See the above document for the details but, in brief, one
> should look for the GlueSACapability that matches InstalledOnlineCapacity (and
> InstalledNearlineCapacity). All SA objects should have one (again, feel free
> to ticket any site that publishes a SA without an InstalledOnlineCapacity
> attribute).
>
> An InstalledOnlineCapacity of zero means that SA must not be included in any
> space accounting. The remaining SAs (those with non-zero
> InstalledOnlineCapacity) form a covering set of the storage in the SE.
>
> You can take InstalledOnlineCapacity (IOC) to mean the total size of the SA,
> (GlueSA)TotalOnlineSize to be the total available size that is currently
> available, (GlueSA)UsedOnlineSize as the amount that is currently being used.
>
> In general the following relationships hold:
>
> IOC >= TotalOnlineSize >= UsedOnlineSize
> TotalOnlineSize >= FreeOnlineSize
> TotalOnlineSize = UsedOnlineSize + FreeOnlineSize
>
> Most SAs will have an IOC with the same value as TotalOnlineSize. They differ
> only when some of the underlying hardware is currently broken or off-line.
>
> 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.
>
> The accounting should be against the VOs listed in the SA object's ACBR
> attributes: if there's more than one VO then that SA is shared between those
> VOs. There's no definition on how to do this: a simple (naive?) approach would
> be to divide the SA equally between the listed VOs; however, if one VO is
> DTEAM and the other is ATLAS then this will likely under-report storage for
> ATLAS.
>
> HTH,
>
> Paul.
>
--
The most effective way to do it, is to do it. (Amelia Earhart)
Northgrid Tier2 Technical Coordinator
http://www.hep.manchester.ac.uk/computing/tier2
|