Enabling Grids for Escienc E INFSORI508833 Program of

Enabling Grids for E-scienc. E INFSO-RI-508833

Program of Work • Draft Program of Work: – PEB, PTF have commented. – http: //agenda. cern. ch/ask. Archive. php? base=agenda&categ=a 05 2272&id=a 052272/moreinfo • Major Sections: – Services & Interfaces Architecture review through use cases. – Requirements DB exists; ensure cycle works. – Tooling Plain web service tooling. Administration tools. INFSO-RI-508833 NA 4 Status – C. Loomis – 24/03/2005 2

Program of Work • Reporting: – PTF Recommendations Written concise proposals with rationale for recommendation. – Forwarded to Technical Director – Discussed within PEB Approve recommendation. Send back for further work. INFSO-RI-508833 NA 4 Status – C. Loomis – 24/03/2005 3

“External” Relationships • Relationships between PTF and other bodies: – – g. Lite design team Baseline Services Group GAG MWSG • Solution 1: – Cross-membership between groups. – Expect PTF members to report status & important information from other bodies to PTF. • Solution 2: (Baseline Services Group) – Need to investigate overlapping responsibilities. – Determine best method for collaboration. INFSO-RI-508833 NA 4 Status – C. Loomis – 24/03/2005 4

Sub-Groups • Prioritization of Requirements – Members: HEP, Biomed, Generic. – Timeline: next week for names; following week for feedback. – Goals: Feedback on JRA 1 proposed Po. W Identify critical requirements from DB. Identify “complex” use cases for PTF walk-throughs. • Web Service – Members: Meb, Security Experts, WS Tools experts – Timeline: 1 month for first version – Goals: Web Service cookbook. Performance of WS (with security) INFSO-RI-508833 NA 4 Status – C. Loomis – 24/03/2005 5

Sub-Groups • Use Case Tools – Members: JRA 1, Integration Team, Tool experts – Timeline: 2 weeks – Goals: Collect interfaces. Identify/verify tools for modeling/sequence diagrams. INFSO-RI-508833 NA 4 Status – C. Loomis – 24/03/2005 6

Use-Cases • Start simple: – job submission with data access – job submission with file transfer • Complex Use Cases: – identified from sub-group INFSO-RI-508833 NA 4 Status – C. Loomis – 24/03/2005 7

Direct App. Representation • Option 1: Membership of apps. in PTF – Full membership; expected to contribute like members. – Will be large increase in size of PTF. • Option 2: Standing invitation – People identified by application; standing invitation to participate. – Need to have commitment to group to work. • Option 3: By invitation – Identify people based on agenda. – More work to arrange; people may not know history of discussions. • TBD. . . INFSO-RI-508833 NA 4 Status – C. Loomis – 24/03/2005 8

Meeting Frequency • More frequent meetings: – Monthly face-to-face – Monthly phone conference • Sub-groups and active mailing lists will make the phone conferences will be more effective. • PTF remains dynamic to tackle unforeseen emergencies/issues. INFSO-RI-508833 NA 4 Status – C. Loomis – 24/03/2005 9

Expectations • The PTF should be dynamic and become the "technical pulse" of the project. • The PTF should not revise the interfaces too frequently and should do it with great care. • It is important that all the lessons learned on g. Lite by the different activities are fed back to the PTF. • We also need to formalise the SA 1 feedback process. • The requirements database is a useful tool and should address the risk of developers driving the g. Lite feature sets themselves. • The work on the metadata interfaces came as a joint effort from experiments through ARDA and JRA 1 and was a positive exercise (good model). • PTF should define priorities to drive the g. Lite release plan (workplan as input), including applications and deployment. INFSO-RI-508833 NA 4 Status – C. Loomis – 24/03/2005 10

Issues • SA 1 participation – Need strong participation. – Within SA 1 need coordinated and representative feedback. • Implementation of recommendations – Escalates to TD and PEB. – Coordination of decisions with respect to EGEE/PEB, LCG and other bodies. • PTF should be “Technical Pulse” of the project. INFSO-RI-508833 NA 4 Status – C. Loomis – 24/03/2005 11