CvmFS Client Setup Inside CERN

This page details particulars for setting up CvmFS clients within CERN and is not for general CvmFS client setup, for that see: http://cernvm.cern.ch/portal/filesystem.

Configuration By Hand

• Install CvmFS packages using the standard method detailed at http://cernvm.cern.ch/portal/filesystem
• Configure the CERN Site Proxy Server. All CvmFS clients at CERN can and should use the IT provided squid service hosted at ca-proxy.cern.ch:3128. To configure CvmFS the file /etc/cvmfs/default.local should contain:

CVMFS_HTTP_PROXY="http://ca-proxy.cern.ch:3128"

• On modern operating systems, CvmFS will likely be used together with autofs. In case some repositories should be kept always mounted, add them to the /etc/fstab file. As example:

atlas.cern.ch /cvmfs/atlas.cern.ch cvmfs defaults,_netdev,nodev 0 0 

Particular Repositories

Some repositories are not part of the default configuration and require a particular configuration. AMS requires cvmfs-keys > 1.2 to include the IT signing keys.

ALICE repositories

Alice repositories (alice.cern.ch, alice-nightlies.cern.ch, alice-ocdb.cern.ch) can benefit from dedicated caches. It is recommended to create the files /etc/cvmfs/config.d/<reponame>.cern.ch.local containing

CVMFS_HTTP_PROXY='http://ca-proxy-alice.cern.ch:3128;http://ca-proxy.cern.ch:3128'

ATLAS repositories

Atlas repositories (atlas.cern.ch, atlas-nightlies.cern.ch, atlas-condb.cern.ch, atlas-online-nightlies.cern.ch, atlas-pixel-daq.cern.ch) can benefit from dedicated caches. It is recommended to create the files /etc/cvmfs/config.d/<reponame>.cern.ch.local containing

CVMFS_HTTP_PROXY='http://ca-proxy-atlas.cern.ch:3128;http://ca-proxy.cern.ch:3128'

CMS repositories

Create the file /etc/cvmfs/config.d/cms.cern.ch.local containing

export CMS_LOCAL_SITE=T2_CH_CERN

Note: the parameter "T2_CH_CERN" is specific for the CERN site only.

CMS repositories (cms.cern.ch, cms-bril.cern.ch, cms-ci.cern.ch, cms-ib.cern.ch, cms-opendata-conddb.cern.ch) can benefit from dedicated caches. It is recommended to create (or add to) the files /etc/cvmfs/config.d/<reponame>.cern.ch.local containing

CVMFS_HTTP_PROXY='http://cmsmeyproxy.cern.ch:3128;http://ca-proxy.cern.ch:3128'

LHCb repositories

LHCb repositories (lhcb.cern.ch, lhcbdev.cern.ch, lhcb-condb.cern.ch) can benefit from dedicated caches. It is recommended to create the files /etc/cvmfs/config.d/<reponame>.cern.ch.local containing

CVMFS_HTTP_PROXY='http://ca-proxy-lhcb.cern.ch:3128;http://ca-proxy.cern.ch:3128'

SFT repositories

SFT repositories (sft.cern.ch, sft-nightlies.cern.ch) can benefit from dedicated caches. It is recommended to create the files /etc/cvmfs/config.d/<reponame>.cern.ch.local containing

CVMFS_HTTP_PROXY='http://ca-proxy-sft.cern.ch:3128;http://ca-proxy.cern.ch:3128'

Configuration By Puppet

See http://github.com/cvmfs/puppet-cvmfs for full details but using the AI puppet masters the following should be enough

class{'cvmfs':}
cvmfs::mount{['atlas.cern.ch','cms.cern.ch']:
}

LxPlus as a Reference

Copying configuration files from LxPlus is also very possible.

Client Verification

To verify your configuration

cvmfs_config probe

Support

For assistance of CvmFS clients within CERN a snow ticket can be created within the CvmFS category.

-- SteveTraylen - 21-Feb-2012