1 / 9

Proposal for changes in the Availability Reports

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.

brendy
Download Presentation

Proposal for changes in the Availability Reports

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. 22 Jan 2013, WLCG Management Board Proposal for changes in the Availability Reports David Collados

  2. Introduction SAM monitoring – Current Situation • ~36 distributed OPS tests submission instances: • 4 HEP tests submission instances at CERN

  3. Introduction 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

  4. Introduction • 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

  5. Motivation • 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

  6. Proposal • 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

  7. Impact • 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

  8. Adoption Plan • 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

  9. Questions?

More Related