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.
> Alessandra Forti <[log in to unmask]> writes:
>
>> Hi Phil,
>>
>> if you go to the GIIS page you'll see that they do publish 2 TB.
>>
>> http://goc.grid.sinica.edu.tw/gstat/SHEFFIELD-LCG2/
>>
>> they might have put quotas on the system and this is why you see only
>> 700GB. Infact if I select atlas which is the main experiment it has
>> ~1.6TB
>
> Hi Alessandra,
>
> Thanks, this is just the feed back we need. We will investigate. Maybe
> we need a separate command for each VO? Can you think off a way to get
> the total ldap?
>
> -Phil
|