Luděk Matyska

gLite job provenance

The Job Provenance (JP) service is designed to automate keeping track of computations on large scale Grids, giving thus users a tool to correctly archive information about their jobs and to re-submit any job in a reconstructed environment. JP provides a permanent minimal record of job (and its environment) related information, to which free-form user annotations can be added. JP also offers the capability of configuring any number of indexed logical views on the large collections of raw data, allowing efficient processing of even complex user queries selecting on both system data and the annotations. The scalable architecture, capable to handle millions of jobs in a single JP installation, and integrated into the EGEE gLite middleware environment is presented.

Catch-All Virtual Organizations - Solution for Heterogeneous and Disperse Grid Users Communities

The virtual organizations form a key concept for seamless utilization of all advanced features of available worldwide grid environments, the EGEE Grid in particular. However, apart from large, well organized user communities there is a substantial, non-trivial activation barrier in adopting grid concept and creating a new VO for small research groups. To minimize this barrier, a so-called “catch-all” virtual organization approach has been implemented. Here we present two successful use cases of catch-all virtual organizations (Virtual Organization for Central Europe and for EUAsia), demonstrating the strengths of this approach, discussing their setups, encountered challenges and suggesting corresponding solutions.

Something you may have wanted to know about L&B

Logging and Bookkeeping (L&B) is a gLite subsystem responsible for tracking jobs on the grid. Normally the user interacts with it via glite-wms-job-status and glite-wms-job-logging-info gLite commands. Here we present other, less generally known but still useful L&B usage patterns which are available with recently developed L&B features. L&B exposes simple HTML (for humans) and plain text (for scripting) interfaces over HTTPS. Hence, for example, pointing a web browser to a jobid yields human-readable page on the job status details. Similarly, the plain L&B server endpoint URL shows a clickable list of an active users jobs and notification handles. Apart of actively querying L&B server, users can also subscribe for receiving notifications on job state changes. Possible criteria range from simple whatever happens to this job to a job of this VO user gets resubmitted to another CE. We demonstrate how to use notifications via both API and CLI.