Greig A Cowan wrote on 13 June 2006 14:16:
>
>> I agree. My point (if any) was that implementing the space API is a
>> way to implement per-VO-quotas, plus it gives you some sort of
>> advertised management of the space it's managing (ie tapeXdiskY or
>> whatever it was). If experiments have asked for guaranteed
>> reservations, then we can use that as a quota facility.
>
> So you are saying that experiments could ask for long-lived space tokens
> in order to guarantee themselves space? I was thinking that the space
> token would only be a short lived entity that would expire once the
> request it was associated with had completed (i.e. the file had been
> copied into the space).
>
I understood from the new SRM 2.2 space model that that was how it
worked: the VO manager talks to the admin, by phone possibly, and asks
for space. (Caveat: just based on the summary Graeme gave last Wed.)
If space is requested via the interface then it can be more dynamic.
So we may have either, or both, types of space, depending on the
implementation. DPM should support the dynamic stuff, whereas CASTOR
will probably only support the "phone space".
Cheers.
--jens
|