EGEE is a project funded by the European Union under contract IST “The LCG ARDA prototypes” Workshop summary Organised by ARDA and the gLite team Frederic Hemmer Massimo Lamanna Erwin Laure Dietrich Liko 3 rd ARDA workshop, CERN, October

3 rd ARDA Workshop Massimo Lamanna 2 Key points  Original title: “The LCG ARDA prototypes”  Open participation Good moment to get feedback from a wider audience Preparatory work for the LHCC comprehensive review 60 persons present  ~50% of the time allocated to ARDA and the LHC experiments Expose and discuss status and plans Feedback to gLite  ~50% of the time allocated to gLite Present in detail key components Expose status and plans Use the feedback  Virtual connection with OSG (Workshop at FNAL) Learn more on OSG itself Broaden the technical discussions Create a link inside our community 15 persons at FNAL

3 rd ARDA Workshop Massimo Lamanna 3 Format of the workshop Wednesday the 20 th Thursday the 21 st Friday the 22 nd 9:00 – 12:30 ARDA prototypes LHC experiments distributed analysis Discussion on gLite Release Plan and Summary 14:00 – 17:30 gLite middleware OSG from FNAL

3 rd ARDA Workshop Massimo Lamanna 4 ARDA Prototype (Wed morning) Importance of users (“naïve users”) out of questions  Users will come if/when enough hardware available  Deployment plan unclear No deployment representative  Extension of the prototype (as interim before the pre-production service arrives…) In principle it is the good direction Inherent risk to stay with a “prototype” The ARDA prototype should present the services described in the Design Document as soon as possible Metadata presentation  Generally well received  Interface owned by gLite  Room for activity in ARDA (i.e. with the experiments and with gLite)  Probably an efficient implementation will need strong connection with the file catalog  Many systems evaluated: add our independent assessment of OGSA-DAI

3 rd ARDA Workshop Massimo Lamanna 5 gLite (Wed and Thu afternoon) Overview of gLite system  Remarkable that a lot “has been written down” (allows discussions)  Key components in specific presentations  “Preparation” of the systematic discussion (gLite release plan) General concern parallel activities could slow down the evolution  Parallel activity not asked by the management Interesting ideas shown in the DM presentation  Many open points open, for example, conflict resolution in file catalog updates  Nobody really like “internal” interfaces to be “hidden” (StorageIndex) Long discussions on WMS  Connection with the DM missing (and needed to make useful evaluation)  Presently 2 systems: one for “pull” and one for “push” (the latter capable of “push” and “pull” although “pull mode” not yet really available from the CE) Overview on R-GMA  Being deployed in LCG2  Re-engineered version for gLite Presentation of gLite PackageManager (status and plans)  Lot of interests and different points of views And potential problems  Is it possible to converge on a “version 1” soon? Involvement of Experiments software team, Grid deployment team, Middleware and Users  GAG is working on this

3 rd ARDA Workshop Massimo Lamanna 6 Experiments session (Thu morning) ATLAS  Fireman too complex and too simplistic at once... More iteration needed  Discovery services needed (ATLAS is evaluating Clarence)  Full WMS service is central  SRM is central as well  Open to use anything else could be proven useful (e.g. PackageManager) LHCb  Advocate their strategy to start with batch  ARDA activity seems very coherent  Role of POOL catalog (I/F to the catalogs). Requires implementation to use gLite catalog Could be something for ARDA?  Enlarge the prototype first, exchange/experiment other components later (no change gear) CMS  Explanation of the current strategy  Need to start on LCG2 for enable users to perform their analysis  More information needed on the status (and plans) of the middleware  Need a realistic plan to bring users on the test bed ALICE  Resume of current activity  Decision to do DC04 (Phase 3) on gLite if possible (“complete” system + resources)  Offer to deploy gLite prototype “as it is” on the ALICE sites

3 rd ARDA Workshop Massimo Lamanna 7 OSG Session Experimental joint meeting ARDA/gLite/OSG Presentation of the OSG approach  Complementary approach with gLite  Mutual benefit in the evolution Technical discussions  Interoperability Tentative roadmap:  Yes, we would like to have such meetings regularly  Next one could be Dec (OSG meeting already scheduled)  Discussion on some topics just started (should be continued and prepared before next meeting) Role/usage of GUID (Provenance, mutability, etc..) Namespace VO issues (light weighted VOs, groups, service deployment vs VO infrastructure) Security model

3 rd ARDA Workshop Massimo Lamanna 8 Experiments session Other threads…  Communication gLite/experiments Established! (but some acknowledgment missing…)  Interactivity Should be built in from the beginning (Rene) Not very different from a fast-response batch (David) A working “batch” would be already a good step forward (Philippe)  General complexity Too many levels (complexity could be a killer)

3 rd ARDA Workshop Massimo Lamanna 9 Draft schedule for pre-production service gLite I/O – Today Logging & Bookkeeping, WMS, CE, WN – In testing – end October CE-Notification – In integration – mid/end November R-GMA – In integration/testing – mid November Replica, File, Combined Catalog – In development – December File Transfer Service – In integration – December File Placement Service– In development – December VOMS – In integration/testing – December UI–In integration – December AliEn TQ & CE–In integration Package Manager – Discussions w/experiments, deployment – prototype exists Grid Access – Prototype exists – discussions on semantics ongoing Accounting (HLR)– In integration – Prototype exists Job Provenance – Proof of concept exists From JRA1 (E. Laure)

3 rd ARDA Workshop Massimo Lamanna 10 Future of the ARDA workshop  Unique for putting in contacts the gLite team and the experiments A bit long (2 and ½ days); could be done more efficient? Unique to get the big picture (interactivity, complexity …) Service providers should be present Promising as bridge with other initiatives (OSG) There is always another meeting at the same time… Traveling is expensive and inefficient…

3 rd ARDA Workshop Massimo Lamanna 11 Future of the ARDA workshop Two-level system  One workshop every 6-12 months ~2 full days Synchronise with other events/milestones CERN is the good location (one travel multiple contacts – within the experiment, within other components of the projects, etc…) Fix dates looong before Next one will be end of June  One meeting every fortnight ~2h Regular pace (“re-use” existing slots) VRVS Usable to connect with OSG meetings  Open meetings, open participation

3 rd ARDA Workshop Massimo Lamanna 12 ARDA Workshop conclusions LCG2 is an essential components for the LHC experiment during 2005  Essential for the experiments to successfully carry on their activity as requested  Hardware and support More computing resources clearly needed for the gLite-based system:  To allow more users to get experience with the system  To allow the deployment team in contact with the new middleware (experience and feedback)  The feedback (on a realistic scale system) will be fundamental for the mw team  And to allow the 3 components to “look to the same system” 3 components: Users, Deployment and Middleware communities Proposal:  Refocus the Pre Production Service Use the existing LCG infrastructure Involve the GD team Install the present software pre-release on a large number of sites with substantial resources –Provided that it does not interfere with the current LCG activity –The proposed time scale is November 2004 ALICE offer to help to deploy gLite prototype “as it is” on the sites of the ALICE VO  ARDA team will move part of their activity on the Pre Production Service (to help users) and will keep access to the prototype for evaluating new versions