LFC

Description

The LFC (LCG File Catalog) is a catalog containing logical to physical file mappings. In the LFC, a given file is represented by a Grid Unique IDentifier (GUID). A given file replicated at different sites is then considered as the same file, thanks to this GUID, but (can) appear as a unique logical entry in the LFC catalog.

The LFC supports Oracle and MySQL as database backends.

Services and Ports

For the LFC server daemon, the port 5010 has to be open locally at your site.

For the LFC Data Location Interface (DLI), the port 8085 also has to be open.

For the information system the port 2170 has to be open locally at your site. It has to be visible by the site BDII.

2170    ldap
5010    lfc daemon
8085    lfc-dli

Installation of a LFC with MySQL

Repositories

The repositories are placed in directory /etc/yum.repos.d/.

All yum *.repos are available at http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2

The needed repositories are:

dag.repo
glite-LFC_mysql.repo
lcg-CA.repo

Get them with

cd /etc/yum.repos.d/
rm -f /etc/yum.repos.d/dag.repo
wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/dag.repo
wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-LFC_mysql.repo
wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/lcg-CA.repo

Installing the packages

Now the software has to be installed

yum install glite-LFC_mysql lcg-CA mysql-server

Configuration

As for most grid services you need a host certificate for the LFC with the right permissions. You can follow the instructions on this page.

Variables

Before the configuration script can be run create an empty site-info.def file in the directory /root/yaim/ and add/ adapt the required variables:

INSTALL_ROOT=
SITE_NAME=
USERS_CONF=
GROUPS_CONF=
MYSQL_PASSWORD=
LFC_DB_PASSWORD=<LFC DB user password>
LFC_DB_HOST=<LFC DB host name>
LFC_DB=<LFC database name>
LFC_CENTRAL=<List of VO names whose catalog is configured as central> # only one central LFC must exist for each VO
LFC_LOCAL=<List of VO names whose catalog is configured as local. If this variable is not defined, it is set to $VOS minus $LFC_CENTRAL>
VOS=
VO_<VO_NAME>_VOMS_CA_DN=
VO_<VO_NAME>_VOMS_SERVERS=
VO_<VO_NAME>_VOMSES=

In addition some information for the supported virtual organizations have to be set. Please refer to this link.

users.conf

For every VO you are supporting you need to define users in the users.conf file. For details please refer to this page.

groups.conf

For the LFC also the groups configuration file is required. For details please refer to this page.

Functions

The functions used can be found in file /opt/glite/yaim/node-info.d/glite-lfc_mysql:

LFC_mysql_FUNCTIONS="
  config_root_email
  config_ldconf
  config_sysconfig_edg
  config_sysconfig_globus
  config_sysconfig_lcg
  config_crl
  config_host_certs
  config_vomsdir
  config_edgusers
  config_mkgridmap
  config_bdii_only
  config_gip_only
  config_gip_lfc
  config_gip_service_release
  config_lfc_user
  config_lfc_upgrade
  config_lfc_mysql
  config_lfc_server
  config_lfc_dli
"

Configuration with yaim

Now, the configuration is done by yaim:

/opt/glite/yaim/bin/yaim -c -s /root/yaim/site-info.def -n glite-LFC_mysql

After successful configuration, you should try to access the LFC from your previously setup user interface. One of the usefuls command to query the LFC is

lfc-ls

Before you run the command you have to specify which LFC to query. This can be done via issuing the two commands

LFC_HOST=dgrid-lfc.fz-juelich.de
export LFC_HOST

Try afterwards a

lfc-ls /grid

---

Go back to gLite Administration Course