Installing OSG Client, gLite client, and DQ2 user tools

Introduction

This page covers the installation of different DQ2 tools at UofC. For an introduction and instructions on how to set them up and how to use them (user instructions) check UsingDQ2AtUC. For generic installation instruction check here on BNL twiki.

Exporting software via NFS

These are installation notes that could be useful for system administrators. Before proceeding here is a description of the UofC configuration. These tools have been installed on a server and exported to all the others machine using NFS. E.g. /share/osg-client on the NFS server is a bind mount of /export/osg-client that is exported to all other machines in the cluster and NFS mounted as /share/osg-client. Bind mounts instead of soft link are necessary to overcome a Pacman limitation. The same configuration is valid for the other installation directories.

OSG wlcg-client installation

An OSG client is installed in /share/wlcg-client using the pacman installation (pacman -get http://www.mwt2.org/caches/:wlcg-client):

Here is the installation of a self conteined version, e.g. for non root users. Answer yes to the initial questions during configuration (cache entrusting and licenses):

• Cache entrusting, like Do you want to add [http://...] to [trusted.caches]? (y/n/yall): y
• Do you agree to the licenses? [y/n] y

The system installation used on UCT2 and UCT3 was done a root, using the grid certificates already installed and maintained in /etc/grid-security/. To do the same answer to the remaining questions:

• Would you like to enable the Condor batch system to run automatically? n
• Would you like to setup daily rotation of VDT log files? n
• Do you want to update the CA certification revocation lists (CRLs) automatically? [y/n] n
• Where would you like to install CA files? ... n (no) - do not install n

If a regular user is looking for a private installation questions are different and he should choose the following:

• Where would you like to install CA files? l [ l (local) - install into $VDT_LOCATION/globus/share/certificates ]

More details and alternative configurations are available on the BNL twiki

Post installation bug fix: The OSG client in VDT 1.8 includes an extra directory in the PYTHONPATH. If you experience the error: OSError: [Errno 2] No such file or directory: '/share/osg-client/globus/lib64/python' (e.g. running Pathena in a 64bit machine on a 32 bit OS), then fix the installation by creating a directory globus/lib64/python within the installation.

OSG client

It is a subset of wlcg-client. It is the main package wlcg-client is derived from. wlcg-client installation with pacman installs OSG client and a couple other small packages necessary for interoperability, so do not install the simple OSG client.

OSG Worker Node client

There is a lighter version of the OSG client, called Worker Node Client (pacman -get OSG:wn). This client installation is used by batch or Grid jobs (non interactive users) and it is a required part of the OSG CE installation. At UofC this client is installed in /share/wn-client. After installing it with Pacman its globus-url-copy should be upgraded as described above for osg-client.

Furthermore if your WN-Client is part of an OSG Site installation, check OSG documentation and comply with all its requirements. Specially, each time this package is installed or relocated, the OSG information system had to be updated:

• siteinfo.py, storage_access_info.py: these are Panda files. Any Panda developer (including myself and Charles) can update them.
• OSG configuration: OSG_GRID must point to the directory of wn-client. This is done with the configure-osg script in the monitoring directory of the OSG installation

DQ2 client

This is the new DQ2 client (developed by Miguel and Mario at CERN). It includes both DQ2 site service client commands and user tools (dq2-* commands).

The DQ2 team (specially Mario Lassnig) is providing a new DQ2 client that includes both the client programs to interact with site services and central catalog and also the enduser tools to move datasets (dq2-get/ls/...). Therefore this packages replaces both previous DQ2-Client and Enduser-tools (dq2_get/ls/...). Since version 0.1.17 the DQ2-Client Pacman installation is compatible with OSG's WLCG-Client and check catalogs and moves files correctly from/to both OSG and LCG storage elements. To simplify maintenance we recommend to install DQ2-Client in a separate directory:

mkdir /share/dq2-client
cd /share/dq2-client
pacman -trust-all-caches -allow tar-overwrite -get http://atlas.web.cern.ch/Atlas/GROUPS/DATABASE/project/ddm/releases/pacman/cache:DQ2Clients

As usual, to use the client you'll have to source the setup file created by Pacman during the installation. For documentation about the DQ2-Client refer to the pages provided by the DQ2 team:

• how to install DQ2-Client using Pacman
• Check DQ2-Clients wiki page and user manual

(Old) DQ2 user tools installation (deprecated!)

It is preferred to use the DQ2 client described in the previous section.

This installation (/share/dq2/) includes:

• DQ2 user tools (dq2_XXX commands to get/put files)
• DQ2 Client (to interact with DQ2 Site services and central server, e.g. register subscriptions)

DQ2 clients are released aperiodically: sometime the files are updated and most of the time no new release is announced (new releases are announced for the server, but they are loosely related), so it is useful to check periodically for new versions of the files.

The directory dq2 is created. The client is installed as recommended in http://dashb-build.cern.ch/ddm/build/stable/doc/guides/dq2-clientapi/html/user/installSection.html#dq2ByTarballsSection (To install the development version check here) :

$ mkdir dq2/ 1
$ cd dq2/
$ wget "http://atlas.web.cern.ch/Atlas/GROUPS/DATABASE/project/ddm/releases/dq2.download/downloadDQ2StableClient.py" -O downloadDQ2StableClient.py
wget "https://twiki.cern.ch/twiki/bin/viewfile/Atlas/DDMClientInstallation?filename=downloadDQ2Client.py.txt" -O downloadDQ2Client.py                 
$ python downloadDQ2Client.py

NB: The post-install configuration in section "2.4.4. DQ2 Post-Installation" is only for RPM installations. It is not necessary with the tarball installation.

The user tools are downloaded from the CVS repository or from one of the AFS installation (usually are in sync, /afs/usatlas.bnl.gov/Grid/Don-Quijote/dq2_user_client/) as mentioned in https://twiki.cern.ch/twiki/bin/view/Atlas/UsingDQ2#Download

Then the setup files are edited to accommodate local needs (dq2.sh, dq2.csh, setup.sh.MWT2_UC, setup.sh.any)

Check

To check the client tools you can set them up and try user commands (see UsingDQ2AtUC). Pay attention to the following:

• the attached script is testing dq2_get by fetching a file: test-dq2_user_client.sh

Using AFS

An alternative to a local installation of DQ2 enduser tools and LCG UI is to use the installation available on AFS from CERN or BNL. If you are on a machine that has no endusertools or LCG UI but has AFS access (e.g. your notebook) you can setup LCG UI and DQ2 endusertools using the AFS installations at BNL or CERN as documented in https://twiki.cern.ch/twiki/bin/view/Atlas/UsingDQ2:

source /afs/usatlas.bnl.gov/lcg/current/etc/profile.d/grid_env.sh
source /etc/glite/glite.[c]sh
source /afs/usatlas.bnl.gov/Grid/Don-Quijote/dq2_user_client/setup.[c,z]sh.any

or

source /afs/cern.ch/project/gd/LCG-share/current/external/etc/profile.d/grid-env.[c]sh
source /afs/cern.ch/atlas/offline/external/GRID/ddm/stable/dq2.[c]sh
source /afs/cern.ch/atlas/offline/external/GRID/ddm/endusers/setup.[c,z]sh.any

More information

-- MarcoMambelli - 29 Jan 2008