data:Dcache/1912/server

From Dgiref
Jump to: navigation, search
Please open a NGI-DE ticket if you experience any Installation or Configuration problem.

Contents

dCache server v1.9.12

Prepare

Operating system
Scientific Linux v.5.6 64 bit

Optimizing the configuration:


Use minimal operating system installation without firewall. To verify installed packages use the command

  • rpm -qa | grep package_name

Install the following additional packages:

  • yum -y install wget yum rpm make gcc gcc-c++ tar sed zlib openssl

After the installation is complete, turn off any unnecessary services (like gpm, sendmail, cups, haldaemon, messagebus, pcmcia, anacron, atd) with the following command:

  • chkconfig <SERVICE> off

Configure the following settings for the server:

  • The host running the srm transfer service needs to have a valid host certificate and a host key in place (/etc/grid-security/hostcert.pem, /etc/grid-security/hostkey.pem).
  • Prepared grid-vorolemap, storage-authzdb [dCache ABA]
Firewall configuration

For normal communication between dCache server and clients the list of default ports(see below) must be accepted on firewall (dCache default ports)

Port number Direction Component
32768 is used by the NFS layer within dCache which is based upon rpc. This service is essential for rpc. NFS
1939, 33808 is used by portmapper which is also involved in the rpc dependencies of dCache. portmap
34075 is for postmaster listening to requests for the PostgreSQL database for dCache database functionality. Outbound for SRM, PnfsDomain, dCacheDomain and doors; inbound for PostgreSQL server.
33823 is used for internal dCache communication. By default: outbound for all components, inbound for dCache domain.
8443 is the SRM port. See Chapter 14, dCache Storage Resource Manager Inbound for SRM
2288 is used by the web interface to dCache. Inbound for httpdDomain
22223 is used for the dCache admin interface. See the section called “The Admin Interface” Inbound for adminDomain
22125 is used for the dCache dCap protocol. Inbound for dCap door
22128 is used for the dCache GSIdCap . Inbound for GSIdCap doors

Install

Install dCache server and clients

  • dcache-server
  • dcap
  • libdcap
  • dcache-srmclient

Configure

Layout

dCache keeps list of the domains and the services that are to be run within these domains in the layout files. Every domain is a separate Java VM.

Note-icon.png
  
dCache provides 3 typical kinds of layout file: head.conf, pools.conf, single.conf.
Note-icon.png
  
If in layout file included more then one domain for normal communication between domains need to be set the parameter messageBroker=cells. In case when all services is working in one domain this parameter is should be set to none.

dcache.conf

The most important file which define layout file for node and specific parameters for current node-services (those parameters could be get from properties files from /usr/share/dcache/defaults/ directory)

Chimera

Chimera is a namespace provider for single-rooted view of distributed dCache files. For configuration Chimera:

  • Create a database for Chimera
  • upload the create.sql, pgsql-procedures.sql

Pools

Note-icon.png
  
dCache pools hold all the data ever written into dCache. These pools are completely independent from the PNFS directories (for the time beeing). In fact, they could be created anywhere and then mounted locally. Do not use the whole disk space available for the pools! dCache needs some additional space to keep record on metadata linked to files stored in each pool.

All files into dCache system located in pools. The pools could be definded on the several "pool-nodes". For define the pools:

  • create the pool directory
  • create a new domain for pool or include the pool service to exist domain into layout file
  • configure PoolManager.conf

PnfsManager

NFS interface for Chimera provides access to dCache file tree. Pnfs makes possible to get and change information about file without access to file data.

Note-icon.png
  
Pnfs just service for monipulation of file tree. it means that provides an access to dCache file tree. Could create, delete, change attributes of files but can't get derect access to file data.
Note-icon.png
  
Directory tags in PNFS are metadata, which will be evaluated by dCache and inherited by future subdirectories.

Publishing Dcache in site-bdii

See details [1]

Proceed

  • Make dCache as a service for OS and add it to autoboot system. So it will be started during boot.
  • Start dCache

Initial test

Simple dCache test for client side:

  • Grid user init
  • Generate random data file
  • Make a directory via srm service
  • Upload random file to dCache via srm
  • Download file from dCache server
  • Delete new file and new folder from destination host
  • Compare uloaded and downloaded file

If all tests passed, probably your dCache service is working normally.

Update

Note-icon.png
  
For easy update don't change the settings into /usr/share/dcache/defaults/*.properties manually (all changes should be set into dcache.conf)
  • For installation of new version from umd just use yum update.