> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
> [log in to unmask]] On Behalf Of Stephen Burke
> It wasn't about the GOC DB, although that is potentially also an issue.
> The point is that site BDIIs publish themselves and therefore they need to
> include themselves in their configuration. If you have multiple site BDIIs
> behind an alias the recommended approach is to publish each node
> separately with with the alias name in the URL (defined by the
> SITE_BDII_HOST yaim variable). Imperial have chosen to publish as though
> they only had a single node.
Which they should be able to do. There has been an increasing degree of
creep in the information system expecting to have access to internal site
implementation details that should be none of its business. This already
causes problems with things like multicore vs hyperthreading, heterogeneous
clusters, variable sized clusters and assorted other things that don't
quite fit the model. We generally deal with it my ignoring the silly
requirements, but it would be a lot more sensible if they weren't there in
the first place.