1 / 6

CMS Requirement Update and Plans

CMS Requirement Update and Plans. Lee Lueking 3D Workshop 26 January 2006. Rough Estimates of CMS DB Resources March 2007 through August 2007. Software Concerns. Some cache coherency discussion and design needed (w/ CORAL team).

evelyn
Download Presentation

CMS Requirement Update 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. CMS Requirement Update and Plans Lee Lueking 3D Workshop 26 January 2006

  2. Rough Estimates of CMS DB Resources March 2007 through August 2007 CMS Req. Update and Plans

  3. Software Concerns • Some cache coherency discussion and design needed (w/ CORAL team). • Additional calibration objects needed for some subsystems (CMS work). CMS Req. Update and Plans

  4. Production Hardware Needs • Offline Database: The RAC (CMSR) is sufficient and support has been very good. Upgrade to 8-nodes is planned and will be used. • Frontier: cmsfrontier1,2,3 • System is now in place with 3 machines, load balancing and failover via DNS Round Robin. • Limited by 100 Mbps ethernet. • Will install 2 additional Squid servers that are well connected, network-wise, to processing resources at CERN, like CMS T0 (prompt reco) farm, Grid CE’s at CERN, et cetera. • Dataset Bookkeeping Service (DBS): • Lxgate40 is current production server. • Will request additional server to load balance w/ lxgate40. • Will request additional server dedicated to Tier-0 farm. CMS Req. Update and Plans

  5. CMS Squid Deployment • Squids deployed at 30 Tier 1 and 2 sites. • Tier 1: LCG: ASCC, IN2P3, PIC, RAL, CNAF, FZK, CERN and OSG: FNAL • Tier 2:LCG: Belgium, Legnaro, Bari, CIEMAT, DESY, Estonia, CSCS, Pisa, Taiwan, GRIF, Rome, OSG: UCSD, Purdue, Caltech, Nebraska, Florida, Wisconsin, MIT + • Will install additional Tier-2, and begin installing at Tier-3 sites as needed. • Possibly 20 or 30 additional sites by August • Including: Budapest, Imperial, NCU/NTU, ITEP, SINP, JINR, IHEP, KNU, CMS Req. Update and Plans

  6. Other • Detector debugging and various calibration and alignment activities require offline databases in addition to ORCOF and Data Management. • Much of the detector construction database info is in the CERN database and this will continue to be used for detector commissioning and beyond. • We have examined the proposed 3D procedures for patch installation, and backups of the T0 Oracle installations. They seem well thought through and appropriate. We will provide additional feedback when we have more experience with them. CMS Req. Update and Plans

More Related