1. Xiaomei Zhang CMS IHEP Group Meeting December 14 2008
CMS Computing
Xiaomei Zhang
CMS IHEP Group Meeting  
December

2. Outline T3 resource and discussion T2 resource and discussion
CRAB and Local Batch Submission functions
CRAB Server
Site monitoring

3. T3 resource and discussion
CPU resource (96 cores)
Old: 6 machines, 48 cores; New: 6 machines, 48 cores
Storage resource
cmsd01 and cmsd02 (old:/cms/cms1, /cms/cms2, /cms/cmsmc1,/cms/cmsmc2)
/home/cms/xxx(old:/home/lhc/cms/xxx)
Backup: /home/cms/xxx, /cms/cmsd01/public/cms-software(<100G)
Login
cmsui01, lxslc(old lxplus, redhat)
Plan
Balance between local disk and SE
Directly read and write SE after SE increase to 100TB
Shut down VNC to use resource more reasonably and efficiently

4. T2 resource and discussion
CPU resource (468 cores)
Old: 104 cores; New: 364 cores
Shared with Atlas, biomed, cms
CMS 50% production, 50% analysis
In theory, 100 or so for analysis(including physics group)
In practice, 200 or more , you can get “running and queue” information from
Storage resource (20TB ->100TB)
Plans
Give local users higher priority
Establish special role for local users in CERN voms (/cms/Role=NULL->/cms/Role=Beijing)
100 or less
SE will be too high in the future
Phedex transfer(debug+prod), production, global analysis, local analysis

5. T2 resource and physics group
A nominal T2 resource:
~500 batch slots, 200TB
~ 468 batch slots(sharing) , 100TB
200 batch slots in T2_CN_Beijing
CPU
Half for simulation and half for analysis
100 for analysis in T2_CN_Beijing
Storage
Central Space 30TB(?)
MC space 20TB
Physics Group Space 60~90TB
Local Storage Space 30~60TB
User Space 1TB (20 members)
100TB in T2_CN_Beijing soon( MC space 20TB, Local Storage 30~60TB, User Space 20TB, tmp 1TB)

6. T2 association to physics group

7. Should we join physics group?
T2 physics group meeting this workshop
Advantage:
Share cpu and space resource
Higher priority
More support
Crab server
Stage out to an official area
More experience
Space management
Batch slots management
From physics point of view,…
Disadvantage:
Requirements on resources

8. CRAB and Local Batch Submission functions
CRAB used for local batch submission
Plan to release next year
Still a plan, no real actions until now
The functions included in the future
Support the input dataset reading from and the output dataset writing to the local disk
Support dataset registering in local DBS
Read or Write to SE with certificate or without certificate?
Still in discussion

9. CRAB Server standalone and client-server mode client-server mode
a server is placed between the user and the Grid
Encourage analysis users to use it
Standalone mode
Directly submit to grid as now
Maintain or not support in the future?
Still in discussion
Used for local batch submission?
guide and questions:
Get support from hn-cms-crabFeedback mailing-list
Grid
Crab server

10. CRAB Server Goals: Status:
make users to submit a large number of jobs easier
don't wait for submission, strong resubmission functionality
you when jobs are finished
know the job status easily in the web page
No limitations on the size of inputbox
Easy to maintain, extend, support
crab client would be kept as stable as possible, as simple as possible
crab server responsible for most of maintaining and extending tasks(physics group)
Status:
The first release in May this year
14 May 2008: CRABSERVER_1_0_0 has been released
Two crab servers available now
Bari and Pisa
Servers will be managed by physics groups
A common server in CERN set up soon

11. The progress in batch submission
advantage and disadvantage
Easy for functions control and debug
Difficult to maintain in the future, time consuming
plans and problems
I plan two support ways
Support the dataset reading from and writing to local disk
but can not support disk data to be published in DBS
Support the dataset reading from and writing to SE
require dcap open to nodes without certificate
or require srmcp with certificate

12. Site Monitoring New transferring link tests
At the rate of 2.5Mb/s
Too many parallel links keep SE busy
Information counted in site monitoring
CMS SAM availability
CMS JobRobot
CMS Commission links
Methods used in site monitoring
Site flag:
UNCOMMISSIONED: site unusable or very unstable
WARNING: unusable today but ok before
COMMISSIONED: usable and stable
The flag for the day depends on the metrics of the previous 7 days

13. Site Monitoring