1 / 5

LHC Delays - consequences

LHC Delays - consequences. 3 main issues: Effect on 2009 procurements Need an agreed MB position – must avoid delaying procurements Upgrades of software and services now possible That had been psotponed or were not ready Need for a concrete CCRC’09 In particular if many updates are made.

vahe
Télécharger la présentation

LHC Delays - consequences

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LHC Delays - consequences • 3 main issues: • Effect on 2009 procurements • Need an agreed MB position – must avoid delaying procurements • Upgrades of software and services now possible • That had been psotponed or were not ready • Need for a concrete CCRC’09 • In particular if many updates are made

  2. Procurements • We do not yet have • Official statement of a revised LHC schedule for 2009 • Reassessments of the experiments’ requirements based on such • BUT ... • 2009 data taking could be at the anticipated levels – or extended? • Amount of 2008 data missed could be small in comparison • Still in resource ramp up to 2009 levels – jump from 2008 to 2009 was still x2 • We know that the risk of problems is procurement/delivery is high and we must not ease the pressure to have resources in place • Experiments will continue to work with cosmics for calibration etc. • We need to resist the temptation to allow procurements to slide or be delayed • Possible exception of tape purchases ... • Unless we get a clear message about long delays from CERN management we have to maintain the existing plan

  3. Upgrades • The delay does allow the possibility to finish deployments/upgrades that had been postponed or were not ready • E.g. IN2P3 will use opportunity for infrastructure work • CERN plans (see Tony Cass’ talk) • ... • Middleware/services (see Oliver Keeble’s talk) • SL5 migration • FTS/SL4/SL5 • SCAS/glexec for multi-user pilots • Updates of storage software (Castor 2.1.8/SRM 2.8; dCache?) • Esp. Castor deployment for user analysis • CREAM ?? • But... • Should be finished by end of this year or January 2009 

  4. CCRC’09 • If significant changes are made to the services will need to foresee a concrete CCRC’09 • Timing (guess): • Accelerator for physics : June 09 • Accelerator startup : April 09 • CCRC must be March at latest (but CHEP, etc. in March) – so this might need to be mid-Feb

  5. Summary • Based on result of today’s discussion, we need to: • Draft a note explaining (to funding bodies) why we must not slow down on procurements (scale or timing) • Plans and schedules for specific deployments of middleware and services • Agree schedule and goals of CCRC’09

More Related