data:Dcache/192/server

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

Contents

Dcache/192/server

Prepare

Operating system
Scientific Linux v.5.1 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:

  • java 1.6 SDK.
  • PostgreSQL version 8 or higher must be installed and running.


Firewall configuration

The dCache frontend runs SE services (GRIS, GridFTP, SRM). Which ports are used for dCache is essentially not important. But it's advisable when all sites that support dCache are using the same ports, so compatibility is automatically achived in an easy manner. When you are setting up your dCache system (by means of dCacheConfigure.sh) you can configure the ports to be opend in site-info.def with the varibales...

DCACHE_PORT_RANGE_PROTOCOLS_SERVER_GSIFTP
Sets the portrange for dcache as a GSIFTP server in "passive" mode. Default value is from 50000 till 52000 ("50000,52000").
DCACHE_PORT_RANGE_PROTOCOLS_CLIENT_GSIFTP
Sets the portrange for dcache as a GSIFTP client in "active" mode. Default value is from 33115 till 33125 ("33115,33125").
DCACHE_PORT_RANGE_PROTOCOLS_SERVER_MISC
Sets the portrange for dcache as a (GSI)DCAP and xrootd server in "passive" mode. Default value is from 60000 till 62000 ("60000,62000").


And this is what dCache developers suggest to configure the firewall. (table taken from dCache book, chapter 22)

Protocol Port(s) Direction Nodes
dCap 22125 incoming doorDomain (admin node)
any outgoing pools
GSIdCap 22128 incoming gsidcapDomain (where GSIDCAP=yes in node_config)
any outgoing pools
GridFTP 2811 incoming gridftpDomain (where GRIDFTP=yes in node_config)
20000-25000 outgoing (active FTP) pools
20000-25000 incoming (passive FTP) gridftpDomain
SRM v1 8443 incoming srmDomain
SRM v2 8444 incoming srmDomain

To change these configurations after setting up dCache, go to /opt/d-cache/config/dCacheSetup and modify the values for (if you want to adopt the settings proposed by the developers)...

  • in the "Java Configuration" section the parameters
    • Dorg.globus.tcp.port.range to "20000,25000"
    • Dorg.dcache.net.tcp.portrange to "33115,33215"
  • in the section "Network Configuration"
    • dCapPort to "22125"
    • dCapGsiPort to "22128"
    • gsiFtpPortNumber to "2811"
    • srmPort to "8443"
    • clientDataPortRange to "20000,25000"

Install

WARNING: Two users edguser and edginfo must be added on information provider nodes (in general this is considered to be the "admin node"). They are not needed on other nodes but, since their presence will do no harm, they may be added on all nodes.

Getting the dCache sources
Now to install finally dCache install the following bundles (yum install should install all given arguments, but it's more reliable to install the bundles separately)

Configure

Get dCache working
When all sources are installed, some configurations have to be done. For this purpose dCache brought some configuration script with it: dCacheConfigure.sh. This script needs two other files for further statements: site-info.def and users.conf. Both of which might be know to people that already have worked with gLite. In fact, it are the same files extended with some dCache specific statements. You can find (and should make a copy to start with) templates located at /opt/d-cache/share/doc/dCacheConfigure/examples.
mkdir /root/nodeconfig
cp /opt/d-cache/share/doc/dCacheConfigure/examples/* /root/nodeconfig
The users.conf
Maybe your site already has a ready-made users.conf, just get it then. Otherwise the default one shipped with dCache is a good starting point. For documentation on the content please look at CERN TWiki.
The site-info.def file

Same for the site-info.def, if your site already has one, use it.

Locating Java
As dCache uses Java, you will need to know the path to your installation of Java Development Kit (JDK). Please note this is not the path to the runtime environment (JRE), which is often a subdirectory within the JDK.
          [root@dcache-node] rpm -qa|grep jdk
          jdk-1.5.0_16-fcs
          [root@dcache-node] rpm -ql jdk-1.5.0_16-fcs | grep bin/java
          /usr/java/jdk1.5.0_16/bin/java
          /usr/java/jdk1.5.0_16/jre/bin/java

In the above example, the JDK path is /usr/java/jdk1.5.0_16.

You must update your /root/nodeconfig/site-info.def file, altering the values of the following variables:

  • MY_DOMAIN
  • JAVA_LOCATION
  • USERS_CONF
  • DCACHE_ADMIN
  • DCACHE_POOLS
  • DCACHE_DOOR_SRM
  • DCACHE_DOOR_GSIFTP
  • DCACHE_DOOR_XROOTD
  • DCACHE_DOOR_LDAP
  • VOS

WARNING: Please be aware that there are two DCACHE_DOOR_XROOTD variables declared in the site-info.def file. This will be fixed with the next release, but in the mean-time, simply delete the extra instance.

When running dCacheConfigure.sh, you must explicitly allow the script to reset various configuration options. This means you must either uncomment the existing lines or add extra lines.


    RESET_DCACHE_CONFIGURATION=yes
    RESET_DCACHE_PNFS=yes
    RESET_DCACHE_RDBMS=yes

With these lines in place, you must run dCacheConfigure.sh to configure dCache. Be patient, it may take several minutes to run.

WARNING: After running dCacheConfigure.sh you should remove or comment-out the three lines that start RESET_. Failure to do this will reset vital data when you next run dCacheConfigure.sh, almost certainly resulting in data loss.</p>

Suitable values are given below.

Initial test

  • check dCache web interface on the dcache server port 2288
  • accessing file system with standard commands
  • copying data using dCache protocols
  • deleting files in dCache

Additional information can be used from the previous dcache instance.

Update

To update/remove the dCache server state, use:

Personal tools