SRB & gLite

1. SRB & gLite V. Breton

2. Introduction • Goal: evaluation of existing technologies for data and tools integration and deployment • Data and tools integration should be addressed using web services • Grid middlewares are dealing with workload and data management relevant to data and tools deployment • First foreseen middlewares • DEISA middleware (workload and data management) • SRB on BIRN (data management) • LCG2 and gLite on EGEE (workload and data management)

3. SRB: context • SRB is a middleware developed by San Diego Supercomputing Center • SRB is used on a large scale american project in the biomedical field: Biomedical Informatics Research Network • Federation of databases storing brain medical images • Within the framework of BIRN, SRB is possibly deployed on several sites in Europe (Spain ?, UK ?)

4. What is SRB ? • SRB is about virtualization of storage resources: the SRB client sees all the storage elements as one single storage resource

5. SRB potential interest for Embrace • SRB strong points • A reliable middleware benefitting from developments for more than 10 years • A middleware used already at a large scale for distributed medical data storage • SRB weak points • Middleware providing limited functionalities (absence of workload management) • Only anonymized information are stored • Interoperability with other middlewares ? • Expertise on SRB within Embrace • CNB, Univ. Manchester nodes of BIRN ? • LPC will use SRB to deploy an MRI platform for rare disease diagnosis • Need volunteers to further dig into SRB middleware

6. EGEE • Two middlewares • LCG2 currently deployed on the infrastructure • gLite currently under deployment on preproduction service • Main features • LCG2 has demonstrated robustness for grid computing, but lacks data management features • gLIte opens new perpectives in terms of data management and security but is just in its infancy

7. gLite Services JRA3 UK Access Services Grid AccessService API CERN IT/CZ Security Services Authorization Information & Monitoring Services ApplicationMonitoring Information &Monitoring Auditing Authentication Data Services Job Management Services MetadataCatalog File & ReplicaCatalog JobProvenance PackageManager Accounting StorageElement DataManagement WorkloadManagement ComputingElement Site Proxy

8. gLite Services for Release 1Software stack and origin (simplified) • Computing Element • Gatekeeper (Globus) • Condor-C (Condor) • CE Monitor (EGEE) • Local batch system (PBS, LSF, Condor) • Workload Management • WMS (EDG) • Logging and bookkeeping (EDG) • Condor-C (Condor) • Storage Element • File Transfer/Placement (EGEE) • glite-I/O (AliEn) • GridFTP (Globus) • SRM: Castor (CERN), dCache (FNAL, DESY), other SRMs • Catalog • File and Replica Catalog (EGEE) • Metadata Catalog (EGEE) • Information and Monitoring • R-GMA (EDG) • Security • VOMS (DataTAG, EDG) • GSI (Globus) • Authentication for C and Java based (web) services (EDG)

9. Main Differences to LCG-2 • Workload Management System works in push and pull mode • Computing Element moving towards a VO based scheduler guarding the jobs of the VO (reduces load on GRAM) • Distributed and re-factored file & replica catalogs • Secure catalogs (based on user DN; VOMS certificates being integrated) • Scheduled data transfers • SRM based storage • Information Services: R-GMA with improved API and registry replication • Prototypes of additional services • Grid Access Service (GAS) • Package manager • DGAS based accounting system • Job provenance service • Move towards Web Services

10. How to proceed ? • Encourage WP3 members (particularly test cases) to deploy applications on their local/national infrastructure and report on their experience • From the list of partners, the main middlewares should be tested: • LPC: EGEE( LCG2,gLite), SRB • SIB: Swiss BioGrid • Uppsala: Nordugrid • Cineca: DEISA • CSC: Nordugrid • CMBI: • Need for common evaluation criteria