FTS BDII Publishing (gLite 1.3)

Overview

This document describes how to publish from a FTS server into the LCG BDII the information on the endpoints it provides. This can then be used by the FTS clients, as well as other clients such as the experiment frameworks.

We cover in this document how to set up the BDII, how to configure the BDII publication script and how to test it is working.

For more information on the BDII see EGEE.BDII Documentation

Pre-requisites

This requires that the FTS is running gLite 1.3, with the Quick Fix QF22 or Quick Fix QF23 applied.

BDII Installation

The BDII rpms are not provided by the standard gLite installer. Instead, they should be taken from the LCG distribution you are using at your site. Alternatively, you can get the from the current LCG (2.6.0) repository.

You require:

• bdii-3.3.7
• lcg-info-templates-1.0.13
• lcg-schema-1.2.1
• glue-schema-1.2.2

BDII Configuration

There are three configuration files for the BDII. These are

• /opt/bdii/etc/bdii.conf
• /opt/bdii/etc/bdii-update.conf
• /opt/bdii/etc/schemas

There are templates for these files in /opt/bdii/doc. For a standard install, first copy over the provided bdii.conf.

> cp /opt/bdii/doc/bdii.conf.example /opt/bdii/etc/bdii.conf

You will then need to either

• add a user bdiiuser
• change the user in the configuration file specified by the variable BDII_USER. This will be the user that the daemon runs under e.g. daemon or edguser.

The schemas file should contain the following:

/etc/openldap/schema/core.schema
/opt/glue/schema/ldap/Glue-CORE.schema
/opt/glue/schema/ldap/Glue-CE.schema
/opt/glue/schema/ldap/Glue-CESEBind.schema
/opt/glue/schema/ldap/Glue-SE.schema
/opt/lcg/schema/ldap/SiteInfo.schema

The bdii-update.conf controls what information is published. Here, you need to specify one line which defines the script and its options that will be used. The file will contain only this line. An example is

FTS file:///opt/glite/sbin/glite-data-transfer-fts-info-provider --vo dteam 
 --vo alice --site CERN-SC

where CERN-SC is replaced by your site name, as published in the GOC DB, and the supported VOs are dteam and alice. The next section provides more details on what options are valid for the script.

Once configured properly, you can start the BDII, using the init.d script provided.

Information Provider configuration

The Information Provider queries the service for information such as endpoints, but some information needs to be specified on the command line. The syntax is

glite-data-transfer-fts-info-provider [ --bdii | --file ] 
[ --site site_name ] [ --vo vo_name... ]  [ --verbose ]

Currently you need to specify your site name, as in the GOC DB, and the VOs that you support (--bdii is currently a default for what format to publish the information in).

Publishing via a Site BDII

In order for the information to be published, you then need to add to your site BDII, a line in bdii-update.conf for it to query the FTS BDII, e.g.

...

GRISFTS ldap://sc3-fts.cern.ch:2170/mds-vo-name=local,o=grid

...

where sc3-fts.cern.ch is replaced the hostname where your FTS is running.

Testing Publication

After a few minutes, you should be able to see the FTS being published in the top-level BDII lcg-bdii.cern.ch

[root@lxb2088 root]# ldapsearch -h lcg-bdii.cern.ch:2170 -b "mds-vo-name=local,o=grid" -x -LLL  'GlueServiceUniqueId=site-fts*' GlueServiceName|grep lxshare026d
dn: GlueServiceUniqueID=site-fts_lxshare026d.cern.ch_org.glite.FileTransfer,md
GlueServiceName: site-fts_lxshare026d.cern.ch
dn: GlueServiceUniqueID=site-fts_lxshare026d.cern.ch_org.glite.ChannelManageme
GlueServiceName: site-fts_lxshare026d.cern.ch-channel

you should replace the hostname lxshare026d with the hostname you are running the FTS one. You should see 2 lines of the form

GlueServiceName: site-fts_HOSTNAME
GlueServiceName: site-fts_HOSTNAME-channel

where HOSTNAME is the name of the FTS host.

Problems?

For any problems, please contact lcg-sc.support@cern.ch