[ ... ]
>>> SITE_OTHER_EGEE_ROC="UK/I"
>> EGEE_ROC becomes EGI_NGI, but I'm not sure if the UK NGI
>> formally exists yet.
> There are lots of variables where EGEE appears
> and EGI should appear and we should make the changes
> systematically. I'll check if there is any documentation
> on which variables are affected and on any suggested
> approaches to change them.
I would have thought that variables like 'SITE_OTHER_EGEE_ROC'
are shell variables, and are used only by YAIM itself so what
would matter is the name of attributes and values in the LDIF
files generated, so changing variable name probably requires a
change in YAIM code, not in 'site-info.def'.
But I double checked and it appears that YAIM makes a special
case and chops off "SITE_OTHER_" from the names of shell
variables with that prefix and puts that and the shell variable
value as string values for 'GlueSiteOtherInfo' as done in
'/opt/glite/yaim/functions/config_gip_site':
> for i in ${!SITE_OTHER_*}
> do
> SUFFIX=${i//SITE_OTHER_/}
> OLDIFS=$IFS
> IFS="|"
> for j in ${!i}
> do
> echo "GlueSiteOtherInfo: $SUFFIX=$j" >> $outfile
> done
> IFS=$OLDIFS
> done
So one can define any YAIM shell variable with that prefix.
The question then becomes which apps looks at values of
'GlueSiteOtherInfo' and what those apps expect to see there.
I am not volunteering to figure that out :-).
