Skip to content
Snippets Groups Projects
Commit e31c6aac authored by Steven Murray's avatar Steven Murray
Browse files

Applied Vlado's corrections to CHEP 2016 paper

parent 9fee2a0c
Branches
Tags
No related merge requests found
No preview for this file type
......@@ -48,9 +48,9 @@ petabytes per year during 2017 and 2018.
LHC physics run 3 will start in 2021 and is predicted to store over 150
petabytes per year. Run 3 will use EOS and CTA as opposed to CASTOR to archive
data to tape. The CTA project will make more efficient use of tape drives in
order to deal with the predicted 150 petabytes of physics data per year. CTA
will accomplish this by introducing a pre-emptive drive scheduler that will keep
data to tape. The CTA project will increase tape drive utilization in order to
deal with the predicted 150 petabytes of physics data per year. CTA
will accomplish this by introducing a pre-emptive scheduler that will keep
tape drives running at full speed \cite{new} all of the time. Physics data on
tape are not only accessed by physicists. These data are read back for data
verification and read and re-written for tape media repack\cite{repack}
......@@ -74,25 +74,24 @@ and other users of CASTOR will migrate to EOS and CTA. Finally, section
\section{CTA architecture} \label{cta_architecture}
Figure \ref{architecture} shows the architecture of CTA which is composed of
many EOS instances communicating with a single CTA instance. Each LHC
experiment at CERN has its own EOS disk storage system and its own set of tapes.
The tape drives are shared by all of the experiments in order to be cost
effective. During any one day, an individual tape drive may mount and transfer
data to and from tapes belonging to many different experiments.
Figure \ref{architecture} shows many EOS instances communicating with a single
CTA instance. Each LHC experiment at CERN has its own EOS disk storage system
and its own set of tapes. The tape drives are shared by all of the experiments
in order to be cost effective. During any one day, an individual tape drive
may mount and transfer data to and from tapes belonging to many different
experiments.
\begin{figure}[h]
\includegraphics[width=\textwidth, trim=0mm 35mm 0mm 0mm, clip]{CTA_architecture_A4.pdf}
\caption{\label{architecture}The CTA architecture}
\caption{\label{architecture}The EOS and CTA architecture}
\end{figure}
Starting on the left hand side of figure \ref{architecture}. EOS clients such
as the \texttt{eos} and \texttt{xrdcp} command-line tools send commands to the
EOS manager server and transfer the contents of files to and from EOS disk
servers. EOS users see their disk files listed in the EOS namespace. They will
also see the copies of their files on tape in the EOS namespace. The tape files
will be seen as replicas. For example the \texttt{eos file info} command will
display the tape copies of a given EOS file.
servers. EOS users see their files on tape as additional replicas. For example
the \texttt{eos file info} command will display the tape replica of a given EOS
file.
In addition to its normal EOS duties, the EOS manager server also queues
requests with the CTA front-end in order to have EOS disk files archived to tape
......@@ -141,7 +140,7 @@ the experience of CASTOR including how to control tape hardware and how to queue
transfer requests in order to use tape hardware efficiently. The CTA tape drive
daemon queries the CTA metadata system for tapes to be mounted and files to be
transferred. The daemon transfers files between tapes and the EOS disk servers.
When the daemon has completed a transfer it writes the result back to the CTA
When the daemon has completed a transfer, it writes the result back to the CTA
metadata system.
The next two subsections explain step by step how a file is archived to tape and
......@@ -359,7 +358,6 @@ instances could be merged into one.
\end{figure}
CASTOR currently stores the custodial copy of all LHC physics data on tape.
Migrating data from CASTOR to EOS and CTA will be very efficient because
CASTOR and CTA share the same tape format. This means only the metadata
needs to be copied from CASTOR to EOS and CTA, no files needs to be copied
between CASTOR and CTA tapes. CTA will simply take ownership of CASTOR
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment