MAN01 How to publish Site Information

From EGIWiki
(Redirected from MAN01)
Jump to: navigation, search
Main operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators

Title How to publish Site Information
Document link
Last modified 19 August 2014
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group
Document Status Approved
Approved Date 26.07.2011
Procedure Statement This manual provides information on how to correctly publish site information in the Information Discovery System.
Owner Owner of procedure

  • EGI profile for the use of the GLUE 2.0 Information Schema - This document specifies how the GLUE 2.0 information schema should be used in EGI. It gives detailed guidance on what should be published, how the information should be interpreted, what kinds of uses are likely, and how the information may be validated to ensure accuracy.

Configuring a site BDII

The site BDII needs to be configured to read from every node in the site which publishes information (meaning that it runs a so-called resource BDII). In YAIM this is defined with the BDII_REGIONS variable, which contains a list of node names which in turn refer to variables called BDII_<NODE>_URL which specify the LDAP URL of each resource BDII.

Some services may have DNS aliases for multiple hosts, but the BDII_REGIONS must contain the real hostnames for each underlying node - the information in the resource BDII is different for each node, so reading it via an alias would produce inconsistent results. However, it will usually be desirable for the published endpoint URLs to contain the alias rather than the real hostname; that can often be defined with a YAIM variable for the service. For the site BDII itself this variable is SITE_BDII_HOST. (If multiple site or top BDIIs are configured identically their content will also be identical, so reading via an alias does not produce any inconsistencies.)

Most services now publish themselves, so sites should check that all relevant services are included. In particular, VOMS servers have only published themselves comparatively recently so may be missing from the configuration. If the glite-CLUSTER node type is used this must also be included. Publication has been enabled for Argus in EMI 2, so this may also need to be added. Common services which do not currently publish are APEL and Squid. See the table below for more detailed information.

It is important to realise that the site BDII itself has a resource BDII, and this must be explicitly included in the configuration, e.g. with something like




In the past it was common for the site BDII to be co-located with the CE so it did not need to be listed explicitly, but if installed on a dedicated node (which is now the recommended deployment) it must be included.

To check that all expected services are published the following command can be used:

ldapsearch -x -h <site-bdii-host> -p 2170 -b mds-vo-name=<site-name>,o=grid objectclass=GlueService \
                     | perl -p00e 's/\r?\n //g' | grep Endpoint:

(replacing <site-bdii-host> and <site-name> with the values for your site), which should list all the service URLs.

In addition, most services should now be published in GLUE 2 format. There is no explicit configuration needed for GLUE 2, but one thing to be aware of is that the site name (and the other parts like o=grid) in the GIIS URL field in the GOC DB must have the correct case as GLUE 2 is case-sensitive. To verify the GLUE 2 publication use the command

ldapsearch -x -h <site-bdii-host> -p 2170 -b GLUE2DomainID=<site-name>,o=glue objectclass=GLUE2Endpoint \
                     | perl -p00e 's/\r?\n //g' | grep URL:

Some services, notably storage elements, may be missing or incomplete in GLUE 2 if they are older than the EMI 2 release. The following table shows the publishing status for gLite and WLCG node types (ARC and Unicore have a different structure).

Node type GLUE 1 GLUE 2 Notes
LCG-CE Yes No Obsolete
CREAM Yes Yes Full publication only in EMI 2
CLUSTER Yes Yes Full publication only in EMI 2
WMS Yes Yes
LB Yes Yes
dCache Yes EMI 2
StoRM Yes EMI 2
FTS Yes EMI 2 Channels not yet published in GLUE 2
Hydra EMI 2 EMI 2 Not yet released in EMI 2
VOMS Yes Yes
MyProxy Yes Yes
Argus No EMI 2 Internal service, publication for deployment monitoring
Site BDII Yes Yes
Top BDII Yes Yes
R-GMA Yes No Obsolete
Apel No No Internal service, publishing not yet requested
Squid No No Configuration exists but not enabled
Nagios Yes Yes

Service-related documentation

Federated Cloud BDII configuration

For information about configuration of a Federated Cloud BDII, please look at the HOWTO15: HOWTO15 How to configure the Federated Cloud BDII

GlueSite Object

These are the existing well established attributes in the GlueSite object. All of these MUST remain.

