1 / 30

EGI Operations and Security

EGI Operations and Security. Tiziana Ferrari (Istituto Nazionale di Fisica Nucleare) Tiziana.Ferrari@cnaf.infn.it. Disclaimer. These slides have been drafted based on the current version of the EGI Blueprint proposal (v1.2, 25 June 2008).

eshe
Download Presentation

EGI Operations and Security

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 Operations and Security Tiziana Ferrari (Istituto Nazionale di Fisica Nucleare) Tiziana.Ferrari@cnaf.infn.it

  2. Disclaimer • These slides have been drafted based on the current version of the EGI Blueprint proposal (v1.2, 25 June 2008). • The purpose of this blueprint is to assess a possible model for the future sustainable grid infrastructure in Europe. • The aim of these slides is to support the discussions in the EGI Geneva Workshop (30 June 2008). • The EGI_DS project will modify this draft blueprint on the basis of feedback provided. EGI Operations and Security

  3. Outline • Players • Activities: EGI.org critical services and NGI international tasks • Funding • EGI Operations Model • Effort • Summary EGI Operations and Security

  4. EGI Operations and Security Players: EGI.org • EGI.org: • coordination of operations and security across countries • central user support • operation/maintenance of central operational tools and services EGI Operations and Security

  5. EGI Operations and Security Players: NGIs • NGIs are expected to: • operate secure Grid infrastructures in the countries • coordinate Grid operations in the countries • collaborate to the definition of common operational procedures, policies, standards/specifications • adhere to standards/specifications to ensure interoperability • support users and operational problems EGI Operations and Security

  6. Federation of NGIs • Operation of the European Grid infrastructure is currently guaranteed by the Regional Operations Centres (ROCs) – one ROC for several countries (NGIs) or corresponding to a single large NGI • Increasing push towards increasing responsibility and autonomy of the NGIs, but federation continues to be a viable model in EGI for economy of scale EGI Operations and Security

  7. Outline • Players • Activities: EGI.org critical services and NGI international tasks • Funding • EGI Operations Model • Effort • Summary EGI Operations and Security

  8. EGI.org Critical Services • Mandatory services needed to ensure: • inter-domain interoperation in the pan-European infrastructure, i.e. to keep a consistent operational model across European countries • ease of access and effective usage of the infrastructure by international user communities • can be delegated to one or more NGIs or other organizations as deemed necessary: many critical services already under the responsibility of many Regional Operations Centres in EGEE • EGI.org Operational Unit will be responsible of: • coordination • running those critical services for which central operation will be decided (list to be defined) EGI Operations and Security

  9. NGI International Tasks • technical services under the responsibility of the NGI which are needed • to support international user communities • to ensure cooperation with EGI.org and other NGIs • to allow the integration, operation and sharing of NGI resources at pan-European and international level, as adherence to common policies and specifications/standards is highly needed in a distributed environment • Note: NGI tasks to support local user communities and to satisfy local needs, areout of the scope of EGI EGI Operations and Security

  10. EGI Operations =EGI.org critical services + NGI international tasks EGI.org critical services NGI international tasks NGI local tasks EGI Operations EGI.org NGI NGI NGI NGI EGI Operations and Security

  11. Outline • Players • Activities: EGI.org critical services and NGI international tasks • Funding • EGI Operations Model • Effort • Summary EGI Operations and Security

  12. Funding • EGI.org critical services: • Initially fully funded by the EC • after transition also sustained by the NGIs (for example via service charges) • EGI.org critical services are a bundle which must be provided in year one of EGI • NGI international tasks: • funding of the NGI local infrastructure including national IT resources and user communities, and NGI management, is a responsibility of the NGI • EC and NGI co-funding to promote the integration of NGIs resources into the European e-Infrastructure • NGI funding: national funding body, fee-for-service contracts, ... EGI Operations and Security

  13. Outline • Players • Activities: EGI.org critical services and NGI international tasks • Funding • EGI Operations Model • Effort • Summary EGI Operations and Security

  14. EGI Operations Model (1/2) • Aims • Autonomy for NGIs  using a common infrastructure for local and international work for greater efficiency • Sustainability • Subsidiarity: do things at as local a level as possible (EGI.org pulls things together) • Increased reliability through pushing responsibility down to sites • Preserving current scalability in presence of more middleware stacks to be supported, more non-EGEE Grids integrated, ... EGI Operations and Security

  15. EGI Operations Model (2/2) • Risks • Autonomy leads to diversity (different procedures that don't interface across national boundaries) • More staff required as we lose the economies of scale of the centralised model • Insufficient effort in EGI.org spec leads to ineffective coordination. • Mitigation • Middleware interoperability via common interfaces • common solutions and procedures for efficiency • Federation of NGIs • Agreement on sharing of EGI.org responsibilities with NGIs EGI Operations and Security

  16. EGI Operations Model and EGEE III • EGI model needs to be consistent with the evolution trend in EGEE III • EGEE-III contains already the implementation of structural changes required to allow for a seamless transition from the current project-based EGEE model to a stable EGI model based on NGIs • preparation work for a smooth transition already started in EGEE III EGI Operations and Security

  17. Outline • Players • Activities: EGI.org critical services and NGI international tasks • Funding • EGI Operations Model • Effort • Summary EGI Operations and Security

  18. Resource estimates • Effort estimated to cope with the EGI transition phase • Efficiency after a few years might reduce the staff requirement • we expect this to be matched by the requirement for new services to meet the evolving requirements of new communities. • Estimates do not take into account: • activities which require tool development work (monitoring and accounting tools, Grid service management tools, etc.), which will be part of the Middleware Function • additional tasks directly related with the Middleware Function (i.e. the deployment and management of experimental and pre-production Grid testbeds) • these are still expected to be run under the responsibility of operations staff EGI Operations and Security

  19. EGI.org Mandatory Services • Three cathegories: • Operation of tools and services • User Support • Coordination EGI Operations and Security

  20. EGI.org critical Services: Operation of tools and services EGI Operations and Security

  21. EGI.org critical Services:User Support Services EGI Operations and Security

  22. EGI.org critical Services:Coordination EGI Operations and Security

  23. EGI.org critical Services:Security EGI Operations and Security

  24. EGI.org Critical Services: overall Effort EGI Operations and Security

  25. NGI International Tasks (1/2) EGI Operations and Security

  26. NGI International Tasks (2/2) EGI Operations and Security

  27. Catch-all services for NGIs • NGIs free to choose the most suitable provisioning model for the requested international tasks: • under the responsibility of the NGI (or a federation of NGIs) • devolution to a third party • service purchased from EGI.org (catch-all) • to facilitate NGIs, especially during the transition phase • economy of scale: number of FTEs needed by EGI.org to run catch-all services scales well with the number of NGIs requesting it EGI Operations and Security

  28. NGI Resource Estimates • resource estimation carried out during the preparation phase of EGEE III for the SA1 activity (Operations) • Different levels of complexity of NGIs and ROCs • Large ROC: 16 FTEs (5 Grid Management, 6.5 Operations and Support, 3.5 Support to VOs, Users and Applications, and 1 Grid Security) • Small ROC: 6 FTEs (2 Grid Management, 2 Operations and Support, 1 Support to VOs, Users, Applications, 1 Grid Security) • sustainability of Asia-Pacific ROC? EGI Operations and Security

  29. Overall NGI Effort EGI Operations and Security

  30. Summary • EGI Operations: a joint effort of NGIs and EGI.org • Funding: • full EC funding for EGI.org critical services, co-funding for NGI international tasks • Effort: • EGI.org: 16 FTE • NGIs: from 200 to 300 FTEs • Increasing autonomy of NGIs is a challenge • transition started in EGEE III EGI Operations and Security

More Related