Jensen, J (Jens) wrote:
> 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!
>
There _is_ a GGUS ticket filed against these tests isn't there? If not,
why not?
Chris
|