CVMFSClient

Responsible

• David Lesny

Background

• Installatiion notes for a Admins.CVMFS Client configuration for the "osg.mwt2.org" repository
• Work being tracked in http://jira.usatlasfacility.org/browse/MW-259

Admins.CVMFS Client Configuration changes for the repository "osg.mwt2.org"

If a node is currently configured to use Admins.CVMFS Client to access the atlas.cern.ch and atlas-condb.cern.ch repositories, one only needs to create two additional files and modify another to allow the node to access the MWT2 repository "osg.mwt2.org".

These changes assume that the Admins.CVMFS servers for the "osg.mwt2.org" repository are uct2-cvmfs.mwt2.org (UC) and iut2-cvmfs.mwt2.org (IU). Long range plans are to add a third regional Admins.CVMFS replica server at UIUC called mwt2-cvmfs.campuscluster.illinois.edu (which should then be added to these configuration files).

The order of the servers listed in CVMFS_SERVER_URL should place the regional Admins.CVMFS server first in the list, with the other regional servers second and third. The same is true for the squid list in CVMFS_HTTP_PROXY.

The following configuration changes would be appropriate for an MWT2(IU) C-node.

Public Key

Copy the public key used on the master server for the "osg.mwt2.org" repository into /etc/cvmfs/keys/osg.mwt2.org

[root@mwt2-condor ~]# cat /etc/cvmfs/keys/osg.mwt2.org.pub 
-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4OcC10VG0S6UdcHbW/17
0Pbn1TYXfl6PFlaeaU+vvJgwVN4Miae1tP0Y+2V4VuvjWBrg8Pxh6MY/aZTZDREZ
9B5idAGPIjBfNZ1F9A8QEHvgz+ELv2aNp7vXMqsfO8wPugqioBsmj86g5dx4Gvva
I24GlNBKdtD1zRqapnR7TkejmAMqY9pUam296+5x1CJ29tuuqWf1Ar1593aEtpCc
joWnvDz7clzG4NNND5pAl4p++E6EvsFv9g9K8HnK0C1gfScmHZQSf0GnkSKgo9ZW
7krGRDHMCjzBjxRsiiHOT5bCihQ3ZYxLnD2p0EwfDiYhcL55A0izCR4SksTG4B9a
0wIDAQAB
-----END PUBLIC KEY-----

Configuration file for the "osg.mwt2.org" repository

The configuration file "osg.mwt2.org.conf" defines the Admins.CVMFS servers to use (in order of preference), the public key for the repository and the maximum size of the local Admins.CVMFS cache for the "osg.mwt2.org" repository

[root@mwt2-condor ~]# cat /etc/cvmfs/config.d/osg.mwt2.org.conf
CVMFS_SERVER_URL=http://iut2-cvmfs.mwt2.org/opt/@org@,http://uct2-cvmfs.mwt2.org/opt/@org@
CVMFS_PUBLIC_KEY=/etc/cvmfs/keys/osg.mwt2.org.pub
CVMFS_QUOTA_LIMIT=1000

Enable the "osg.mwt2.org" repository

To enable access to the "osg.mwt2.org" repository, the name must be added to the list of defined repositories (CVMFS_REPOSITORIES). This is normally defined in the file /etc/cvmfs/default.local, but the location is site dependent and might be defined in another file. In the following example, the repositories "atlas.cern.ch", "atlas-condb.cern.ch" and "osg.mwt2.org" will be available on this node.

The CVMFS_HTTP_PROXY defines the list of squids the node should use to front-end the Admins.CVMFS servers for each repository. This example has the MWT2(IU) squid listed first, with the squids at UIUC and UC as a secondary in a load balanced group.

CVMFS_CACHE_BASE defines the location of the local cache used by CVFMS Client

[root@mwt2-condor ~]# more /etc/cvmfs/default.local 
CVMFS_CACHE_BASE=/scratch.local/cvmfs2/cache
CVMFS_HTTP_PROXY="http://iut2-squid.iu.edu:3128;http://mwt2-squid.campuscluster.illinois.edu:3128|http://uct2-grid1.uchicago.edu:3128;DIRECT"
CVMFS_REPOSITORIES="atlas,atlas-condb,osg.mwt2.org"

