1 / 12

Updates on GridPP Storage Status and Deployment Support for User Experiments

On July 12, 2007, the Joint GridPP Board discussed the current status of storage systems used across various sites. Approximately two-thirds are running DPM, while one-third utilizes dCache, with some support ongoing for CASTOR and StoRM as well. The GridPP community comprises around 50 members from various countries and maintains robust collaboration. Key topics included proactive support, monitoring, accounting, storage performance, and recent developments regarding security vulnerabilities. The meeting emphasized the importance of stability and ongoing efforts to enhance storage and computing resource efficiency.

yon
Télécharger la présentation

Updates on GridPP Storage Status and Deployment Support for User Experiments

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. GridPP storage status update Joint GridPP Board Deployment User Experiment Update Support Team, Imperial 12 July 2007, j.jensen@rl.ac.uk

  2. Status • Everybody running DPM or dCache • In some cases, and • Roughly 2/3 running DPM, 1/3 dCache • Unless not: • 3-4 CASTOR, 1 StoRM

  3. Support • Community with about 50 members • Includes members from Ireland, Germany, Canada, Poland, Italy, CERN • Weekly VRVS meetings, mailing list, wiki, blogs • Good relations to developers

  4. Migration Proactive support Stability Monitoring Accounting Other SRMs Usable storage CPU to storage ratios Security Upgrades Filesystems Issues Overview (randomly)

  5. Migration GLUE 1.3 SRM 2.2 …GLUE 2.0 Interoperability, testing “Proactive” support Short 1+ staff Help sites getting stuck (not naming names) Sites going AWOL (no stick) Issues Details

  6. Stability Keep SE running & happy Software – robust vs feature Monitoring & Acct. <Repeat usual discussion> Shared available space Account by VO subsets Issues Details

  7. Other SRMs Bristol on StoRM CASTOR, CASTOR, CASTOR, and CASTOR CPU/Storage ratios Most Atlas and CMS sites short Does anyone care? If yes, what do we do…? Issues Details

  8. Security SSC (Alessandra) Recent DPM vuln. Upgrades Regular, ongoing Trivial to non-trivial E.g. db schemas Manual vs YAIM Issues Details

  9. Filesystems Optimised Investigations Distributed Not supported But required? Usable Storage Performance WN-to-SE LAN Metrics Stability Experiment experts Issues Details

  10. Loose ends • Contributions to Grid storage m’ware • Information systems (GIP), accounting • Upstream: Documentation, testing • Dissemination, publications, demos • NGS Engineering Task Force (Jens) • Evaluated DPM (also for Solaris) • Distributed filesystems (AFS eval., GPFS?)

  11. Other Contributions • LCG • SRM testing community, WLCG GSSD • CASTOR • International standards • GSM-WG, GLUE-WG

  12. Conclusions • Lots of DPM expertise (Graeme, Greig), dCache expertise (Derek, Greig) • Plus SRM, GLUE, filesystems expertise • Publications & disseminations • Regular significant support issues (no asymptotic smoothness)

More Related