Establishing Future Groups for Baseline Services and Technical Discussions in Grid Middleware
The Baseline Services Group has completed its first round and produced a report, but key discussions and metrics were lacking. To enhance interoperability, two distinct yet overlapping groups are proposed: 1) The Baseline Services Group will continue to address open issues, establish milestones, and monitor progress. It will consist of existing members and representatives from various middleware platforms. 2) The Technical Working Group will focus on interoperability, technical issues, and service development within the grid middleware context, meeting monthly to ensure constant collaboration and reporting to the PEB.
Establishing Future Groups for Baseline Services and Technical Discussions in Grid Middleware
E N D
Presentation Transcript
Baseline Services Group - Future PEB 28th June 2005 Ian Bird IT/GD, CERN
Introduction • Group has finished first round – report produced • But: • Did not fully discuss several items • Did not produce metrics, milestones for getting services deployed and of sufficient quality • And: • Exposed a need for technical discussion forum • Services provide a basis for interoperability – need to have a forum to pursue this • So: • We propose 2 distinct/overlapping groups as continuation
1) Baseline Services group • Continuation of the present group to: • Continue the unfinished work of the group as discussed above, and address still open issues, • Produce agreed milestones, metrics, and interface definitions for the agreed services, • Follow up and monitor progress towards these goals, • Members • Existing BSWG members • Middleware (gLite, OSG, ARC) representative (1 each) • Major Tier 1 site representatives • Closed membership – invitations for specific issues • Limited lifetime – one year? • Meet regularly • Weekly or bi-weekly • Reports to PEB regularly
2) Technical Working Group • Technical working forum, to address and agree issues, such as: • Interoperability between the different grid middleware stacks (EGEE, OSG, ARC) • Compatibility and coordination with the Applications Area projects, • Address and resolve technical issues (such as security models, storage access control, etc., etc.), specific issues that need agreement • Agree on and monitor the development, release, and deployment of services; including how services should develop/improve etc. • Members: • Experiment grid “architects” and the people responsible for integrating the experiment software with the grid middleware (baseline services). • Middleware developers (how?) • Site representation (how many?) • No fixed lifetime • Monthly meetings • Reports to PEB (as AF), input to grid projects, BSWG, etc.
