1 / 21

EGI: A European Distributed Computing Infrastructure

EGI: A European Distributed Computing Infrastructure. Steven Newhouse Interim EGI.eu Director. The EGI Context. EGI Collaboration. Research Community. Research Community. Research Community. N G I. Research Community. N G I. Research Community. E I R O. E I R O. N G

afra
Download Presentation

EGI: A European Distributed Computing Infrastructure

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. EGI: A European Distributed Computing Infrastructure Steven Newhouse Interim EGI.eu Director

  2. The EGI Context EGI Collaboration Research Community Research Community Research Community N G I Research Community N G I Research Community E I R O E I R O N G I N G I EGI.eu

  3. EGI.eu • Coordination for European HTC • Policy & services needed to run a grid • Governance by its stakeholders • EGI Council votes proportional to GDP • Owned by its stakeholders • EGI Council fees proportional to votes • Location selected to be Amsterdam • Distributed staffing model • Approximately 51 staff, 4.59M€/year

  4. How much does it cost?

  5. How to make e-Infrastructuresustainable? • Minimise what you need to sustain! • Be a middleware customer, not a developer • Be a service provider, not a research organisation • Don’t control resources, work with resource providers • What does that leave for EGI.eu? • Services that do not fit nationally or in a community • Management & technical expertise for it all to work! • Recognise that we are transitioning to this goal! • Process started in EGEE-III

  6. DANGER Proposal Under Construction

  7. The EGI-InSPIRE Project Integrated Sustainable Pan-European Infrastructure for Researchers in Europe • A proposal for an FP7 project • Work in progress..., i.e. this may all change! • Targeting call objectives: • 1.2.1.1: European Grid Initiative • 1.2.1.2: Service deployment for heavy users • Targeting a 3 year project • Seeking a total 25M€ EC contribution

  8. EGI-InSPIRE Objectives • Transition to a sustainable federated European e-infrastructure built from national resources • Deliver production quality services to all its user communities and users • Provide a scalable user support model for international research communities within Europe and their worldwide collaborators • Interoperation and interoperability with other e-infrastructures

  9. EGI Project Ecosystem Community Supporting Projects SSC SSC Support Centres Community SSC SSC EGI SSC EC Projects Software Providers Software Providers Software Providers

  10. Project Structure External Relations: Policy, Dissemination and Standards Software Provisioning and Support Operations and Tools User Support and Services SA2 Middleware Unit JRA1 Operational Tools NA3 User Support SA3 Software Support SA4 Services for HUCs SA1 Operations Project Management

  11. Project Structure Technical Collaborations (e.g. CHAIN, GISELR, OGF-EUROPE-II, ...) EGI-InSPIRE Software Projects (e.g. EMI, ...) SSC Projects (e.g. ROSCOE, SAFE, CUE, Application Porting SSC, ...) Managerial Collaborations (e.g. EC, DEISA, OSG, ...)

  12. External Relations: Policy, Dissemination and Standards • Dissemination internally & externally to EGI • Development of EGI’s sustainability model • Co-ordinatingEGI’s standards activity • EGI Policy development for governance, middleware, security, operations & user communities • Two large annual events to promote collaboration within European DCI • In collaboration with PRACE/DEISA & others

  13. User Community Coordination & Support • Coordination of effective, responsive support for the EGI user communities (reactive) • Coordination of training, documentation and technical requirements from the user communities (proactive) • Technical services to: • Support the management and establishment of virtual organisations • Deployment and Support of services & tools to support Heavy User Communities (HUCs)

  14. Operations • Providing a Reliable Grid Infrastructure • Availability of Skilled Support Teams • Service Deployment Validation • Providing a Secure Infrastructure • Accounting for Resource Usage • Helpdesk Infrastructure • Infrastructure for Grid Management • Regionalisation of the Operational Tools

  15. Who does what in EGI? • Internal National Infrastructure & Activities • Infrastructure that is not visible internationally • Activities with no external dependency • NGI International Tasks • The ‘service’ interface to your national grid • Community defined that EGI will enforce • EGI Global Tasks • Provided by EGI.eu through community partners • Services needed for the whole EGI community

  16. EGI Software Infrastructure • Recall some design facts: • EGI federation of national grid activities • EGI is not developing middleware • EGI does not control the resources its users use • As a consequence: • EGI will need to integrate different middleware • EGI needs to identify interoperable solutions • EGI must work with multiple software providers and deployments to achieve itsgoals

  17. EGI Software Infrastructure Software Provider Software Provider Software Provider Software Component Software Component Software Component Software Component 3rd Line Support Agreement Middleware Collaboration Board • End-Users • Software Providers • Resource Providers EGI Software Repository Compatible Component Rejected: Failed quality criteria 2nd Line Support Unified Middleware Distribution Other Middleware Distributions Fully Supported Software Component Community Supported Software Component Software Component

  18. Software Infrastructure Provision • Define and maintain the UMD roadmap and the relationship with the software providers • Define the quality criteria that will be applied to all and specific software components and verify they are achieved • Provide a repository for the software components within UMD and the related support tools and structures • Second line support for deployed software

  19. EGI @ EGEE’09 • Tuesday: • 11am: EGI InSPIRE Workshop • 2.30pm: EGI Governance models • 7pm: EGI Gateways Project • Wednesday: • 9am: SSC Project Plenary • 2.30pm: Heavy User Communities (in HEP SSC Session) • Thursday: • 9am: EMI Project Plenary • 11am & 2.30pm: EMI & UMD Workshop • Friday: • 8.30am: SSC Projects Workshop

  20. EGI Timeline • 30/9/09: Feedback from current draft & EGEE’09 due • 16/10/09: Deadline for submitting requests for Letter of Support • Process being finalised this week • 23/10/09: EGI Council meeting • Letters of support approved • 24/11/09: Final proposal submission • Spring 2010: Launch of EGI.eu • May 1st 2010: EGI project starts

  21. Summary • EGI is a collaboration for HTC in Europe • Provide a sustainable European e-Infrastructure • Strengthen support for HPC user communities • EGI.eu is the coordinating organisation • Being established in Amsterdam • Launch Spring 2010 • 3yr FP7 Project being prepared for 25M€ • Continue and complete the transition to EGI

More Related