T2_CH_CSCS CMS Information

User Information

• User Information: Help and examples on how to work on the CSCS Tier-2
• Tier-2 to physics groups associations
  • Currently, T2_CH_CSCS is associated to the b-physics group, only

Administrator information for running the local site

• CMS site contact's shifter information: Daily interactive checks for our site's health
• CMS Site Log for T2_CH_CSCS
• CmsVObox
• Data sets to keep/delete table - used in querying users as to what can be deleted
• CMS Software area (structure, setup, verification)
• CMS SiteDB: CMS database with site information. Here we also need to put our resource pledges for each quarter.
  • Q32010: CPU 1200 kSI2k (12000 HEPSPEC06 /4 = 3000 kSI2k. From this value 40%), 300 job slots, and 250 TB disk from our 300 TB total share.

External admin relevant information

• Indico space for the CMS Facility Operations Wiki / meetings
• Operational Procedures for CMS Sites from the central CMS wiki
• T2 admin guide from the central wiki

CMS Requirements

• Batch system related requirements
  • Heavy ion production users
    • CMS wants to introduce role=hiproduction for the MC production of heavy ion events (q.v. Talk by T. Kress). Most probably we just can map them to the existing cmsprod pool accounts (depends on local communities. TODO: ask Swiss community).
  • Priority users
    • A limited number of users for every CMS physics group can take the Priority User VOMS role (role=priorityuser). These should be mapped to a group of local system users (e.g. priorityuser01, ...). These should get a higher priority than normal CMS users. Current proposal is to give the sum of the (few) priority users the same priority as the sum of the CMS analysis users: production / priorityuser / analysisuser = 0.5 / 0.25 / 0.25. Questions can be asked from hn-cms-analysisoperations@cern.ch.
    • central Twiki page indicating readiness, to be filled out by us. Also, look at talk by T. Kress at FacOps 2009-09-28
• CMS job I/O requirements
  • 2009-06-18 Ian Fisk reports on CMSSW I/O campaign in PADA meeting. Aim is to increase CPU efficiency while trying to keep I/O as low as possible.
  • 2009-03-30 Ian Fisk's Talk on specific dCache issues mentions CMS I/O bound jobs requiring 3 MB/s of data.
• Storage related requirements
  • Storage organization and sizing for CMS
  • requirements on the namespace setup (smaller table)
  • VOMS role=production must be able to write to /store/results/ path
  • VOMS role=priorityuser must be able to write into /store/group/ path

Interesting Talks and links on Tier-2 relevant technologies

• Tier-2 Storage organization
  • Ian Fisk's slides from Computing Integration Meeting Jul 16th 2008. This defines a schema of storage classes and sizes.
  • Ian Fisk's slides from PADA Meeting of Sep 4th 2008 with Tier-2 to physics groups associations.
  • Ian Fisk's slides from CMS week of Sep 25th 2008. Contain descriptions of storage policies and group mappings.
• Three tech talks on SE technologies from the CMS offline workshop 2009-04:
  • GPFS/Storm
  • Lustre/dCache
  • Hadoop
    • Hadoop OSG site: https://twiki.grid.iu.edu/bin/view/Storage/Hadoop
• dcache to Lustre/Storm comparison by Giacinto Donvito at the CMS offline workshop 2009-10
• Information on pilot jobs

old information

• Status of Summer08 Monte Carlo production
• obsolote Analysis Group page on CERN twiki

-- DerekFeichtinger - 24 Apr 2009