From bbb2b80b139cc6d4b890724384e57227254bc76f Mon Sep 17 00:00:00 2001 From: =?utf8?q?Milo=C5=A1=20Mula=C4=8D?= Date: Mon, 21 Jul 2008 09:16:43 +0000 Subject: [PATCH] various comments --- org.glite.lb.doc/src/LBAG-Installation.tex | 8 +++++--- org.glite.lb.doc/src/LBAG-Introduction.tex | 2 ++ org.glite.lb.doc/src/LBAG-Running.tex | 4 ++-- org.glite.lb.doc/src/LBDG-Introduction.tex | 2 ++ org.glite.lb.doc/src/LBDG.tex | 3 +++ org.glite.lb.doc/src/LBUG-Introduction.tex | 5 ++++- org.glite.lb.doc/src/LBUG-Tools.tex | 2 ++ org.glite.lb.doc/src/consumer_api.tex | 5 +++++ 8 files changed, 25 insertions(+), 6 deletions(-) diff --git a/org.glite.lb.doc/src/LBAG-Installation.tex b/org.glite.lb.doc/src/LBAG-Installation.tex index b9be338..eac4dae 100644 --- a/org.glite.lb.doc/src/LBAG-Installation.tex +++ b/org.glite.lb.doc/src/LBAG-Installation.tex @@ -27,7 +27,7 @@ For temporary files, approximately 10\,GB is sufficient for LB server setups working normally, more can be needed when backlog forms in data export to any external service. For example, typical setup processing 40\,000 jobs per day where all jobs are purged after 10 days needs about 58 -($0.000000120\cdot 40000\cdot 10 + 10$) gigabytes (not accounting for operating +($10 \cdot 40000 \cdot 0.000000120 + 10$) gigabytes (not accounting for operating system and system logs). For smooth handling of 40\,000 jobs/day, this or better machine configuration @@ -180,7 +180,8 @@ and started as described above. Register a~new job with the \LB server and check that its status is reported correctly. -\req Installed glite-lb-client package, valid user's X509 credentials. +\req Installed glite-lb-client package, valid user's X509 credentials, +known destination (address:port) of running \LB server. Can be invoked from any machine. \how @@ -200,7 +201,8 @@ The command should report ``Submitted'' job status. Send several \LB events, simulating normal job life cycle. Checks delivery of the events via \LB logger. -\req Installed glite-lb-client package, valid user's X509 credentials. +\req Installed glite-lb-client package, valid user's X509 credentials, +known destination (address:port) of running \LB server. Must be run on a~machine where glite-lb-logger package is set up and running. \how diff --git a/org.glite.lb.doc/src/LBAG-Introduction.tex b/org.glite.lb.doc/src/LBAG-Introduction.tex index df262b1..f417b69 100644 --- a/org.glite.lb.doc/src/LBAG-Introduction.tex +++ b/org.glite.lb.doc/src/LBAG-Introduction.tex @@ -28,6 +28,8 @@ and delivering the events to \LB servers where users can query for them \label{f:comp-query} \end{figure} +\TODO{uplne to same (ty components) mame i v UG; chceme to tady duplikovat? +zvlast kdyz v odstavci nad tim se pise, ze uz je to popsane v UG} \input components diff --git a/org.glite.lb.doc/src/LBAG-Running.tex b/org.glite.lb.doc/src/LBAG-Running.tex index e3ee44e..d208f66 100644 --- a/org.glite.lb.doc/src/LBAG-Running.tex +++ b/org.glite.lb.doc/src/LBAG-Running.tex @@ -192,7 +192,7 @@ However, it is triggered with \verb'glite-lb-purge' client command A~typical invocation specifies \LB server to purge (\verb'-m' option), and purge timeouts (grace periods) for several job states -- options \verb'-a' (aborted), \verb'-n' (canceled), \verb'-c' (cleared), and -\verb'-o' (other). +\verb'-o' (other). \LB versions 2.0 supports also \verb'-e' (done) option. A~job falling in one of the four categories is purged when it has not been touched (\ie an event arrived) for time longer than the specified category timeout. @@ -214,7 +214,7 @@ Server superuser privileges (X509 credentials) are required to run \verb'glite-l If the server database has already grown huge, the purge operation can take rather long and hit the \LB server operation timeout. At client side, \ie the glite-lb-purge command, it can be increased by setting GLITE\_WMS\_QUERY\_TIMEOUT -environment variable. +environment variable. \TODO{mozna zminit, ze i po tom timeoutu bezi purge dal?} Sometimes hardcoded server-side timeout can be still reached; in this case the server fails to return a correct response but the purge is done anyway. diff --git a/org.glite.lb.doc/src/LBDG-Introduction.tex b/org.glite.lb.doc/src/LBDG-Introduction.tex index aab8e2f..df5bfee 100644 --- a/org.glite.lb.doc/src/LBDG-Introduction.tex +++ b/org.glite.lb.doc/src/LBDG-Introduction.tex @@ -68,6 +68,8 @@ much as possible. In a few cases the error can not be intuitively mapped and \LB specific error value greater than \lstinline'EDG_WLL_ERROR_BASE' is returned. +\TODO{mozna by stalo za to zminit f-ce edg\_wll\_*Error*} + Few API function return \lstinline'char *'. In such a~case \lstinline'NULL' indicates an error, non-null value means success. diff --git a/org.glite.lb.doc/src/LBDG.tex b/org.glite.lb.doc/src/LBDG.tex index 0254f92..31367c3 100644 --- a/org.glite.lb.doc/src/LBDG.tex +++ b/org.glite.lb.doc/src/LBDG.tex @@ -77,6 +77,9 @@ Interface is described in details together with programing examples. } \newpage \input{web_services} +\TODO{zminit http interface - podporujeme ho jeste? tusim ze fila +to nejak resuscitoval} + \newpage \bibliographystyle{unsrt} \bibliography{lbjp} diff --git a/org.glite.lb.doc/src/LBUG-Introduction.tex b/org.glite.lb.doc/src/LBUG-Introduction.tex index 7633a46..954c0f0 100644 --- a/org.glite.lb.doc/src/LBUG-Introduction.tex +++ b/org.glite.lb.doc/src/LBUG-Introduction.tex @@ -124,6 +124,8 @@ to every single event. The primary key is the jobid, which is also one of the required attributes. The other common attributes are currently the timestamp of the event origin, generating component name and the event sequence code (see Sect.~\ref{evprocess}). +\TODO{je jich mnohem vic (type, arrived, priority, ....) cili bud bych +je vyjmenoval vsechny, nebo napsal neco jako 'priklady nekterych dalsich jsou...'} While the necessary and sufficient condition for a global jobid is to be Grid-wide unique, additional desired property relates to the @@ -916,4 +918,5 @@ functions, allowing the user to specify that similarly misbehaving CE's should be penalized or completely avoided when RB decides where jobs get submitted. - +\TODO{zminit, ze umime zpracovavat condorove a PBS joby; jsou i v appendixu v seznamu eventu, tak by se asi nekde zminit mely} +% \subsubsection{Non-glite event sources} diff --git a/org.glite.lb.doc/src/LBUG-Tools.tex b/org.glite.lb.doc/src/LBUG-Tools.tex index d445e38..e3c3625 100644 --- a/org.glite.lb.doc/src/LBUG-Tools.tex +++ b/org.glite.lb.doc/src/LBUG-Tools.tex @@ -19,6 +19,7 @@ GLITE\_WMS\_NOTIF\_SERVER& address of \verb'glite-lb-bkserver' daemon, in form \ GLITE\_WMS\_NOTIF\_TIMEOUT& timeout (in seconds) for notification registration\\ X509\_USER\_CERT and X509\_USER\_KEY & location of user credentials\\ \end{tabularx} +\TODO{zminil bych i EDG\_WL\_QUERY\_SERVER} For backward compatibility, all \verb'GLITE_WMS_*' variables can be prefixed by \verb'EDG_WL_' instead. @@ -33,3 +34,4 @@ For debugging purposes, low-level commands for getting \LB job status and job re \verb'examples' directory (\verb'glite-lb-job-status' and \verb'glite-lb-job-log'). The same directory contains also debugging commands for getting of all user jobs (\verb'glite-lb-user_jobs') and CE-reputability rank (see Section \ref{s:ce-rank}, \verb'glite-lb-stats'). +\TODO{job-log vs. job\_log - ujednotit} diff --git a/org.glite.lb.doc/src/consumer_api.tex b/org.glite.lb.doc/src/consumer_api.tex index 83835bb..1946d89 100644 --- a/org.glite.lb.doc/src/consumer_api.tex +++ b/org.glite.lb.doc/src/consumer_api.tex @@ -487,6 +487,8 @@ interval. ... \end{verbatim} +\TODO{pro prehlednost bych mozna pridal seznam vsech atributu +na ktere se lze ptat} \subsection{Event queries and application specific queries} \label{ASQ} @@ -830,3 +832,6 @@ red jobs, but they have failed. ... \end{verbatim} \fi + +\TODO{pro prehlednost bych mozna pridal seznam vsech atributu +na ktere se lze ptat} -- 1.8.2.3