Attribute Example Schema Notes
GlueSiteName RAL-LCG2 Free Text, No White Space Same as GOCDB name if in GOCDB, your choice.
GlueSiteUniqueID RAL-LCG2 Identical to your !GlueSiteName Same as GlueSiteName
GlueSiteWeb `` Free Text Valid URL about the site.
GlueSiteLatitude 52.42 NN.NN Site Latitute.
GlueSiteLongitude 16.91 NN.NN Longitude of Site.
GlueSiteDescription Rutherford Lab Free Text A long name for the site.
GlueSiteLocation Dublin, Ireland Town, City, Country An decreasing resolution ending with Country, agree a country name within a country. i.e UK != United Kingdom. Scotland and the Balkans should write a dynamic provider.
 !GlueSiteUserSupportContact `` Valid URL URL for getting support. A ticket system if available.
 !GlueSiteSysAdminContact `xmpp://` Valid URL How to contact the admins.
 !GlueSiteSecurityContact `` Valid URL How to contact for security related matters.

The GlueSite object in the 1.3 Glue Schema contains an attribute GlueSiteOtherInfo. To quote.

 The attribute is to be used to publish data that does not fit any other attribute of the site entity.
A name=value pair or an XML structure are example[s] of usage.

All this extra configuration will be with in the static information for the glue site within the Grid Information Provider system.

Guidelines for GlueSite Object

A format for publishing useful information about sites within the !GlueSiteOtherInfo is needed, as shown in the following table.

