1. GridPP13 Collaboration Meeting
GridPP Overview
Tony Doyle
4 July 2005
GridPP13 Collaboration Meeting

2. GridPP13 Collaboration Meeting
Contents
Technical Design Reports
Timescales
Oversight Committee Summary
Current concerns
Actions (and how these were addressed)
Feedback from the July 1 (OC7) meeting
“Get Fit” Plan and Problem Solving
Beyond GridPP2..
4 July 2005
GridPP13 Collaboration Meeting

3. June Reports
Computing Technical Design Reports:
preprints/lhcc/public/
ALICE: lhcc pdf
ATLAS: lhcc pdf
CMS: lhcc pdf
LHCb: lhcc pdf
LCG: lhcc pdf
LCG Baseline Services Group Report:
Contains all you (probably) need to know about LHC computing
4 July 2005
GridPP13 Collaboration Meeting

4. GridPP13 Collaboration Meeting
Timescales
Service Challenges – UK deployment plans
4 July 2005
GridPP13 Collaboration Meeting

5. Functionality
Requirement
OMII
VDT/GT
LCG/gLite
Other
Comment
Storage Element
Yes
SRM via dCache, DPM or CASTOR
LCG includes Storage Resource Management capability
Basic File Transfer
GridFTP
LCG includes GridFTP
Reliable File Transfer
File Transfer Service
FTS is built on top of GridFTP
Catalogue Services
RLS
LCG File Catalogue, gLite FireMan
Central catalogues adequate, high throughput needed
Data Management tools
OMII Data Service (upload / download )
LCG tools
(replica management, etc.)
gLite File Placement Service under development
Compute Element
OMII Job Service
Gatekeeper
LCG uses Globus with mods
Workload Management
Manual resource allocation & job submission
Condor-G
Resource Broker
RB builds on Globus, Condor-G
VO Agents
Perform localised activities on behalf of VO
VO Membership Services
Tools for account management, no GridMapFile equivalent
CAS
VOMS
CAS does not provide all the needed functionality
DataBase Services
MySQL, PostgreSQL, ORACLE
Off–the-shelf offerings are adequate
Posix-like I/O
GFAL, gLite I/O
Xrootd
Application Software Installation Tools
Tools already exist in LCG-2
e.g. PACMAN
Job Monitoring
Monalisa, Netlogger
Logging & Bookkeeping service, R-GMA
Reliable Messaging
Tools such as Jabber are used by experiments (e.g. DIRAC for LHCb)
Information System
MDS (GLUE)
BDII
LCG based on BDII and GLUE schema
Fits on a page. Concentrate on robustness and scale. Experiments have assigned priorities.
4 July 2005
GridPP13 Collaboration Meeting

6. July Documents Addressed various concerns of the OC
PPARC Oversight Committee Papers
Seventh GridPP Oversight Committee (July 2005)
Executive Summary
Project Map
Link to Project Map Database (Excel) Version (v2)
Resource Report
LCG Report
EGEE Report
Deployment Report
Middleware/Security/Network Report
Applications Report
User Board Report
Tier-1/A Report
Tier-2 Report
Dissemination Report
UK Analysis
Metrics and Deployment
Middleware Planning
Experiment engagement questionnaire
See
Addressed various concerns of the OC
4 July 2005
GridPP13 Collaboration Meeting

7. GridPP13 Collaboration Meeting
Exec2 Summary
GridPP2 has already met 21% of its original targets with 86% of the metrics within specification
“Get fit” plan described (requested by OC)
gLite 1 was released in April as planned but components have not yet been deployed or their robustness tested by the experiments
Service Challenge (SC) 2 addressing networking was a success at CERN and the Tier-1
SC3 addressing file transfers for the experiments is about to commence
Long-term concern: hardware at the Tier-1 in
Short-term concerns: under-utilisation of resources and the deployment of Tier-2 resources
4 July 2005
GridPP13 Collaboration Meeting

8. RAL joins labs worldwide in successful Service Challenge 2
The GridPP team at Rutherford Appleton Laboratory (RAL) in Oxfordshire recently joined computing centres around the world in a networking challenge that saw RAL transfer 60 terabytes of data over a ten-day period. A home user with a 512 kilobit per second broadband connection would be waiting 30 years to complete a download of the same size.
4 July 2005
GridPP13 Collaboration Meeting

9. GridPP13 Collaboration Meeting
gLite 1
4 July 2005
GridPP13 Collaboration Meeting

10. 100 green sites sitting on a grid
Thu 16 Jun 2005
Last week the UK CIC-on-duty team celebrated the milestone of having 100 sites passing the Sites Functional Test. Thanks to all the sites who acted promptly to trouble tickets raised by the UK team during their shift.
4 July 2005
GridPP13 Collaboration Meeting

