1 / 7

Lightweight Preservation Environment

Lightweight Preservation Environment. Gary Jackson <garyj@umiacs.umd.edu>. Introduction. The LPE is a prototype data grid built in conjunction with Fujitsu Labs of America In part, the LPE is a test bed for exercising Globus grid technologies

breck
Download Presentation

Lightweight Preservation Environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lightweight Preservation Environment Gary Jackson <garyj@umiacs.umd.edu>

  2. Introduction • The LPE is a prototype data grid built in conjunction with Fujitsu Labs of America • In part, the LPE is a test bed for exercising Globus grid technologies • An intention of the LPE is to preserve data. I will not be talking about the preservation measures today.

  3. Globus Components • The LPE is largely built on Globus Toolkit components • Grid Security Infrastructure (GSI) and GSI interfaces • Replica Location Service (RLS) • Metadata Catalog Service (MCS) • GridFTP

  4. Implementation • The implementation is based on GT3 and the Open Grid Services Infrastructure (OGSI) • This infrastructure is being replaced with Web Services Resource Framework (WS-RF)

  5. Implementation • The LPE is implemented as a set of Grid Services • This means each component has it’s own API that can be accessed through web-service remote procedure call

  6. Implementation • The Data Manager (DM) is the core of the LPE • The Preservation Manager (PM) and Transform Manager (TM) handle preservation aspects • The interface is servlet-based to talk natively to the DM

  7. Lessons Learned • Globus is flexible, but also complicated • Some Globus components are fragile (MCS, RFT) while others are very solid and reliable (GSI interfaces, GridFTP) • Globus is evolving and improving: the implementation was made much better with subsequent toolkit releases

More Related