Restart Admins.CVMFS Client

Once Admins.CVMFS Client has been configured to use the "osg.mwt2.org" repository, the server must be restarted to activate the changes. The best way is to do a "restartclean" which flushes the local Admins.CVMFS caches as well as restart the server

[root@mwt2-condor ~]# service cvmfs restartclean
Shutting down CernVM-FS:                                   [  OK  ]
Wiping out /scratch.local/cvmfs2/cache/atlas.cern.ch       [  OK  ]
Wiping out /scratch.local/cvmfs2/cache/atlas-condb.cern.ch [  OK  ]
Wiping out /scratch.local/cvmfs2/cache/osg.mwt2.org        [  OK  ]
Starting CernVM-FS:                                        [  OK  ]
[root@mwt2-condor ~]# 

Test access to the "osg.mwt2.org" repository

There as several commands one can use verify the "osg.mwt2.org" is available.

The simplest test is to simply "ls" the repository.

[root@mwt2-condor ~]# ll /cvmfs/osg.mwt2.org
total 14
drwxr-xr-x 1 cvmfs cvmfs 4096 Jun 27 12:56 app
drwxr-xr-x 1 cvmfs cvmfs 4096 Jun 27 12:04 CA
drwxr-xr-x 1 cvmfs cvmfs 4096 Mar 20 18:20 wn-client


[root@mwt2-condor current]# ll /cvmfs/osg.mwt2.org/app/atlas_app/local/
total 19
drwxr-xr-x 1 cvmfs cvmfs 4096 Jun 24  2011 lib
drwxr-xr-x 1 cvmfs cvmfs 4096 Jun 24  2011 lib64
-rw-r--r-- 1 cvmfs cvmfs   89 Mar 26 05:35 setup-dq2.sh
-rw-r--r-- 1 cvmfs cvmfs  511 Mar 24 11:33 setup.sh
-rwxr-xr-x 1 cvmfs cvmfs  571 May 16 14:16 setup.sh.local
-rwxr-xr-x 1 cvmfs cvmfs  733 May 11 09:47 setup.sh.local.20120511
-rwxr-xr-x 1 cvmfs cvmfs  580 May 16 14:15 setup.sh.local.20120516
-rw-r--r-- 1 cvmfs cvmfs  511 Mar  7 17:19 setup.sh.orig
-rw-r--r-- 1 cvmfs cvmfs 4758 Apr 27 10:21 vomses

One should also output the contents of a file within the repository

[root@mwt2-condor current]# cat /cvmfs/osg.mwt2.org/app/atlas_app/local/setup.sh.local
#export ATLAS_LOCAL_POOLCOND=yes

export FRONTIER_SERVER="(serverurl=http://frontier.racf.bnl.gov:8000/frontieratbnl)(serverurl=http://frontier.triumf.ca:3128/ATLAS_f
rontier)(proxyurl=http://uct2-grid1.uchicago.edu:3128)(proxyurl=http://iut2-squid.iu.edu:3128)"


# Xrd Proxy
export XrdSecGSIUSERPROXY=${X509_USER_PROXY}_XrdProxy
voms-proxy-init -quiet -voms atlas:/atlas -vomses /osg/mwt2/app/atlas_app/local/vomses -key $X509_USER_PROXY -cert $X509_USER_PROXY 
-out $XrdSecGSIUSERPROXY -noregen


[ -f /share/local/setup.sh.local ] && source /share/local/setup.sh.local

Other very useful commands are

service cvmfs probe	Probes the accessiblity of the defned repositories
cvmfs_config showconfig	Display the current configuration definitions
cvmfs_config chksetup	Verify the syntax of the configuration files
cvmfs-talk host info	Display the defined hosts (Admins.CVMFS servers) for each repository
cvmfs-talk proxy info	Display the defined proxies (Squid servers) for each repository