1 / 13

OGF27 – GSM-WG roadmap

OGF27 – GSM-WG roadmap. Jens Jensen OGF27, Banff Based on work discussed at ’26. New Group Chair. After a long stint, Arie Shoshani (LBNL) retired from post as chair And Alex Sim (LBNL) as secretary Timur Perelmutov (FNAL) new co-chair. Why. How we work… Implementers show up at OGF

lise
Download Presentation

OGF27 – GSM-WG roadmap

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. OGF27 – GSM-WG roadmap Jens Jensen OGF27, Banff Based on work discussed at ’26

  2. New Group Chair • After a long stint, ArieShoshani (LBNL) retired from post as chair • And Alex Sim (LBNL) as secretary • TimurPerelmutov (FNAL) new co-chair

  3. Why • How we work… • Implementers show up at OGF • So do the users • But never at the same time • Discussions need lots of time

  4. High Level Summary Some areas still need docs: • Optional parts of protocol • Underlying storage differences • Within the spec • E.g. extra placement data, or spaces • HTTPS roadmap

  5. Users • WLCG • SNIA – Cloud • “StoRM in front of S3”

  6. Issues • Are users using SRM most effectively • “SRM is too complex for us” • But problem is complex • “We want to use the richer functionality” • “It is slow” • But they are not using it effectively

  7. Role of GSM-WG discussed • Most see need for standards • However, also busy with WLCG • Roadmap discussed • Getting clearer: change to CG

  8. Scope of Group • Storage Element • SRM is the control protocol • GridFTP (&c) for data transfer • GLUE for info

  9. Scope of Group • SRM 2.2 standardisation • GFD.129 • Experiences (GFD.154) finalised • Two standard test suites • Interoperation testing • Documents reviewed by ext’l reviewer

  10. Meta-Issues • Many mailing lists and working groups • gsm-wg itself has low volume • Less direct activity now, more boundary • Various levels of contributions at OGF • A Few Good (Wo)Men – which is good • Occasionally many tourists – also good

  11. OGF contributions • Not just WLCG (openness) • Eg financial, biomed, earth systems, fusion • Mostly sites and devs though • Many dCache people providing good input • Industry (SNIA) EoI via data mgmt

  12. Option chosen: • Long list of issues, see OGF 22 and 23 • New implementations coming along • WLCG will change requirements • Will SRM 2.2+, 2.3 or 3.0 be implemented? • Keep it open • As an alternative to CERN coffee breaks • *Cough*, I mean GDB of course

  13. Not included (?) • SRM security – httpg vs https vs khttp? • Take data transfer on board • Strong req for xrootd standardisation • GridFTP req’d by all SRM impl • https-as-a-transfer-protocol (Paul) • Interop activities • Eg NAREGI, SRB, iRODS

More Related