> Also, I this method assumes that the dCache instance in question is
> running gsidcap, which is not always the case if you are using dCache. You
> can see this by querying some of the other sites that you know have
> dCache installed.
>
> Another handle on whether a site is running dCache or DPM can be obtained
> from the GlueSARoot path.
>
> ldapsearch -x -H ldap://site-bdii.pp.rl.ac.uk:2170 -b
> mds-vo-name=RALPP-LCG,o=grid |grep pnfs/
>
> ldapsearch -x -H ldap://ce.epcc.ed.ac.uk:2170 -b
> mds-vo-name=ScotGrid-Edinburgh,o=grid |grep dpm/
>
> Of course, the /pnfs and /dpm paths are only the defaults used by YAIM.
> Sites are able to use a different path so the absence of /pnfs from any
> site doesn't necessarily mean that it does not have a dCache instance.
The path method is the method I am using just now but the responses are
disappointing can be seen at
http://www.gridpp.ac.uk/storage/status/gridppDiscStatus.html in
the Storage Type column.
The question marks indicate a response from an SE/dpm/dcache instance but
there path does not correspond to the default (which is reasonable -
there is no gridpp law that states sites must use the default path). And
hyphens indicate no response whatsoever for the glueSARoot path.
As can be seen about 50% of responses are non-default making it
problematic monitoring classic SE/dpm/dcache storage levels. However I
shall implement the new method from Jens today, which shall hopefully
prove robust.
Cheers,
Jamie.
|