\section{Installation and Configuration}
-\TODO{}
\subsection{Complete RPMs description}
%\subsection{Daemons description}
%\subsection{CLI tools description: purge/dump/load}
+\TODO{honik}
+
+seznam RPM pro obe verze
+
+popisky rovnou doplnit do RPM
+
\subsection{\LB server}
\subsubsection{Hardware requirements}
\TODO{Initial YAIM way only, rest in Sect.~\ref{maintain:index}}
-\subsubsection{Notification delivery}
+\subsubsection{Server superusers}
-\subsubsection{Multiple server instances}
+Certain administrative operations (identified bellow when appropriate)
+on \LB server are privileged.
+When they are invoked remotely, a~special authorization is required.
+By default, the server identity (X509 certificate subject) is considered
+privileged.
+Additional subjects can be specified in \emph{superusers file},
+specified by \verb'--super-users-file' server option
+(one subject per line).
+After changing the file, the server has to be restarted.
+
+The default startup script checks for existence of
+/opt/glite/etc/LB-super-users and uses it eventually.
+
+
+\subsubsection{Notification delivery}
\subsubsection{Export to R-GMA}
Register for receiving notifications, and log events which trigger
the notification delivery. Checks the whole notification mechanism.
-\TODO{}
+\TODO{mozna jen odkaz do User Guide}
\subsection{Deployment scenarios}
+\TODO{salvet}
+
\TODO{jakou zatez ktery snese}
\subsubsection{Standalone \LB server}
It is complemented with the full commands reference that is provided
as standard manual pages installed with the \LB packages.
-\subsubsection{Server superusers}
-
-Certain administrative operations (identified bellow when appropriate)
-on \LB server are privileged.
-When they are invoked remotely, a~special authorization is required.
-By default, the server identity (X509 certificate subject) is considered
-privileged.
-Additional subjects can be specified in \emph{superusers file},
-specified by \verb'--super-users-file' server option
-(one subject per line).
-
-The default startup script checks for existence of
-/opt/glite/etc/LB-super-users and uses it eventually.
-
\subsubsection{Changing index configuration}
% full-scan skodi, LB se tomu brani
\subsubsection{On-line monitoring and statistics}
-CE Rank
+\TODO{ljocha: CE Rank}
-DB mon (a mon)
+\TODO{honik: DB mon (a mon)}
-histogramy :-)
+% histogramy :-)
\subsection{\LB proxy}
-Purge zamrzlych jobu (overit v kodu, na ktere verzi to mame(installed optionally in glite-jp-client.rpm) )
+\TODO{ljocha}
+Purge zamrzlych jobu (overit v kodu, na ktere verzi to mame )
\subsection{\LB logger}
+\TODO{ljocha}
+
Karantena (od ktere verze to mame?)
+- kdyz se nepodari rozparsovat soubor
+- client/examples -- parse-logevent-file??, lze pouzit
Cistky pri zaseknuti, nesmyslna jobid apod.
+Debugovaci rezim
+
+Notifikacni IL
+
\subsection{Used resources}
-Adresare, porty, ...
+\TODO{ljocha}
+Demoni, Adresare, porty, ...
\subsection{Concepts}
+\TODO{ruda: typy jobu -- simple, dag, collection}
+
\subsubsection{Jobs and events}
To keep track of user jobs on the Grid, we first need some reliable
way to identify them. This is accomplished by assigning a unique
-\section{Tools description}
+\section{User tools}
\label{s:lb-tools}
+\TODO{vytahnout WMS-UI do zvlastni kapitolky}
+
In this section we give a description of the tools that are installed
together with the \verb'glite-lb-client' RPM. These tools are \LB-specific.
Besides these tools, more general WMS commands \verb'glite-wms-job-status'
GLITE\_WMS\_LOG\_DESTINATION & address of \verb'glite-lb-logd' daemon, in form \verb'hostname:port'\\
GLITE\_WMS\_LOG\_TIMEOUT & timeout (in seconds) for asynchronous logging\\
GLITE\_WMS\_LOG\_SYNC\_TIMEOUT & timeout (in seconds) for synchronous logging\\
-GLITE\_WMS\_NOTIF\_SERVER& address of \verb'glite-lb-bkserver' daemon, in form \verb'hostname:port'\\
+GLITE\_WMS\_NOTIF\_SERVER& address of \verb'glite-lb-bkserver' daemon, in form \verb'hostname:port', for receiving notifications\\
GLITE\_WMS\_NOTIF\_TIMEOUT& timeout (in seconds) for notification registration\\
X509\_USER\_CERT and X509\_USER\_KEY & location of user credentials\\
\end{tabularx}
using standard X509 environment variables \verb'X509_USER_KEY' and
\verb'X509_USER_CERT'.
-For additional information see also manual page GLITE-LB-LOGEVENT(1).
+For additional information see also manual page glite-lb-logevent(1).
\input log_usertag.tex
environment variable.
\verb'glite-lb-notify' support these actions:
+
\begin{tabularx}{\textwidth}{lX}
\texttt{new} & Create new notification registration.\\
\texttt{bind} & Binds an notification registration to a client.\\
\texttt{ -f field1,field2,...} & list of status fields to print (only owner by default) \\
\end{tabularx}
-For additional information see also manual page GLITE-LB-NOTIFY(1).
+For additional information see also manual page glite-lb-notify(1).
\subsubsection{Example: Registration and waiting for simple notification}
\label{e:notify}
When you let notification client running several minutes without any incomming notification, it will finish and remove your registration from the server automatically.
+\subsubsection{Example: Waiting for notifications on all user's jobs}
+
+\TODO{}
+
\subsubsection{Example: Waiting for more notifications on one socket}
-\TODO{ljocha}
+\TODO{ruda}
git://scientific.zcu.cz / jra1mw.git / commitdiff