FTS 2.0 pilot service and schedule / actions for move to production Room: 28-R-015 At this meeting we need to conclude on experiment-testing of FTS 2.0, if we are to stick to the agreed timetable of: <P> <UL> <LI>circa 1 month testing at CERN, including 1-2 patch updates; <LI>roll-out at all Tier1s to allow for the services to be fully debugged and settled in prior to dress rehearsal activities </UL> <P> This would translate to: <P> <UL> <LI>June 11th 2007: experiments give the green light to FTS 2.0 deployment in production at CERN; <LI><B><EM>June 18th 2007: upgrade of CERN services (TBC)</EM></B> <LI>July 9th 2007: green-light to Tier1 sites to start deployment of FTS 2.0 services at their sites; <LI>July/August: settling in and debugging at sites as required; <LI>Post-CHEP 2007: full production load. </UL> <P> The current status of experiment testing / validation (AFAIK) is: <P> <UL> <LI>ALICE: ok given at June GDB; <LI>ATLAS: ok; <LI>CMS: ok; <LI>LHCb: ok. </UL>

FTS service monitoring requirements Room: 28-R-015 From CMS "top 5" issues presented to MB in Prague: <UL> <LI>transfers and queues monitor <LI>backup servers <LI>heartbeat and similar ”service-is-up" monitoring </UL> <P> Can we come to a common requirement / proposal?

Status of WLCG Q1 Tx-Ty Transfer Milestones - aka Multi-VO tests Room: 28-R-015 <P> Proposal from June GDB is to attempt Tier0-Tier1 export for one week at the following daily averages: <P> <UL> <LI>ATLAS - 650MB/s <LI>CMS - 200MB/s <LI>ALICE & LHCb - 30MB/s each </UL> <P> Any fluctuations in export rate need to be explained. <P> <OL> <LI> Demonstrate Tier0-Tier1 data export at 65% of full nominal rates per site using experiment-driven transfers <P> Mixture of disk / tape endpoints as defined by experiment computing models, i.e. ~30% tape for ATLAS; transfers driven by experiments <P> Period of at least one week; daily VO-averages may vary (~normal) <LI> Demonstrate Tier0-Tier1 data export at 50% of full nominal rates (as above) in conjunction with T1-T1 / T1-T2 transfers <P> Inter-Tier transfer targets taken from ATLAS DDM tests / CSA06 targets <LI> Demonstrate Tier0-Tier1 data export at 35% of full nominal rates (as above) in conjunction with T1-T1 / T1-T2 transfers and Grid production at Tier1s <P> Each file transferred is read at least once by a Grid job <P> Some explicit targets for WMS at each Tier1 need to be derived from above </UL>

SRM v2.2 site / experiment test schedule and July pre-GDB meeing Room: 28-R-015 <a href="http://indico.cern.ch/conferenceDisplay.py?confId=9808">July pre-GDB meeting</a>

SLC4 SL3-compatibility Worker Nodes

• Ulrich Schwickerath (CERN)

Room: 28-R-015 So far access to the SLC4 SL3-compatibility Worker Nodes has only been available through the pre-production service. CERN plans to install the SLC4 32-bit native build gLite worker node middleware now it has been released and put them under a production CE. This will take several weeks and we would like to know if/when the experiments are ready for this. Jobs which can only run on SL3 will have to request this in their JDL. See: http://goc.grid.sinica.edu.tw/gocwiki/How_to_publish_my_machine_architecture http://goc.grid.sinica.edu.tw/gocwiki/How_to_publish_the_OS_name

Up-coming service interventions Room: 28-R-015 <P> Possible slots prior to start of Dress Rehearsals and Pilot LHC run: <UL> <LI>Slot in June, e.g. June 11 (following weeks are CMS / ATLAS weeks respectively). <LI>Week of CHEP 2007?? (1st week of September) </UL> <P> Foreseen interventions: <P> <UL> <LI>Move of CASTOR DBs to better h/w (to be done by VO - service interruption involved). <EM>Now fully done - item to be removed.</EM> <LI><B>Deployment of new CASTOR version, including new LSF plug-in (ATLAS, CMS, PUBLIC, LHCb, ...)</B> <P> Proposed schedule: <UL> <LI>PUBLIC: June 12 <LI>ATLAS : June 13 <LI>LHCB : June 18 <LI>CMS : TBD <LI>ALICE : TBD </UL> <P> <LI>Oracle Critical Patch updates <UL> <LI>17 April 2007 (skipped) <LI>17 July 2007 <LI>16 October 2007 <LI>15 January 2008 </UL> </UL>

AOB Room: 28-R-015