\subsubsection{CREAM jobs}
-\LB 2.2 implements support for CREAM jobs. \LB gathers events from CREAM, performing both the mapping of CREAM attributes to WMS attributes (if possible) and storing CREAM-specific attributes. Thus, the jobs submitted directly to computing elements can be tracked by \LB. Moreover, the jobs submitted to WMS and from there to CREAM logs WMS and CREAM data which are integrated by \LB providing more detailed and up-to-date job's data. The CREAM job states are mapped to \LB ones according to Appendix \ref{a:creammapping}.
+\LBver{3.2} implements support for CREAM jobs.\footnote{Essential support was already available in \LBver{2.1}.} \LB gathers events from CREAM, performing both the mapping of CREAM attributes to WMS attributes (if possible) and storing CREAM-specific attributes. Thus, jobs submitted directly to computing elements can be tracked by \LB. Moreover, jobs submitted to WMS and from there to CREAM log WMS- and CREAM-specific data, which are integrated by \LB to provide more detailed and up-to-date job status information. CREAM job states are mapped to \LB's state diagram according to Appendix \ref{a:creammapping}.
-CREAM events are generated by thee CREAM executor and LRMS, the generic \emph{CREAMStatus} event is generated when CREAM notifies that the job status has been changed.
+CREAM events are generated by the CREAM executor and LRMS; the generic \emph{CREAMStatus} event is generated when CREAM notifies that the job status has been changed.
\subsubsection{Sandbox transfers}
A sandbox transfer is special entity in \LB, which tracks the transfer of input or output sandboxes of the (compute) job. Thus, it allows to check state of sandboxes giving more detailed overview of the status of compute job.
git://scientific.zcu.cz / jra1mw.git / commitdiff