Job Provenance

From EgeeWiki

Contents

What is Job Provenance service

Job Provenance (JP) is a Grid service that keeps long-term trace on completed computations for further reference. It is a job-centric service, keeping records about job life cycle, its environment, inputs/outputs, user parameters etc. The data collected from the Grid middleware where the job has run can be complemented with user annotations that add a personalized view.

Why Job Provenance?

  • For GRID designers
Important feature of each grid system is a job lifecycle monitoring service. Example of such a service is the gLite Logging and Bookkeeping service. In a typical Grid today the valuable information collected by this service is available to the end users only during job lifetime. Purpose of Job Provenance is to store all collected information for long-term and allow efficient queries into stored provenance datasets. Having Job Provenance service available in a grid is also important for the user communities as the JP is designed to provide application specific view on grid jobs.
  • For system administrators
Typical job lifecycle monitoring service, such as gLite LB is not designed to keep large datasets. JP service deployment solves an issue of keeping the LB database reasonably small (purging) as it provides an automated LB to JP data moving facility. More...
  • For user groups (developers of its tools)
The JP service is designed to provide core engine to build custom application-specific job evaluation and management tools. For more information see Job Provenance Demo, Job Provenance in ATLAS environment, Job Provenance for AUGER experiment.
  • For end users
With JP a user gains access to all available records about finished jobs generated by grid services or attached to the jobs by users (during job life or after). JP helps to create application-specific view on the grid where a grid job is seen as a scientific experiment. The abilities of JP was also explored by participation in Provenance Challenges.

Use cases

  • Job Provenance as a logbook
  • Analyze finished jobs using the Job Provenance service
  • Job Provenance helps to organize experiments and submit jobs

Current status, news

News

13.2.2008 - Presentation at PDP2008, see [1], Multiple Ligand trajectory docking study - semiautomatic analysis of molecular dynamics simulations using egee glite services.

Status

Testbed: Job Provenance is currently running and available at JRA1 preview testbed.

Projects: Click here for projects evaluating Job Provenance service.

Release: Job Provenance release (how to install Job Provenance, available release tools and components)

Job Provenance design

Further resources


JRA1 CZ homepage