From f8091463c340b08cbf4f8d924f3f4199ac2a6d4d Mon Sep 17 00:00:00 2001 From: =?utf8?q?Ale=C5=A1=20K=C5=99enek?= Date: Tue, 8 Jul 2008 10:28:12 +0000 Subject: [PATCH] global checkpoint -- todo's --- org.glite.lb.doc/src/LBAG-Installation.tex | 27 ++++++++++++++++++++---- org.glite.lb.doc/src/LBAG-Introduction.tex | 2 ++ org.glite.lb.doc/src/LBAG-Running.tex | 34 +++++++++++++----------------- org.glite.lb.doc/src/LBUG-Introduction.tex | 2 ++ org.glite.lb.doc/src/LBUG-Tools.tex | 6 ++++-- org.glite.lb.doc/src/logevent.tex | 2 +- org.glite.lb.doc/src/notify.tex | 9 ++++++-- 7 files changed, 54 insertions(+), 28 deletions(-) diff --git a/org.glite.lb.doc/src/LBAG-Installation.tex b/org.glite.lb.doc/src/LBAG-Installation.tex index 1a7d545..15a1a6f 100644 --- a/org.glite.lb.doc/src/LBAG-Installation.tex +++ b/org.glite.lb.doc/src/LBAG-Installation.tex @@ -1,10 +1,15 @@ \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} @@ -78,9 +83,23 @@ transakce \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} @@ -210,4 +229,4 @@ Send events via \LB proxy. Checks the proxy functionality. 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} diff --git a/org.glite.lb.doc/src/LBAG-Introduction.tex b/org.glite.lb.doc/src/LBAG-Introduction.tex index f19705e..df262b1 100644 --- a/org.glite.lb.doc/src/LBAG-Introduction.tex +++ b/org.glite.lb.doc/src/LBAG-Introduction.tex @@ -33,6 +33,8 @@ and delivering the events to \LB servers where users can query for them \subsection{Deployment scenarios} +\TODO{salvet} + \TODO{jakou zatez ktery snese} \subsubsection{Standalone \LB server} diff --git a/org.glite.lb.doc/src/LBAG-Running.tex b/org.glite.lb.doc/src/LBAG-Running.tex index d58a415..79fa0ca 100644 --- a/org.glite.lb.doc/src/LBAG-Running.tex +++ b/org.glite.lb.doc/src/LBAG-Running.tex @@ -7,20 +7,6 @@ that need more verbose description. 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 @@ -263,23 +249,33 @@ wiki page: \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, ... diff --git a/org.glite.lb.doc/src/LBUG-Introduction.tex b/org.glite.lb.doc/src/LBUG-Introduction.tex index 5d73daf..7633a46 100644 --- a/org.glite.lb.doc/src/LBUG-Introduction.tex +++ b/org.glite.lb.doc/src/LBUG-Introduction.tex @@ -84,6 +84,8 @@ see Sect.~\ref{local}. \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 diff --git a/org.glite.lb.doc/src/LBUG-Tools.tex b/org.glite.lb.doc/src/LBUG-Tools.tex index ac186f3..d445e38 100644 --- a/org.glite.lb.doc/src/LBUG-Tools.tex +++ b/org.glite.lb.doc/src/LBUG-Tools.tex @@ -1,6 +1,8 @@ -\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' @@ -13,7 +15,7 @@ Behaviour of \verb'glite-lb-*' commands can be changed by setting the following 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} diff --git a/org.glite.lb.doc/src/logevent.tex b/org.glite.lb.doc/src/logevent.tex index 6ca6eb4..7210803 100644 --- a/org.glite.lb.doc/src/logevent.tex +++ b/org.glite.lb.doc/src/logevent.tex @@ -43,7 +43,7 @@ to valid X509 user credentials has to be set to authorise her. This is done 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 diff --git a/org.glite.lb.doc/src/notify.tex b/org.glite.lb.doc/src/notify.tex index 2d50008..22e2cfc 100644 --- a/org.glite.lb.doc/src/notify.tex +++ b/org.glite.lb.doc/src/notify.tex @@ -21,6 +21,7 @@ However, only a single active client for a notification is allowed. 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.\\ @@ -74,7 +75,7 @@ where \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} @@ -96,6 +97,10 @@ Wait for notification: 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} -- 1.8.2.3