11. Current concern 1. under-utilisation
Under -utilisation of existing Tier-1/A resources
improving overall and w.r.t. Grid fraction from 2004 to 2005
Non-Grid
Grid
4 July 2005
GridPP13 Collaboration Meeting

12. Current concern 2. under-delivery
The current situation is somewhat better than these 2005 Q1 numbers indicate
Some late procurements (OK given under-utilisation)
Technical problems (being overcome)
4 July 2005
GridPP13 Collaboration Meeting

13. Longer-Term concern: allocations
2004
2005
2006
2007
2008
2009
2010
Alloc.
Disk
CPU
Tape TB
KSI2k
kSI2k
ALICE 5 14 4 1 10 24 13 26 48 46 84 80
147
ATLAS 27
400 68
257
529
150
508
801
377
887
1571
1033
1249
2593
2026
1892
3504
2790
CMS 40 86 50
200
206 74
205
128
283
483
227
449
670
343
661
1148
503
916
1663
LHCb 15 90 25 30
108
222
104
191
384
207
644
346
450
868
714
545
1290
1178
TOTAL
191
796
239
298
1282
331
604
1604
891
1100
2167
1280
1945
3891
2316
2633
5516
4130
3641
7358
5944
LHC TOTAL 87
590 69
174
651
250
450
980
664
841
1492
1080
1484
2712
2074
2087
4206
3934
3020
5857
5710
LHC Fraction
46%
74%
29%
58%
51%
76%
61%
69%
84%
70%
90%
79%
95%
83%
80%
96%
Starting point: fair shares input to BaBar and LHC MoUs
4 July 2005
GridPP13 Collaboration Meeting

14. Metrics and Deployment
GridPP is a significant contributor to EGEE (20%)
CPU utilisation is low
Disk utilisation is climbing (but very low)
4 July 2005
GridPP13 Collaboration Meeting

15. Metrics and Deployment
Sites upgrade improvements – quarterly upgrades within 3 weeks
gradual improvement in site configuration and stability
Reflects systematic approach and measurable improvements in deployment
4 July 2005
GridPP13 Collaboration Meeting

16. GridPP Deployment Status 2/7/05 (9/1/05)
Measurable Improvements
totalCPU
freeCPU
runJob
waitJob
seAvail TB
seUsed TB
maxCPU
avgCPU
Total
2966
(2029)
1666 (1402)
843 (95)
31 (480)
74.28 (8.69)
16.54 (4.55)
3145 (2549)
2802 (1994)
4 July 2005
GridPP13 Collaboration Meeting

17. GridPP13 Collaboration Meeting
Actions
GridPP to submit the proposal for LCG phase 2 funding to the Committee prior to its submission to Science Committee (minute 4.9).
Done. 27 page report inc. input from OC at unfunded
GridPP to clarify the situation with regard to ATLAS production run tests for the next physics workshop (minute 5.3).
See News Item
(and slide)
GridPP to provide an update on progress resolving problems caused by mismatches between local batch systems and the capabilities of the grid Resource broker (minute 6.3).
(See slide)
GridPP to more fully document its alignment with each of the individual experiments (minute 15.2).
An experiment engagement questionnaire has been used (initial input in February and further [updated] input in June). See
4 July 2005
GridPP13 Collaboration Meeting

18. ATLAS steps up Grid production
4 July 2005
GridPP13 Collaboration Meeting

19. GridPP13 Collaboration Meeting
RB Action
GridPP to provide an update on progress resolving problems caused by mismatches between local batch systems and the capabilities of the grid Resource broker (minute 6.3).
The problem of connecting the local CE to a batch queue is largely overcome – many (all shared) sites now do this.
There were problems subsequently deploying the accounting system (APEL) to point to the local batch system.
Overcome (13 ex 18 sites), but not as straightforward as it could be.
The JDL from the job is not passed to the local system. Hence there is no way for the local scheduler to use info from the Grid scheduler.
This is a limitation from a (shared) site viewpoint (attempting to balance Grid and local jobs).
The short term solution is to set up separate batch queues.
It is not a limitation for the experiments (affects efficiency).
It is noted as a requirement and it is intended that this will be delivered in Year 2 of JRA1 for the WMS.
4 July 2005
GridPP13 Collaboration Meeting

20. GridPP13 Collaboration Meeting
Actions
GridPP to define its usage policy with respect to Tier-1 allocations (minute 15.4).
See and documents within (“fair shares” using PPARC Form X information)
GridPP to produce an updated risk register (minute 15.5).
Incorporated in the new Project Map at (with 7 “high” risks)
GridPP to produce a “get-fit” plan for production metrics (minute 15.6).
See Metrics and Deployment document and its incorporation into the Project Map
GridPP to define its metrics for job success (minute 15.7).
Adopted EGEE-wide definition at
(See slides)
GridPP to produce a statement of intent regarding its adoption of gLite (minute 15.8).
See Middleware Selection document
4 July 2005
GridPP13 Collaboration Meeting

