proposal for changes in the availability reports
DESCRIPTION
22 Jan 2013, WLCG Management Board. Proposal for changes in the Availability Reports. David Collados. Introduction. SAM monitoring – Current S ituation ~36 distributed OPS t ests submission instances: 4 HEP tests submission instances at CERN. Introduction. - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Proposal for changes in the Availability Reports](https://reader036.vdocuments.site/reader036/viewer/2022062305/56816587550346895dd83e1a/html5/thumbnails/1.jpg)
Proposal for changes in the Availability Reports
David Collados
22 Jan 2013, WLCG Management Board
![Page 2: Proposal for changes in the Availability Reports](https://reader036.vdocuments.site/reader036/viewer/2022062305/56816587550346895dd83e1a/html5/thumbnails/2.jpg)
2
SAM monitoring – Current Situation– ~36 distributed OPS tests submission instances:
– 4 HEP tests submission instances at CERN
Introduction
22 Jan 2013
![Page 3: Proposal for changes in the Availability Reports](https://reader036.vdocuments.site/reader036/viewer/2022062305/56816587550346895dd83e1a/html5/thumbnails/3.jpg)
3
SAM monitoring - Current Situation– OPS: CEs (ARC, CREAM, OSG), SRMv2, Site-BDII– HEP VOs: CEs (ARC, CREAM, OSG), SRMv2
• ALICE: CREAM-CE• ATLAS: CREAM-CE, OSG-CE, OSG-SRMv2, SRMv2• CMS: ARC-CE, CREAM-CE, OSG-CE, OSG-SRMv2, SRMv2• LHCb: CE, CREAM-CE, SRMv2
Introduction
22 Jan 2013
![Page 4: Proposal for changes in the Availability Reports](https://reader036.vdocuments.site/reader036/viewer/2022062305/56816587550346895dd83e1a/html5/thumbnails/4.jpg)
4
• Generating 8 monthly availability/reliability reports– Tier0/1s History (last 6 months, OPS VO)– Tier0/1s VO OPS (last 6 months, OPS VO)– 4 Tier0/1s HEP VOs (last 6 months, HEP VOs)– Tier0/1s Summary (last month, OPS+HEP VOs)– Tier2s (last month, OPS VO)
• Proposal to remove OPS tests from reports
Introduction
22 Jan 2013
![Page 5: Proposal for changes in the Availability Reports](https://reader036.vdocuments.site/reader036/viewer/2022062305/56816587550346895dd83e1a/html5/thumbnails/5.jpg)
5
• OPS infrastructure part of EGI-InSPIRE– Not sure how it will be after end of project
• OPS tests do not reflect how sites are doing for experiments
• Maintenance of OPS tests not clear after EMI• Reduce effort in availability re-computations• Homogenize and reduce number of monthly
reports
Motivation
22 Jan 2013
![Page 6: Proposal for changes in the Availability Reports](https://reader036.vdocuments.site/reader036/viewer/2022062305/56816587550346895dd83e1a/html5/thumbnails/6.jpg)
6
• Remove OPS numbers from all reports• Replace existing reports with:– One summary report per VO including T0/T1s/T2s– One history report per VO including T0/T1s
• Having similar content to existing ones
Proposal
22 Jan 2013
![Page 7: Proposal for changes in the Availability Reports](https://reader036.vdocuments.site/reader036/viewer/2022062305/56816587550346895dd83e1a/html5/thumbnails/7.jpg)
7
• Funding agencies and RRB bodies will have more than one monthly number per Site
• In case of test failure, site admins should be notified and be able to understand what the problem is based on the test output
Impact
22 Jan 2013
![Page 8: Proposal for changes in the Availability Reports](https://reader036.vdocuments.site/reader036/viewer/2022062305/56816587550346895dd83e1a/html5/thumbnails/8.jpg)
8
• Generate new reports for evaluation (March)• Review how T2s are evaluated compared to
official OPS report (March/April)– Test may need changes (more verbose)?– Follow up on open issues
• Present results and re-iterate process until confident with new reports (2/3 months)
• Decide when to switch to new reports
Adoption Plan
22 Jan 2013
![Page 9: Proposal for changes in the Availability Reports](https://reader036.vdocuments.site/reader036/viewer/2022062305/56816587550346895dd83e1a/html5/thumbnails/9.jpg)
9
Questions?