> I hope the sum of the six VOs equals the real total :)
it is not guarantueed. In my case I would publish 500GB for each VO but
they are really only 500GB. As I suspect that is the case in sheffield
for any VO that is not atlas.
cheers
alessandra
On Fri, 24 Jun 2005, Philip Clark wrote:
> Jamie Ferguson <[log in to unmask]> writes:
>
>> Hi Alessandra, Phil,
>>
>> Ive looked into this and you are right. Most sites have a block of storage
>> hat they offer to everyone. Hence a command such as
>> ldapsearch -LLL -x -h lcgse0.shef.ac.uk -p 2135 -b "mds-vo-name=local,
>> o=grid" "GlueSAAccessControlBaseRule=dteam" GlueSAStateAvailableSpace
>> GlueSAStateUsedSpace
>> shows all the storage available and used in total.
>>
>> However some sites (Sheffield obviously one of them) divide up their
>> storage on offer per VO.
>> I shall amend some code and total up the Sheffield amount.
>>
>> Phil - Its just a case of querying the info system for each VO (6 of them)
>> each time changing the GlueSAAccessControlBaseRule variablee.g. for atlas
>> ldapsearch -LLL -x -h lcgse0.shef.ac.uk -p 2135 -b "mds-vo-name=local,
>> o=grid" "GlueSAAccessControlBaseRule=atlas" GlueSAStateAvailableSpace
>> GlueSAStateUsedSpace
>> Let me know if there are any other errors detected, it would be appreciated.
>> Cheers,
>> Jamie.
>
> Cheers Jamie,
>
> Lets do this, it might be a while before sites get the new
> schema. More lovely perl for you :)
>
>
> -Phil
>
--
********************************************
* Dr Alessandra Forti *
* Technical Coordinator - NorthGrid Tier2 *
* http://www.hep.man.ac.uk/u/aforti *
********************************************
|