Page History
...
This page describes the general scheme how xrootd software an configuration files are installed and distributed at SLAC.
Taylor
Taylor is used to distribute xrootd releases to the data servers and redirectors. Taylor runs daily on a server. The actions Taylor performs are configured by an options file:
/etc/taylor.opts
To see the taylor options for a particular server login to that server and run:
taylor -q opts
For more information about Taylor run man taylor.
To configuration option for xrootd for Taylor are:
Wiki Markup xrootd=\[Name\],\[restart\] cmsd=\[restart\] olbd=\[restart\]
The Name and reatart option are optional. Name could be: glast, babar, atlas. The name might be used later on to
determine which configuration file 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.
...
server architecture | tgz arch name used by Taylor | comment |
|---|---|---|
Solaris 10 sparc | sun4x_510 |
|
Solaris 9 sparc | sun4x_59 |
|
Linux 64 bits RHEL4 | amd64_linux26 | xrootd build uses x86_64_linux_26 for the arch |
Linux 32 bits RHEL4 | i386_linux24 |
|
Linux 32 bits RHEL3 | i386_rhel30 |
|
Configuration files
...
To complete a xrootd installation the The following configuration files are distributed by Taylor(for xrootd and cmsd):
Config file | Copied to dir | Purpose |
|---|---|---|
xrootd.cf | /opt/xrootd/prod/etc | xrootd configuration read by xrootd and cmsd deamon at startup |
StartXRD.cf | /opt/xrootd/prod/etc | The StartXrd and StartCMS 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 |
These files are located in the distribution directory:
/afs/slac/package/xrd/distrib/xrootd/local
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:
Wiki Markup %%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 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, the xrootd-glast.cf file would be copied to /opt/xrootd/prod/etc/xrootd.cf.