Logging and Bookkeeping
What is LB?
Logging and Bookkeeping (LB for short) is a Grid service that keeps a short-term trace of Grid jobs as they are processed by individual Grid components.
The LB was initially developed in the EU DataGrid project as a part of the Workload Management System (WMS). The development continued in the EGEE project (EGEE-II, EGEE-III respectively), where LB became an independent part of the gLite middleware.
Current status & news
News
- 13.4.2010 User Forum Poster - Monitoring CREAM Jobs in RTM via L&B here.
- 1.4.2010 LB 2.0 is certified - see patch #3795 in Savannah for release notes and other info.
- 15.12.2009 A update of LB roadmap presented at JRA1 All-hands meeting.
- 19.6.2009 - a patch 1.9.2 released. Support of export to MSG. See patch #3075 in Savannah.
Current status
- LB service major versions:
- LB version 1.x, that is included in gLite 3.1 and widely deployed production version. Download here.
- LB version 2.0 is current production
version. It is certified and its deployment begins.
See patch
#3795 in Savannah for release notes and other info. Highlights:
- non-intrusive purger (task #7632)
- extended and streamlined LB notifications (related to tasks #7630, #7631)
- simple LB interfaces (HTML and plain/text queries, part of task #7637)
- advanced authorization (allow specifying trusted components to log critical LB events, FQANs to define LB superusers; task #7634)
- extensively rewritten documentation
- New development releases (see roadmap) what are usually deployed on JRA1 preview testbed and used as a experimental service.
- Older version of LB, that appeared in gLite 3.0 become obsolete and is not maintained anymore.
- Platform support - LB itself proves to be portable - we've managed to build on Debian 4, SLC 4, SL 5, and SuSE 9, 10, and 11, all in 32 and 64 bit clones. On the contrary, a fully automated build in Etics is not available.
- IPv6 support - LB internals work with hostnames only, no IPs are recorded in any internal data structures. Therefore IPv4-specific code is clustered around handling network connections, and we don't expect serious problems with IPv6 support (the only potential complication is c-ares library, however, it claims IPv6 already). Full IPv6 compliance is expected with LB 2.1.
Development roadmap
- Upcoming release - LB 2.1
- preliminary IPv6 readiness
- advanced authorization (finer superuser access -- limit accessible fields eg. for monitoring tools; task #7634)
- elementary support for native (non-WMS) CREAM jobs (task #7638)
- common logging format (task #7633)
- unification of LB authz configuration
- Collection aware purge
- Initial implementation of WS interface to support AGU / Glue 2.0
- Logging sandbox transfer events - specic state machine
- Full LB roadmap here
Why LB?
To understand the role of LB in Grid middleware design, its role in Grid management and operation and the LB usage patterns of Grid users we can recommend our presentation at 2008 CESNET conference available here.Further resources
Contacts & support
- User support for gLite users is available via GGUS support system.
- Apparent software bugs are tracked in Savannah. In the documentation you will find what information might be useful when submitting a LB specific problem/bug.
- You are encouradged to send developers all non-bugs comments and questions by email egee-jra1(at)lindir.ics.muni.cz.
Last modified: $Date: 2010/04/16 12:52:39 $ by $Author: sitera $.