\label{a:events}
Complete list of all events' names together with their description follows.
% see events.tex.T
-\TODO{Enable page break in the following table:}
\input{events}
\newpage
% see status.tex.T
\input{status}
-
+\begin{figure}[hb]
+\centering
+\includegraphics[width=.6\hsize]{images/wms2-jobstat}
+\caption{\LB\ job state diagram}
+\end{figure}
-\section{Introduction}
+\section{\LB Architecture}
\input versions
%historie: vyrobeno pro WMS v EDG, 1. a 2. verze (seq. èísla,
\begin{figure}
\centering
-\includegraphics[width=.8\hsize]{images/wms2-jobstat}
+\includegraphics[width=.6\hsize]{images/wms2-jobstat}
\caption{\LB\ job state diagram}
\label{f:jobstat}
\end{figure}
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, \verb'glite-wms-job-status' and \verb'glite-wms-job-logging-info' available
-in \verb'glite-wms-ui-cli-python' RPM, provide more information about user jobs and corresponding events.
+Besides these tools, more general WMS commands \verb'glite-wms-job-status'
+and \verb'glite-wms-job-logging-info' available
+in \verb'glite-wms-ui-cli-python' RPM, provide also information about user jobs
+and corresponding events.
Behaviour of \verb'glite-lb-*' commands can be changed by setting the following enviroment variables:
\begin{tabularx}{\textwidth}{lX}
GLITE\_WMS\_NOTIF\_TIMEOUT& timeout (in seconds) for notification registration\\
X509\_USER\_CERT and X509\_USER\_KEY & location of user credentials\\
\end{tabularx}
-For backward compatibility, all \verb'GLITE\_WMS\_*' variables can be prefixed by \verb'EDG\_WL\_' instead.
+For backward compatibility, all \verb'GLITE_WMS_*' variables can be prefixed by
+\verb'EDG_WL_' instead.
\input{logevent}
For debugging purposes, low-level commands for getting \LB job status and job related events are provided in
\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
+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').
is as follows:
\begin{verbatim}
-glite-lb-logevent -e ChangeACL -s UserInterface -p --permission 1 \
- -j <job_id> \
- --user_id <user_id> \
- --user_id_type <user_id_type> \
+glite-lb-logevent -e ChangeACL -s UserInterface -p --permission 1
+ -j <job_id>
+ --user_id <user_id>
+ --user_id_type <user_id_type>
--permission_type <permission_type> --operation <operation>
\end{verbatim}
\begin{tabularx}{\textwidth}{lX}
\verb'<job_id>' & specifies the job to change \\
\verb'<user_id>' & specifies the user to use, can be either an X.500 name
- (subject name) or a VOMS group (of the form <VO>:<Group>)\\
+ (subject name) or a VOMS group (of the form
+ VO:Group)\\
\verb'<user_id_type>' & \verb'0' or \verb'1', indicating \verb'user_id'
specifies X.500 name or VOMS group, respectively \\
\verb'<permission_type>' & \verb'0' or \verb'1', indicating the user is
};
@@@}
+Events for gLite world:
+
\begin{tabularx}{\textwidth}{l>{\bfseries}lX}
@@@{
my $flesh = 'gLite'; #XXX
if ($flesh ne $event->{flesh}->{$e}) {
$flesh = $event->{flesh}->{$e};
- gen "% new flesh $flesh \n";
+ gen "\\end{tabularx}\n";
+ gen " Events for $flesh world:\n\n";
+ gen "\\begin{tabularx}{\\textwidth}{l>{\\bfseries}lX}\n";
$fleshno += 100;
$eventno = $fleshno;
}
General template for adding user tag is as follows:
\begin{verbatim}
-glite-lb-logevent -s Application -e UserTag \
- -j <job_id> \
- -c <seq_code> \
- --name <tag_name> \
+glite-lb-logevent -s Application -e UserTag
+ -j <job_id>
+ -c <seq_code>
+ --name <tag_name>
--value <tag_value>
\end{verbatim}
Command usage is:
\begin{verbatim}
- glite-lb-logevent [-h] [-p] [-c seq_code] \
+ glite-lb-logevent [-h] [-p] [-c seq_code]
-j <dg_jobid> -s Application -e <event_name> [key=value ...]
\end{verbatim}
where
\begin{tabularx}{\textwidth}{lX}
-\texttt{ -h -{}-help} & this help message\\
\texttt{ -p -{}-priority} & send a priority event\\
\texttt{ -c -{}-sequence} & event sequence code\\
\texttt{ -j -{}-jobid} & JobId\\
Each event specified after \verb'-e' option has different sub-options enabling
to set event specific values.
-Address of local logger, where event is sent, must be specified by environment
+Address of local-logger, daemon responsible for further message delivery, must
+be specified by environment
variable \verb'GLITE_WMS_LOG_DESTINATION' in a form \verb'address:port'.
Because user is allowed to change ACL or add user tags only for her jobs, paths
environment variable.
\verb'glite-lb-notify' support these actions:
-\begin{description}
-\item[new] Create new notification registration
-\item[bind] Binds an notification registration to a client.
-\item[refresh] Enlarge notification registration validity.
-\item[receive] Binds to an existing notification registration and listen to server.
-\item[drop] Drop the notification registration.
-\end{description}
+\begin{tabularx}{\textwidth}{lX}
+\texttt{new} & Create new notification registration.\\
+\texttt{bind} & Binds an notification registration to a client.\\
+\texttt{refresh} & Enlarge notification registration validity.\\
+\texttt{receive} & Binds to an existing notification registration and listen to
+server.\\
+\texttt{drop} & Drop the notification registration.\\
+\end{tabularx}
For action \verb'new', command usage is:
\begin{verbatim}
- glite-lb-notify new [ { -s socket_fd | -a fake_addr } -t requested_validity ] {-j jobid | -o owner | -n network_server | -v virtual_organization }
+ glite-lb-notify new [ { -s socket_fd | -a fake_addr } -t requested_validity ]
+ {-j jobid | -o owner | -n network_server | -v virtual_organization }
\end{verbatim}
For action \verb'bind', command usage is:
\begin{verbatim}
-glite-lb-notify bind [ { -s socket_fd | -a fake_addr } -t requested_validity ] notifid
+ glite-lb-notify bind [ { -s socket_fd | -a fake_addr } -t requested_validity ]
+ notifid
\end{verbatim}
For action \verb'refresh', command usage is:
\begin{verbatim}
-glite-lb-notify refresh [-t requested_validity ] notifid
+ glite-lb-notify refresh [-t requested_validity ] notifid
\end{verbatim}
For action \verb'receive', command usage is:
\begin{verbatim}
-glite-lb-notify receive [ { -s socket_fd | -a fake_addr } ] [-t requested_validity ] [-i timeout] [-f field1,field2,...] [notifid]
+ glite-lb-notify receive [ { -s socket_fd | -a fake_addr } ] [-t requested_validity ]
+ [-i timeout] [-f field1,field2,...] [notifid]
\end{verbatim}
For action \verb'drop', command usage is:
\begin{verbatim}
-glite-lb-notify drop notifid
+ glite-lb-notify drop notifid
\end{verbatim}
where
git://scientific.zcu.cz / jra1mw.git / commitdiff