Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Table of Contents

Introduction

This page describes the general scheme how xrootd software an configuration files are installed and distributed at SLAC.

...

To configuration option for xrootd for Taylor are:

Wiki Markupxrootd=\[Name\],\[restart\] cmsd=\[restart\] olbd=\
cmsd=[restart\]

The Name and reatart restart option are optional. Name could be: glast, babar, atlas. The name might be used later on to
is used by Taylor to determine which configuration file (xrootd.cf) to be used for a particular host.
The restart option is used by ranger. If it is set ranger will check every 15min if the daemon is running and if not try to restart it by executing "/opt/xrootd/prod/etc/StartXRD" (or StartCMS, StartOLB).

Distributing the xrootd tgz files.

...

When Taylor runs on an xrootd server it finds all release that matches the architecture of the local host and if will untar the release to the /opt/xrootd directory if the
release has not yet been installed. This means that all release that are available in the distribution directory are also available on an xrootd server.

...

To complete a xrootd installation the following configuration files are distributed by Taylor(for xrootd, cmsd and cmsdfrm):

Config file

Copied to dir

Purpose

xrootd.cf

/opt/xrootd/prod/etc

xrootd configuration read by xrootd, cmsd and cmsd frm deamon at startup

StartXRD.cf

/opt/xrootd/prod/etc

The StartXrd, StartCMS and StartCMS StartFRM scripts source this script. It contains the start up configuration

RestartALL

/opt/xrootd

script to restart xrootd or cmsd

activate

/opt/xrootd

script to activate a xrootd version

...

The xrootd.cf and StartXRD.cf files depend on the xrootd cluster and therefore these files include the proper configuration file depending on the server host name or the taylor options for xrootd. For example the xrootd.cf
file might contain the lines:

...

No Format

%%if   ($ENV{HOSTSTEM} eq 'kan') || ($ENV{HOSTNAME} eq 'bbr-rdr03') || ($ENV{HOSTNAME} eq 'bbr-rdr04')
%%include /afs/slac/package/xrd/distrib/xrootd/local/xrootd-kan.cf
%%elif (Option->xrootd->has('glast'))
%%include /afs/slac/package/xrd/distrib/xrootd/local/xrootd-glast.cf
%%endif

Taylor is passing parsing this file and if the server host name used the stem kan (e.g. kan103) the xrootd-kan.cf file
would be copied to /opt/xrootd/prod/etc/xrootd.cf. If the taylor xrootd option for the server is Taylor is running on has the value glast (e.g.: xrootd=glast,restart), the xrootd-glast.cf file would be copied to /opt/xrootd/prod/etc/xrootd.cf.