general ObjectStoreURL rados://cta-id@cta-tapepool:cta-ns
\end{lstlisting}
\begin{alertbox}
BufferCount specifies the size of the ObjectStore in blocks. But what is the size of a block?
\end{alertbox}
\section{Configure an EOS workflow to allow EOS to talk to the CTA front-end}
\subsection{tapeserverd configuration}
\section{Rmcd configuration}
Rmcd is the Remote Media Changer daemon, a TCP/IP server (which you must run locally for security reasons: it only listens to the localhost network). Has a device driver for the drive and one for the library.
The tape drives can now be indicated to tapeserverd through the \texttt{/etc/castor/TPCONFIG} file:
The file \texttt{/etc/sysconfig/rmcd} contains the following parameters:
\begin{lstlisting}
DAEMON_COREFILE_LIMIT=unlimited
RUN_RMCD=yes
RMCD_OPTIONS=/dev/smc
\end{lstlisting}
\begin{boxedverbatim}
VDSTK1 VLSTK /dev/nst0 smc0
VDSTK2 VLSTK /dev/nst1 smc1
\end{boxedverbatim}
\section{Install the Tape Server}
\label{install_cta_install_tape_server}
The memory blocks size and number shall also be added in \texttt{/etc/castor/castor.conf}:
If the CTA instance is not using real tape hardware, follow the directions in Appendix~\ref{install_mhvtl} to install the
mhVTL Virtual Tape Library.
\begin{boxedverbatim}
TapeServer BufSize 5242880
TapeServer NbBufs 200
\end{boxedverbatim}
\section{Starting up the xroot server with the CTA plugin}
Julien and Eric's scripts create the following \texttt{/etc/xrootd/xrootd-cta.cfg}:
\begin{lstlisting}
# Load the plugin XrdCtaOfs
xrootd.fslib libXrdCtaOfs.so
Finally we start the CTA version of \textbf{tapeserverd}:
\subsection{Starting up the xroot server with the CTA plugin}
Before starting the xroot server we need to change the VFS backend permissions again (because new files have been created with the \texttt{stage:st} user by the tapeserver daemon). Example:
...
...
@@ -432,34 +476,6 @@ We now create some useful soft links to simplify the xrootd configuration:
The CTA Command Line Interface needs to speak to a \emph{xroot} server which uses the CTA plugin to interpret and execute the commands sent by the user. All the information needed by the \emph{xroot} server is contained within a configuration file which is currently called \texttt{xrd.cf.cta}. Its contents is the following:
\begin{verbatim}
# Load the plugin XrdCtaOfs
xrootd.fslib /usr/lib64/libXrdCtaOfs.so
# Use the Kerberos 5 security module
xrootd.seclib libXrdSec.so
# The xroot server process needs to be able to read the keytab file
All this will work fine provided that you have a file called \texttt{/etc/krb5.keytab.cta} which is a copy of your keytab file (\texttt{/etc/krb5.keytab}). \texttt{/etc/krb5.keytab.cta} must be owned by the user.group that will run the \emph{xroot} server process. If you don't have a keytab file you may get one using \texttt{cern-get-keytab}(for CERN supported Linux systems) or \texttt{msktutil}(for other systems), as explained in:
The \emph{xroot} server then can be launched with the following command:
\begin{verbatim}
...
...
@@ -507,6 +523,8 @@ Where the first parameter is the name of the xroot instance, the second one is t
The \emph{xroot} server can be stopped by pressing \texttt{Ctrl+c}. Once the server is running, the CTA CLI will be able to send commands and receive results.
\section{Configure an EOS workflow to allow EOS to talk to the CTA front-end}
\subsection{Preparing the EOS workflows }
The closew,retrive and deletearchive EOS workflows need to be registered to work with CTA. The following EOS command have to be applied for CTA directory:
...
...
@@ -559,54 +577,15 @@ To trigger manually EOS workflows just use the following eos commands:
file workflow <filename> default delete
\end{verbatim}
\section{tapeserverd configuration}
The tape drives can now be indicated to tapeserverd through the \texttt{/etc/castor/TPCONFIG} file:
\begin{boxedverbatim}
VDSTK1 VLSTK /dev/nst0 smc0
VDSTK2 VLSTK /dev/nst1 smc1
\end{boxedverbatim}
The memory blocks size and number shall also be added in \texttt{/etc/castor/castor.conf}:
\begin{boxedverbatim}
TapeServer BufSize 5242880
TapeServer NbBufs 200
\end{boxedverbatim}
Finally we start the CTA version of \textbf{tapeserverd}:
Using \texttt{tpstat} and \texttt{tpconfig}, one can put the drive up and see it attempt to schedule itself
in the logs (either \texttt{/var/log/messages} or \texttt{/var/log/castor/tapeserverd.log} depending on the
installation and leftovers from previous castor tape server.
The log typically look like (simplified) in a loop:
\section{Rmcd configuration}
Rmcd is the Remote Media Changer daemon, a TCP/IP server (which you must run locally for security reasons: it only listens to the localhost network). Has a device driver for the drive and one for the library.
\begin{boxedverbatim}
MSG="ProcessForker handling a ProcessForker message" type="ForkDataTransfer" len="47"
