On Thursday 28 Jul 2005 17:35, Dr D J Colling wrote:
> Thanks all,
>
> So this works if I replace sfn with srm. Now, given this is part of a cms
> MC production script and that we have a mixture of srm and and classic SEs
> out there, is there any automatic way to tell which is which?
You can try querying the BDII. Classic SEs are "GlueSEType: disk" and SRM SEs
should be "GlueSEType: srm_v1" (though the erroneous "srm" is I think also
lurking about):
# ldapsearch -LLL -H ldap://lxn1189.cern.ch:2170 -x -b \
'mds-vo-name=local,o=grid' 'GlueSEUniqueID=se1-gla.scotgrid.ac.uk' \
| grep GlueSEType
GlueSEType: disk
# ldapsearch -LLL -H ldap://lxn1189.cern.ch:2170 -x -b \
'mds-vo-name=local,o=grid' 'GlueSEUniqueID=srm.epcc.ed.ac.uk'\
| grep GlueSEType
GlueSEType: srm_v1
> In practise
> this is not a real problem as we specify which SE that it goes to, however
> I would still be interested to know if there any automated method
This needs to be published consistently - you shouldn't have to keep this
information yourself, although I suppose you can infer from the catalog entry
which SE type it is?
> or if we
> are just hope that all the non srm SEs just go away.
I think we hope this anyway ;-)
cheers
graeme
--
--------------------------------------------------------------------
Dr Graeme Stewart http://www.astro.gla.ac.uk/users/graeme/
GridPP DM Wiki http://www.physics.gla.ac.uk/gridpp/datamanagement/
|