21. GridPP13 Collaboration Meeting
Metrics Action
GridPP to define its metrics for job success (minute 15.7).
GridPP adopts the EGEE-wide definition at
The (web-based) QA system accounts for Workload Management System registered job successes (that can then be categorised by Virtual Organisation or Resource Broker)
Before introducing the figures it should be understood that there are caveats:
It only measures what the WMS “sees”
doesn't catch failure of WMS to register job in the first place (but this is a rare occurrence)
if a job half way through the script fails (for example tries but fails to copy a file) but the script completes successfully then WMS sees everything as OK.
If a VO (e.g. LHCb) deploys an agent then the WMS only registers the success of the initial (python) script: strategy enables higher overall LHCb performance (combined push-PULL model). (This currently leads to other problems in overall accounting should contention become an issue).
Overall: an end user may see either:
1. a worse efficiency
failed job for other hidden e.g. data management problems
2. a better efficiency by
choosing selected sites according to the Site Functional Test performance index;
deploying an agent to initiate real jobs at sites where the agent succeeded.
Physicists are “smart” and now “see” > 90% efficiency but the definition here is one defined within a given VO adopting their own methods (and from informed input from people currently submitting jobs to the system).
4 July 2005
GridPP13 Collaboration Meeting

22. GridPP13 Collaboration Meeting
Overview
Integrated over all VOs and RBs for first half of 2005
Successes/Day
Success % %
Key point: Improving from 42% to 78% during 2005
[For the UK RB (lcgrb01.gridpp.rl.ac.uk)
Successes/Day
Success % % ]
4 July 2005
GridPP13 Collaboration Meeting

23. GridPP13 Collaboration Meeting
LHC VOs
ALICE ATLAS CMS LHCb
Successes/Day N/A
Success % 42% % % %
4 July 2005
GridPP13 Collaboration Meeting

24. GridPP13 Collaboration Meeting
Other VOs
BaBar CDF D0 BioMed
Successes/Day
Success % 76% % % 76%
PMB request: please enable the BioMed VO at your site
4 July 2005
GridPP13 Collaboration Meeting

25. GridPP13 Collaboration Meeting
Interlude..
Angels & Demons introduces the character of Robert Langdon, professor of religious iconology and art history at Harvard University. As the novel begins, he's awakened in the middle of the night by a phone call from Maximilian Kohler, the director of CERN, the world's largest scientific research facility in Geneva, Switzerland. One of their top physicists, Lenoardo Vetra, had been murdered, with his chest branded with the word "Illuminati.”
Lenoardo Vetra created antimatter in canisters to simulate the Big Bang. Vetra's murder, though, allows one of the canisters to be stolen. Langdon and Vittoria Petra are quickly sent off to Rome and Vatican City, to help find the canister and return it to CERN before it explodes at midnight...
4 July 2005
GridPP13 Collaboration Meeting

26. GridPP13 Collaboration Meeting
Agents and Daemons
4 July 2005
GridPP13 Collaboration Meeting

27. The future for the experiments?
4 July 2005
GridPP13 Collaboration Meeting

28. OC Preliminary Feedback
ALL earlier actions were considered as “done” from OC perspective
GridPP to investigate alternative procurement strategies in order to improve Tier-1/A utilisation
Actions:
Tier-1/A Board
I evaluate alternative approaches
User Board – THIS MEETING
improve experiment estimates
GridPP to associate more resources for technical documentation (for end users and system administrators)
Internal advertising: is anyone within GridPP willing/able to take up the role of “Documentation Officer”?
(There will be an incentive for this)
If this fails, to advertise the post using role description (being drafted)
Deployment Board – THIS MEETING
4 July 2005
GridPP13 Collaboration Meeting

29. OC Preliminary Feedback
GridPP to develop a deployment model that works for smaller T2 centres in association with CERN
GridPP to provide a gap analysis for LCG
(using the baseline services and the [classified] experiment components as described in the TDRs)
GridPP to address UB questionnaire outcomes
(perceptions as well as actual shortcomings)
GridPP to document the high-level "value" GridPP is adding/delivering
(using Project Map)
OC8 in February 2006 “important” (not “G8 on Wednesday”)
4 July 2005
GridPP13 Collaboration Meeting

30. GridPP13 Collaboration Meeting
The “Get Fit” Plan
Set SMART (Specific Measurable Achievable Realistic Time-phased) Goals
4 July 2005
GridPP13 Collaboration Meeting

