On 20 Jun 2011, at 18:14, Peter Grandi wrote:
> On 20/06/11 14:44, Daniela Bauer wrote:
>
>>> change some details so "GlueCEUniqueID: ce01...." becomes
>>> "GlueCEUniqueID: cream02...".
>> How would yaim have ever heard of ce01 on cream02 ? It should make the
>> ldif files automatically.
>
> I had a look again at this and the overall issue is that in
> 'site-info.def' one cannot put a list as the value of 'CE_HOST',
> even if some recent pages talk about a new node type called
> 'glite-CLUSTER':
>
> http://glite.cern.ch/glite-CLUSTER/
> http://www.gridpp.ac.uk/deployment/users/Cluster-node.pdf
>
> The old-style technique that I have seen documented in some web
> page is to manually modify the 'CE_HOST' variable before running
> YAIM on a particular CE.
>
> But this page at DESY documents an alternative:
>
> http://grid.desy.de/install/glite.html
>> /opt/glite/yaim/bin/yaim -v -s /opt/misc/yaim/`hostname
> -s`-info.def -n lcg-CE -n TORQUE_utils
>
> Inspired by the latter I have decided to do something similar:
> to have 'site-info-ce01.def', ... 'site-info-cream02.def' where
> each contains something like:
>
> source "$GLITE_LOCATION/yaim/etc/site-info.def"
> CE_HOST=cream02.$MY_DOMAIN
>
site-info.def is (possibly was its been a while) just sourced as a shell script, so you can do things like
CURRENT_HOST=`hostname -f`
MY_DOMAIN=gridpp.rl.ac.uk
case ${CURRENT_HOST} in
lcgce01.gridpp.rl.ac.uk) CE_HOST=lcgce01.$MY_DOMAIN;;
lcgce02.gridpp.rl.ac.uk) CE_HOST=lcgce02.$MY_DOMAIN;;
lcgce08.gridpp.rl.ac.uk) CE_HOST=lcgce08.$MY_DOMAIN;;
*) CE_HOST=lcgce02.$MY_DOMAIN;;
esac
inside it.
yaim will also look for a host specific config file under nodes/<hostname> where nodes is a directory at the same path as your site-info.def.
Derek
|