1 / 4

Baseline Services Group - Future

Baseline Services Group - Future. PEB 28 th 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:

diem
Télécharger la présentation

Baseline Services Group - Future

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. Baseline Services Group - Future PEB 28th June 2005 Ian Bird IT/GD, CERN

  2. 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

  3. 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

  4. 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.

More Related