From 6719bea2ead9d6a51f5221dd76d32ef4387276c3 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Ale=C5=A1=20K=C5=99enek?= Date: Mon, 7 Jul 2008 19:34:32 +0000 Subject: [PATCH] jp export --- org.glite.lb.doc/src/LBAG-Running.tex | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/org.glite.lb.doc/src/LBAG-Running.tex b/org.glite.lb.doc/src/LBAG-Running.tex index 42fbf42..7d0413b 100644 --- a/org.glite.lb.doc/src/LBAG-Running.tex +++ b/org.glite.lb.doc/src/LBAG-Running.tex @@ -206,7 +206,8 @@ dump the purged data into a~file at the server side. It's location (prefix) is given by \verb'-S' server option, the purge command reports a~specific file name on its output. -It is recommended (and the default YAIM setup does so) to run the purge +It is recommended (and the default YAIM setup does so, via +the \verb'glite-lb-export.sh' wrapper) to run the purge command periodically from cron. Server superuser privileges (X509 credentials) are required to run \verb'glite-lb-purge'. @@ -234,6 +235,24 @@ purge script \verb'glite-lb-bkpurge-offline.sh' \paragraph{Export to Job Provenance} +An important, though currently optional, processing of \LB dumps +is their upload to the Job Provenance service for permanent preservation +of the data. + + +When enabled (via configuration environment variables, see bellow), +the export is done in two steps: +\begin{itemize} +\item \verb'glite-lb-export.sh' wrapper script, after calling \verb'glite-lb-purge', breaks up the resulting dump file on a~per-job basis. +The individual job dump files are stored in a~dedicated spool directory. +\item \verb'glite-jp-importer' daemon (installed optionally in glite-jp-client.rpm) checks the spool directory periodically, +and tries to upload the files into JP. +\end{itemize} + +Details, including the configuration variables, are covered at the following +wiki page: +\url{http://egee.cesnet.cz/mediawiki/index.php/LB_purge_and_export_to_JP}. + \subsubsection{On-line monitoring and statistics} CE Rank -- 1.8.2.3