1 / 17

Quarterly report version v1.0

Quarterly report version v1.0. London Tier-2 Quarter 3 2005 Olivier van der Aa. Current site status data. Local network connectivity is that to the site SE It is understood that SFT failures do not always result from site problems, but it is the best measure currently available.

oralee
Download Presentation

Quarterly report version v1.0

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. Quarterly report version v1.0 London Tier-2 Quarter 3 2005 Olivier van der Aa

  2. Current site status data • Local network connectivity is that to the site SE • It is understood that SFT failures do not always result from site problems, but it is the best measure currently available. Quarterly report: London Tier 2

  3. All GridPP Resources • The GridPP-Tier-2 MoUs made reference to integrated CPU over the 3 years of GridPP2. Under the “Promised – integrated kSI2K hours until this quarter” an estimate is provided of what the Tier-2 would have expected to provide to this quarter on the basis of planned installations. “Static kSI2K” shows what would currently be expected if all purchases planned to this quarter had been made and implemented. The actual columns show what has been delivered. • The Promised Integrated kSI2K days is computed on a 92 day basis (July,Aug,Sep). Integrated KsI2K days=KSI2K(Promised CPU)*92+Integrated KSI2K days(last report) • The Actual Integrated KSI2K days (AKSI2KD) is computed as: AKSI2KD=KSI2K(Actual CPU)*(Number of Days SFT OK)+AKSI2KD(Last report) Quarterly report: London Tier 2

  4. LCG resources Estimated for LCG: Not clear how to obtain. Numbers are from previous report 1) The estimated figures are those that were projected for LCG planning purposes: http://lcg-computing-fabric.web.cern.ch/LCG-Computing-Fabric/GDB_resource_infos/Summary_Institutes_2004_2005_v11.htm 2) Current total job slots are those reported by EGEE/LCG gstat page. Quarterly report: London Tier 2

  5. VOs supported by site X = supported Quarterly report: London Tier 2

  6. CPU used per VO over quarter (KSI2K hours) • Information currently available from APEL • http://goc.grid-support.ac.uk/gridsite/accounting/tree/gridpp_view.php- please note these pages are • still under development! • NB2: couldn’t get these to agree with the normalised CPU hours on the next slide!!! Quarterly report: London Tier 2

  7. Usage by VO for Tier-2 Numbers of Jobs per VO: http://surl.se/txy Numbers of KSI2K Hours: http://surl.se/txz Quarterly report: London Tier 2

  8. Storage resources in use per VO (GB) Difficult to provide this for the period but we can at least show *current* usage. Numbers need to be provided by site Admins (> du – sh) but this will change under dCache. Quarterly report: London Tier 2

  9. CPU Usage by VO (KSI2K hours) Nb: This can be extracted from APEL – http://goc.grid-support.ac.uk/gridsite/accounting/custom.php Quarterly report: London Tier 2

  10. Usage by VO (jobs) Nb: This can be extracted from APEL Quarterly report: London Tier 2

  11. Progress over last quarter Quarterly report: London Tier 2

  12. Tier-2 risks • Here “risk” is any significant event (which has a reasonable chance of occurring) that could potentially prevent the Tier-2 from meeting its project commitments. For example, not getting expected funding to fund equipment/infrastructure is a reasonable risk whereas loss of all staff is not. Quarterly report: London Tier 2

  13. Tier-2 planning for next quarter • DPM installation for QMUL. • Test with large disk (20TB) • Finalize the move to 2.6.0. • Test of the 2.7.0 release. • Really need to know when it will be there. • SLA document for the LT2. • Uniformisation of the VO supported in the LT2 Quarterly report: London Tier 2

  14. Objectives and deliverables for last quarter Quarterly report: London Tier 2

  15. Objectives and deliverables for next quarter Quarterly report: London Tier 2

  16. Meetings, papers & effort For Tier-2 coordinator: Quarterly report: London Tier 2

  17. Summary & outlook Conclusion from last quarter • Migration to 2.6.0: We need a upgrade plan for the upcoming releases. Especially for big sites like QMUL. • SC3. Could sustain 480 Mb/s Essential Targets • All sites ready with an SRM implementation for SC4 • All sites supporting the same set of VO • Bring all available resources into LCG. (IC-LeSC SGE-LCG integration, Brunel). Quarterly report: London Tier 2

More Related