1 / 17

Quarterly report version v0.1

Quarterly report version v0.1. London Tier-2 Quarter 4 2005 Olivier van der Aa. Current site status data. To Update based on the SFT history. Local network connectivity is that to the site SE

vidor
Download Presentation

Quarterly report version v0.1

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 v0.1 London Tier-2 Quarter 4 2005 Olivier van der Aa

  2. Current site status data To Update based on the SFT history • 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 To Update based on the SFT history • 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 (Oct,Nov,Dec). 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 Quarterly report: London Tier 2 X = supported

  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/affm Numbers of KSI2K Hours: http://surl.se/affo Quarterly report: London Tier 2

  8. Storage resources in use per VO (GB) To update 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 (http://surl.se/affr) Quarterly report: London Tier 2

  10. Usage by VO (jobs) Nb: This can be extracted from APEL http://surl.se/affq 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 • Improve LT2 site efficiency • Monitor more closely the job efficiency in each site • Improve support. Finalize the Service Level Agreement document for the LT2. Top priority • SC4: Finalize SRM installation and LFC. Transfer tests between T1-LT2 and inter site transfer tests. • Test of the 2.7.0 release and upgrade. • Will test the RB component. Quarterly report: London Tier 2

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

  15. Objectives and deliverables for next quarter • With the current DPM-dCache transfer rate problem we will have to make DPM-DPM transfer to achieve acceptable rates Quarterly report: London Tier 2

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

  17. Summary & outlook Conclusion Summary from last quarter • SRM installed in most LT2 sites • Target to bring online all available hardware is achieved. See Brunel and LeSC. • VO support enhanced with the atlas software installed in all T2 sites. Essential Targets • Finalize the SRM deployment, with a tight schedule. • Prepare the SLA document to enhance the speed of solving software problems in the lt2. • Continue the SC4 transfer tests. Quarterly report: London Tier 2

More Related