LCG CCRC’08 Status WLCG Management Board November 27 th 2007

CHEP 2007 LCG Overview Conclude on scaling factors – done Conclusions on scope / scale of February challenge (resource limited)  We have feedback from the sites and can now work this out: (partial) reprocessing at sites with sufficient resources; read pass over data files including calibration DB lookup for those without  Conclude on SRM v2.2 storage setup details  Experiments to come with details on storage classes by Tier at December F2F  This will defined what is available for pre-challenge testing in January and the February challenge itself – iteration possible prior to May – practical experience certainly needed  ‘Walk-throughs’ by experiments of ‘blocks’, emphasising “Critical Services” involved and appropriate scaling factors  Details on next slide (hidden) – this is perhaps best combined with the above?  Essential for sites to understand which are the services involved and the necessary parameters for sizing / configuring the services appropriately  Also needed to understand how well we do wrt the 2008 requirements  Monitoring, logging and reporting the (progress of the) challenge  First discussion during this week’s WLCG Service Reliability workshop, conclude during F2F and GDB (possible iteration in January?)  CDR challenge in December – splitting out ‘temporary’ (challenge) and permanent data CDR challenge in December  Other tests that can be done prior to February??  De-scoping? How do we negotiate this if required?

October 9, 2007 M.Kasemann CCRC f2f planning meeting 4/10 CCRC’08 – Proposed Schedule Phase 1 - February 2008: –Possible scenario: blocks of functional tests, Try to reach 2008 scale for tests at… 1.CERN: data recording, processing, CAF, data export 2.Tier-1’s: data handling (import, mass-storage, export), processing, analysis 3.Tier-2’s: Data Analysis, Monte Carlo, data import and export  Experiments have been asked to present these ‘blocks’ in detail at December CCRC’08 planning meeting, including services (WLCG, experiment) involved as well as corresponding ‘scaling factors’  Resource availability at sites expected to limit scope / scale of challenge (e.g. not all sites will have full 2008 resources in production by then – no / reduced re-processing pass at these – e.g. read each event in the file including a conditions DB lookup?) Phase 2: Duration of challenge: 1 week setup, 4 weeks challenge Ideas: Use January (pre-)GDB to review metric, tools to drive tests and monitoring tools –This means that we must preview the metric etc already in December meeting – more later!  Use March GDB to analysis CCRC phase 1  Launch the challenge at the WLCG workshop (April 21-25, 2008)  Schedule a mini-workshop after the challenge to summarize and extract lessons learned (June 12/13 in IT amphitheatre or Council Chamber)  Document performance and lessons learned within 4 weeks. Recent CSA07 experience ‘suggests’ doing these things concurrently is indeed harder than separately, e.g. load on storage due to transfers + production

CHEP 2007 LCG So What Happens When There Are Problems?  We know well that a challenge of this scale is most unlikely to proceed without any incident / problem whatsoever  But this is a Common Challenge – by all of us, for all of us – together!  When problems arise we must report them openly and work on them systematically, using the mechanisms that have been shown to work  We have already agreed and scheduled meetings / workshops to analyze the results of the challenges – and to write up the results – but this is a somewhat longer term view…

CHEP 2007 LCG Summary  We are on track with planning / preparations  It is important that we make good progress during the December F2F  Start asap regular calls with A-P to ensure they are up to speed with status of planning and their own preparations  Thursday December 6th is the proposed date for 1 st call Thursday December 6th  Problems are inevitable – if we cannot go over them or through them, then we need to go around them