1 / 15

CERN Status and Plans

CERN Status and Plans. Maria Girone, CERN IT-DM. Outline. CERN Physics DB Services Readiness Current Resource Allocation & Usage Alarm and Problem Escalation & Handling New Requests Streams Archive DBs Plans. Physics Database Services Review. Note:

darice
Download Presentation

CERN Status and Plans

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. CERN Status and Plans Maria Girone, CERN IT-DM

  2. Outline • CERN Physics DB Services Readiness • Current Resource Allocation & Usage • Alarm and Problem Escalation & Handling • New Requests • Streams • Archive DBs • Plans

  3. Physics Database Services Review • Note: • Alice online, integration, standby and archive DBsare deployed on dual-core servers. Warranty extended for DBs at CC (to be replaced in Q1/Q2 2010) • CMS online uses 4-core servers

  4. ATLR (ATLAS Offline)

  5. ATONR (ATLAS Online)

  6. ATLR: High Load Handling • Clear trend observed of increase in resource usage for ATLR. Actions taken: • Application review with developers • ATLAS_Dashboard migration to WLCGR • Panda and DQ2 to dedicated nodes (node 3 and node 5 – node 5 added) • Reallocation of TAGS to a dedicated DB (Archive DB)

  7. ATLR: High load Issue

  8. CMSR (CMS Offline)

  9. CMSONR

  10. LCGR

  11. Alarms and Problem Handling • Alarms: • GGUS handled by CERN and Tier1 site ROCs • For CERN there will be a piquet DB (being finalized now) • Experiments and Physics DB contacts https://twiki.cern.ch/twiki/bin/view/PDBService/PhysicsDatabasesSection Ex: recent LHCb streams replication • “Team tickets” Phydb.support@cern.ch and • grid-service-databases@cern.ch for Distributed DB Operations Ex: consultancy, interventions scheduling, problems

  12. On-call team • 7 DBAs supporting the DB services • Online DB and Offline DB support is 24x7 • Stream set-up support is 8x7 • Archive DB support ?

  13. Work in Progress • ATLAS: • consolidation of ATLR to critical offline applications (Cool, Panda, DQ2) • Standby DB for ATLR • Dedicated resources to TAGS (expected increase of ~11TB/year for event TAGS, ~8TB/year for MC TAGS) on a ATLAS Archive DB • CMS • Freeze a few times per year the state of the production  database for use of re-reconstruction on a dedicated CMS Archive DB • Till new hardware arrives archive DBs are deployed on old hardware, with limited space allocation of order of 1TB. Can be increased relaxing on-disk backups (tape backups are in place  )

  14. Medium Term Plans - End of Run 2010 • Prepare the move of production DB from RHEL4 to RHEL5 • Most of validation and test DBs are already on RHEL5 • Some validation DBs will be left on the current production DB OS version for patch update validation • Started to study new features of 11gR2 within the openlab program of work with Oracle (see tomorrow) with the aim of upgrading to 11g during the 2010-2011 shutdown

  15. Conclusions • The Physics Database Services have grown significantly in the last few years • Service Size • Service Quality • User Appreciation • A robust, scalable and performing service has been built • Close collaboration with the experiments is even more important now as the real LHC workload is coming

More Related