Key Example Type Notes
GRID EGI [#validgrid List of valid grid names] Multiple ones can be defined.
WLCG_TIER 1 Tier level of site in WLCG context. Either 0, 1 , 2 , 3 , 4
WLCG_PARENT UK-T1-RAL Name of the higher (administrative) tier site in WLCG The WLCG_NAME of the site at a higher tier with WLCG
WLCG_NAME IT-ATLAS-federation [#lcgnames Valid WLCG Names] An official WLCG name.
WLCG_NAMEICON `` Valid URL URL to WLCGNAME icon, ideally 80x80 pixels.
EGEE_ROC Russia Valid federated Operations Centre name Only applicable if your site is still part of a federated Operations Centre ("ROC" according to the old EGEE terminology). Name MUST match the Operations Centre name declared in GOCDB. Note. If the site is now part of a NGI, then EGI_NGI MUST be used (see below).
EGI_NGI NGI_CZ Valid NGI Must agree with the GOC DB
EGEE_SERVICE prod prod, pps or cert Which EGEE grid your site is part of, multiple attributes is okay. Obsolete in EGI.
OLDNAME Bristol text If your !GlueSiteName changes at some point please record your old name here.
ICON `` Valid URL Icon Image for your site, ideally 80x80 pixels
BLOG `` Valid RSS or Atom Feed Your site blog if you have one
CONFIG yaim yaim, puppet, quattor, ... The configuration tool(s) used at the site

Note. Keywords starting with one of the grid names are to some extent reserved for that grid.


GlueSiteName: RAL-LCG2
GlueSiteOtherInfo: BLOG=
GlueSiteOtherInfo: EGI_NGI=NGI_UK
GlueSiteOtherInfo: GRID=EGI
GlueSiteOtherInfo: GRID=GRIDPP
GlueSiteOtherInfo: GRID=WLCG
GlueSiteOtherInfo: ICON=
GlueSiteOtherInfo: WLCG_TIER=1

Distributed Tier1s and Tier2s

Within an WLCG context for instance there are instances of distributed Tier2s and Tier1s. If separate component sites want to exist as a single WLCG tier then they might contain common values for their WLCGNAME.

GlueSiteName: CSCS-LCG2
GlueSiteOtherInfo: CONFIG=yaim
GlueSiteOtherInfo: EGI_NGI=NGI_CH
GlueSiteOtherInfo: GRID=EGI
GlueSiteOtherInfo: GRID=WLCG
GlueSiteOtherInfo: WLCG_TIER=2

Note that WLCG_PARENT is an accounting unit defined in the MOU document, as shown in

Established Grid Name

Short Name Long Name URL
EGI European Grid Initiative
EELA Europe and Latin America
WLCG World LHC Computing Grid
GRIDPP UK Particle Physics Grid
UKNGS National UK Grid Service
OSG Open Science Grid (US)
NDGF Nordic DataGrid Facility
LondonGrid London Grid
NORTHGRID Northern (UK) Grid
SCOTGRID Scottish Grid
SOUTHGRID Southern (UK) Grid
Academic Grid Malaysia Malaysian Grid
UPM Campus Grid Universiti Putra Malaysia
AEGIS Academic and Educational Grid Initiative of Serbia
BIGGRID Dutch e-science Grid
Consorzio Cometa Consorzio Multi-Ente per la promozione e l'adozione di Tecnologie di calcolo Avanzato (Italy)
D-Grid German Grid
EUMED EU/Mediterranean Grid
GILDA Grid INFN Laboratory for Dissemination Activities (Italy)
GISELA Grid Initiative for e-Science virtual communities in Europe and Latin America
GRISU Griglia del Sud (Southern Italy Grid)
NEUGRID Neuroscience Grid
RDIG Russian Data Intensive Grid
SEE-GRID South Eastern European GRid-enabled eInfrastructure Development

Important: The EGEE Grid name was decomissioned on 14-02-2011. All sites need to replace this grid name with EGI.

Being part of a grid is just a reference that your site is in some way associated with a particular Resource Infrastructure Provider either technically or as part of a collaboration. The list of Grids can be extended. Please contact operations at to request changes.

Valid WLCG Names

The WLCG names are the site names that appear within the LCG MOU concerning commitments to LHC computing.

WLCG Name Current GlueSiteName
ES-PIC pic

For the tier two names please consult The column marked Accounting Name are the WLCG Names which in the case of Tier2s are the GOCDB names. Use your site GOCDB name as your WLCG_NAME.

Also some tier2s live under more than 1 tier1 perhaps for different for different VOs. If your tier2 has more that one WLCG_PARENT then just add two distinct records to show this. Also some tier2s do not have a WLCGNAME at all.

GlueSiteUniqueId: EENet
GlueSiteName: EENet
GlueSiteOtherInfo: GRID=WLCG
GlueSiteOtherInfo: GRID=EGI
GlueSiteOtherInfo: EGI_NGI=NGI_NL
GlueSiteOtherInfo: WLCG_TIER=2
GlueSiteOtherInfo: WLCG_PARENT=UK-T1-RAL
GlueSiteOtherInfo: WLCG_PARENT=NL-T1

Valid EGI NGI Names

The valid names are those published on GOCDB.

YAIM Instructions

YAIM will have to be updated for those sites using yaim. This will be done and submitted to sites in the normal way.

YAIM Variable and Value Resulting Glue Attribute and Value
SITE_DESC="Rutherford Lab" GlueSiteDescription: Rutherford Lab
SITE_EMAIL= GlueSiteSysAdminContact:
SITE_SUPPORT_EMAIL= GlueSiteUserSupportContact:
SITE_SECURITY_EMAIL= GlueSiteSecurityContact:
SITE_LOC="Soho, London, United Kingdom" GlueSiteLocation: Soho, London, United Kingdom
SITE_LONG=52.45 GlueSiteLongitude: 52.45
SITE_LAT=-12.34 GlueSiteLatitude: -12.34
SITE_WEB="" GlueSiteWeb:
GlueSiteOtherInfo: GRID=WLCG
SITE_OTHER_<KEY>="<VALUE1>|<VALUE2>|<VALUE3>" GlueSiteOtherInfo: <KEY>=<VALUE1>GlueSiteOtherInfo: <KEY>=<VALUE2>
GlueSiteOtherInfo <KEY>=<VALUE3>

If multiple values for GlueSiteOtherInfo are needed, then just delimit your values with a |. The charater | must be avoided in values.

Check your own GlueSite Object

The information published can be checked through an ldap search:

    $ ldapsearch -x -H ldap:// \
  -b 'Mds-Vo-Name=<SiteName>,o=Grid'  '(ObjectClass=GlueSite)'

In addition, VAPOR is a tool which provides a GUI for different views of published information, including a LDAP view.

Site information in GLUE 2

The GLUE 2 equivalent of the GlueSite object is the GLUE2AdminDomain. The same information should be present although in a slightly different format, and there are separate GLUE2Contact and GLUE2Location objects.

Revision History

Version Authors Date Comments
M. Krakowian 19 August 2014 Change contact group -> Operations support
B. Grenier 22 November 2017 Link FedCloud-specific doc
A. Paolini 03 July 2018 removed reference to GSTAT, added link to VAPOR