31. GridPP13 Collaboration Meeting
“I take it plea bargaining is out of the question?”
See Dave’s talk
4 July 2005
GridPP13 Collaboration Meeting

32. GridPP13 Collaboration Meeting
Our 14 problems…
0.104: Number of LCG/EGEE job slots published by the UK. The current total is 2477 and the target was 3000.
0.105: Number of LCG/EGEE jobs slots used. The current fraction is 19% compared to a target of 70%. This demonstrates that above is clearly not an issue but that usage is presently low.
0.106: GridPP KSI2K available: By the end of March 2005 the combined Tier-1 and Tier-2 CPU power was expected to be 5184 KSI2K compared to 2277 KSI2K achieved. This number is dominated by the 4397 KSI2K expected from the Tier-2s which has been slowly becoming available.
0.108: GridPP disk storage available: Similar to above. Only 280TB available compared to 968TB anticipated but the situation is improving.
0.111: GridPP tape storage made available to LCG/EGEE. At present the tape storage is being used but not really via the Grid route.
0.112: Fraction of available KSI2K used in quarter: at present a rough estimate shows about 42% of the available CPU was used compared to a target value of 70%.
0.113: Fraction of available disk used in quarter: This is estimated at 64% compared to the target of 70%.
0.114: Fraction of available Tape used in quarter: This is estimated at 61% compared to the target of 70%.
0.131: Tier-1 service disaster recovery plans up to date: This has not been updated within the last 6 months.
0.143: Accumulated scheduled downtime in the last quarter: The current value of 418 days is almost identical to the current) target of 411 days. The metric expects the 25% figure to reduce to 5% by the third year.
3.6.3: LCG Deployment evaluation reports: first report due in March 05 was delayed to the second quarter.
Tier-2 Hardware realisation: This flags the same issue as and above. Tier-2 hardware has been delayed but the situation is improving.
5.2.7 Quarterly reports received within 1 month of the end of the quarter: The 05Q1 reports were received late. Some of the delay was due to the unfortunate timing of EGEE meetings.
6.2.11: Non-HEP applications tested on the GridPP Grid (submitted via the NGS submission mechanism). The NGS submission mechanism is not yet adequate.
4 July 2005
GridPP13 Collaboration Meeting

33. GridPP13 Collaboration Meeting
The “Get Fit” Plan
… not (yet) “The Final Solution”
We hope this drives the right behaviour
Plea bargaining is (probably) OK..
4 July 2005
GridPP13 Collaboration Meeting

34. Some Problem Solving Strategies
4 July 2005
GridPP13 Collaboration Meeting

35. LHC EXPLOITATION PLANNING REVIEW
Beyond GridPP2..
LHC EXPLOITATION PLANNING REVIEW
Input is requested from the UK project spokespersons, for ATLAS and CMS for each of the financial years 2008/9 to 2011/12, and for LHCb, ALICE and GridPP for 2007/8 to 2011/12.
Physics programme
Please give a brief outline of the planned physics programme. Please also indicate how this planned programme could be enhanced with additional resources. In total this should be no more than 3 sides of A4. The aim is to understand the incremental physics return from increasing resources.
Input will be based upon PPAP roadmap input
E-Science and LCG-2 (26 Oct 2004)
and feedback from CB (12 Jan & 7 July 2005)
4 July 2005
GridPP13 Collaboration Meeting

36. Problem Solving and Improved Communication
“Communication, in essence, is the shift of a particle from one part of space to another part of space. A particle is the thing being communicated. It can be an object, a written message, a spoken word or an idea. In its crudest definition, this is communication.
This simple view of communication leads to the full definition:
Communication is the consideration and action of impelling an impulse or particle from source-point across a distance to receipt-point, with the intention of bringing into being at the receipt-point a duplication and understanding of that which emanated from the source-point..”
from The Scientology Handbook
This may be a clue to how we will overcome our problems
But we can always improve this..
4 July 2005
GridPP13 Collaboration Meeting

37. GridPP13 Collaboration Meeting
Summary
LHC Technical Design Reports define an endpoint
Responsive-mode deployment/development
Timescales for LHC are soon – first cosmics data taken
Oversight Committee – improve “efficiency”
Some particular issues:
Tier-1/A utilisation
Documentation Officer
“Get Fit” plan endorsed by OC
requires support from everyone to improve metrics
There are 14 deployment problems (some interdependency) that need to be solved
Many areas are now quantifiable (significant progress here)
Service Challenges will help focus attention
Improved communication and documentation (become a scientologist?!)
Aim: measured end-to-end performance improvements during 2005
Beyond GridPP2: input required over the summer to PPARC LHC exploitation planning review
4 July 2005
GridPP13 Collaboration Meeting