DILIGENT CERN-CNR meeting

Wednesday 8 Feb 2006, 15:00 → 16:30 Europe/Zurich

Attendees: PA, RFM, CNR on phone

https://twiki.cern.ch/twiki/bin/view/DILIGENT/H_gLite15and30 Pedro prepared background information on gLite 3.x on twiki: - it is result of integration of LCG 1.7 and gLite 1.5 - new mw should be able to go for production * good for DILIGENT to have a stable release - new services still under development/testing will not be included in gLite 3.0 - four major consequences: 1. catalogue Fireman will not be included, functionalities provided by LFC (also include gLite I/O functionalities) 2. matadata catalogue AGMA is excluded but will be tested to be, maybe, included in future 3. Hydra (for data encryption used by BioMed) same as AGMA 4. Two WMS will be available. LCG WMS provides less functionalities than WMS (simplified implementation) but more reliable ACTION PA: check if they can talk bw them Pedro presented DILIGENT/gLite release combined timeline: Jan 20: release of gLite 1.5.0 Feb 20: development code freeze for gLite 3.0.0 Feb 30: end of testing and integration Mar 15: end of certification and deployment in PPS Mar 31: development code freeze for gLite 3.1.0 Apr 30: release of gLite 3.0.0 and start deployment at sites Apr 30: development code freeze for DILIGENT release alfa Apr 30: end of testing and integration May 31: end of certification and deployment in PPS Jun 30: release of DILIGENT release candidate Alfa Jul 31: release of gLite 3.2.0 and start deployment at sites Aug 31: end of testing and integration Aug 31: release of DILIGENT release Alfa More information: - GLite odd versions will be prototype versions and gLite even versions will be production versions - The deployment in gLite3.0 may change to YAIM (but always RPM based) - No new services will be included before gLite3.2 - After gLite 3.0 Fireman, gLiteIO, DGAS, Hydra and AMGA will: . be still available through gLite1.5 . have limited support (not yet clear the level of support) . be partially tested (only applies to DGAS, Hydra and AMGA since they are new) - The list of middleware support units is the following: .Castor2 .dCache .Data management .DPM .FTS .Glue .GridICE .Information System/GIP/BDII .LFC .R-GMA .RLS .Security Management/VOMS .Workload Management * We need to compare functionalities * We should move to the new version Three options as far as caralogue usage is concerned: 1.continue to use Fireman and ask to support 2.adapt to LFc, support is ensured 3.adopt LFc but ask EGEE for providing same interfaces as Fireman * We should use LFc and do not rely on the support provided on Fireman ACTION PA: will send information related to LFC usage * Shared concerns about partners' reaction * We should move from 1.4.1 to 1.5 in March * Install gLite 3 end of March * Practise with catalogue before, we should install it before (i.e. last week of February) * UMIT will leave the project, tasks will be moved to UniBas ACTION CERN: Organise EGEE2 presentation at next Tcom in March @ CERN Pedro explained functionalities of various services * Plans for next Tcom: - outline new releases provided by EGEE, - highlight main differences (data managent in particular) - move to new release at the end of March before the f2f meeting * we will not update to 1.5 but directly to 3.0, we should start installing needed components even before the official release * Plans for CERN-CNR collaboration: deployment starts in CNR infrastructure on March 13 and Henry come to CERN on March 20 ACTION LP: check if needed a presentation from EGEE2 to DILIGENT in occasion of next f2f TCom meeting