Hi
first I know there is savana bug (10398) open regarding this issue, and this is
an add-on to it
the yaim config_gip function for a LFC allows either a local or a global
catalog
to run in a given machine, not both.
The case at LIP and other sites is that the site supports some VO global
catalog
and also several local catalogs.
the solution is to manually modify the lcg-info-generic.conf and
lcg-info-static.ldif in the LFC machine.
the solution described in
http://goc.grid.sinica.edu.tw/gocwiki/2%2e6%2e0_Local_VO_published_as_Global_LFC
is not enough since with this solution one will have the following entries
# lfc.host.name, SiteName, grid (for globalvo)
dn: GlueServiceUniqueID=lfc.host.name,mds-vo-name=SiteName,o=grid
....
GlueServiceUniqueID: lfc.host.name
# lfc.host.name, SiteName, grid (for localvo)
dn: GlueServiceUniqueID=lfc.host.name,mds-vo-name=SiteName,o=grid
.....
GlueServiceUniqueID: lfc.host.name
that means a GlueServiceUniqueID two times (repeated) for two different
things, and this causes that the BDII will only publish one of it
since will not do it for repeated dn: entries
So the GlueServiceUniqueID has to be different for the local and global
catalog.
I have added this to the bug referred above
cheers
Mario David
|