100 likes | 291 Views
SRM Annual Meeting. Attendees Olof Barring, CERN Jean-Philippe Baud, CERN James Casey, CERN Peter Kunszt, CERN Andy Kowalski, Jlab Don Petravick, Fermilab Timur Perelmutov, Fermilab Matteo Melani, SLAC Junmin Gu, LBNL Alex Sim, LBNL Arie Shoshani, LBNL. Meeting Location: LBNL
E N D
SRM Annual Meeting Attendees Olof Barring, CERN Jean-Philippe Baud, CERN James Casey, CERN Peter Kunszt, CERN Andy Kowalski, Jlab Don Petravick, Fermilab Timur Perelmutov, Fermilab Matteo Melani, SLAC Junmin Gu, LBNL Alex Sim, LBNL Arie Shoshani, LBNL Meeting Location: LBNL Sept. 1-2, 2004
Agenda Wednesday, September 1: 9:00 am - 12:30 pm Session 1:SRM-Basic Presentations and discussions on the desirability and features of an SRM-Basic. This is a concept submitted to GGF in the GSM-WG charter. We will also discuss what features should SRM-Advanced include. The relationship of SRM-Basic and SRM-Advanced to SRM v1.1 and v2.1, and future SRM versions will be discussed as well. 10:30 am – Break 12:30 pm - 2:00 pm Lunch Break 2:00 pm - 5:30 pm Session 2: Experience with SRM implementations Presentations and discussions on implementations of SRMs, including SRM v1.1 and SRM v2.1. Discussion should include: missing features, unnecessary features, enhancement to current specs, features that are hard to implement, etc. 3:30 pm - Break 5:30 pm - Adjourn Thursday, September 2: 9:00 am - 12:30 pm Session 3: SRM v3.0This session is open for discussion of advanced features we currently do not have in SRM v2.1. This includes, but not limited to the interaction of SRMs with Virtual Organization Managers (VOMS), authorization, ACLs, accounting, and storage usage optimization. 10:30 am - Break 12:30 pm - 2:00 pm Lunch Break 2:00 pm - 5:30 pm Session 4: SRM and WSRFWSRF is a framework that includes multiple services (such as notification service). Specifying an SRM interface in this framework depends on which services one assumes to use. The issues to be discussed are how to specify generic SRM interfaces, and have specific WSRF interfaces interoperate. We may also discuss the possibility of interoperability of web-services-based SRM interfaces and WSRF-based interfaces. 3:30 pm - Break 5:30 pm - Adjourn
Experience with SRM ImplementationsProblem with specimplementation difficulties
SRM-Basic • SRM-Basic • Presentations/discussion • Arie (Alex’s slides) – general approach to versions • Olof – Basic proposal • Alex – combined Olof’s and other enhancement • Arie – features discussion (original table) • Peter - suggestion
Experience with current versions • Maturity and experience • Don/Timur • Andy on 2.1.1 • Alex 2.1.1. • with SRM 1.1 • Presentations/discussions • Alex Sim • Olof Barring • Need guidelines for how long to keep requests after they are finished • Get involved in Glue schema • Reference GSI module • Reference test suites • Peter Kunszt • with SRM 2.1 • Presentations/discussions • Junmin Gu + Alex Sim • Jean-Philippe Baud/James Casey
SRM-Basic Relationship to SRM v1.x, v2.x and SRM-Advanced
SRM v3.0 • Authorization • Accounting • Late binding of get and copy • Provide an ordered list of source SURLs)
SRM and WSRF • How to take advantage of framework? • What is the effect on the SRM interface • Advantages to SRM?
Problems with SRM 2.1 • How to assign directories to Permanent space (e.g. HPSS) x x y y F1(V) SRM logical directory z z F2 (v) F4 (P) F3 (v) F4 (P) Volatile Space home HPSS permanent Space Foo1 Foo2 Foo3
Problems with SRM 2.1 • Size of returns from SRM • e.g. status, ls • Given {offset,count} – what is default size limit? • If size limit exceed – what is error (too many results?) • A dedicated port for SRM • add recursiveLevel etc in get/copy requests since they take directories.