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
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
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
\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
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.
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.
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.
\newpage
\input{web_services}
+\TODO{zminit http interface - podporujeme ho jeste? tusim ze fila
+to nejak resuscitoval}
+
\newpage
\bibliographystyle{unsrt}
\bibliography{lbjp}
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
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}
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.
\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}
...
\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}
...
\end{verbatim}
\fi
+
+\TODO{pro prehlednost bych mozna pridal seznam vsech atributu
+na ktere se lze ptat}