1 / 12

Future directions of EGI Operations

Future directions of EGI Operations. Tiziana Ferrari/EGI.eu Technical Forum 2012. Outline. Short-term objectives Now  April 2013 Medium-term objectives Now  April 2014. Short-term (1). Retirement of unsupported software

breena
Download Presentation

Future directions of EGI Operations

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. Future directions of EGI Operations Tiziana Ferrari/EGI.eu Technical Forum 2012 Future directions of EGI operations

  2. Outline • Short-term objectives • Now  April 2013 • Medium-term objectives • Now  April 2014 Future directions of EGI operations

  3. Short-term (1) • Retirement of unsupported software • Decommissioning of gLite 3.1 and unsupported gLite 3.2 by 30-09-2012 • From 01-10-2012 • Security Nagios monitoring extension with required probes • Security dashboard displaying alarms for sites hosting unsupported software • COD opening GGUS tickets through the sec dashboard • From 01-11-2012 • Escalation of open tickets to EGI CSIRT • Sites hosting unsupported service end-points eligible for suspension Future directions of EGI operations

  4. Short-term (2) • Transition of infrastructure, operational tools and application software towards SHA-2 • Action plan • SHA-2 readiness matrix • Validation of SHA-2 and RFC proxy compliance during the UMD validation processes • Assessment of SHA-2 readiness of the production infrastructure and operational tools • Assessment of the impact on user applications Future directions of EGI operations

  5. Short-term (3) • By 30-04-2013 • Implement service change and mitigations needed to compensate for the end of several tasks currently provided by EMI and IGE • Impact of changes and risk assessment started in August • See agenda of August meeting of OMB Future directions of EGI operations

  6. Specialized middleware support • Availability of 3rd level support units • Ticket workflows and support tools might need to be adapted in case technology-specific support units are not operating anymore • Use of the technology helpdesk will continue, but possibly by a subset of Technology Providers (TPs) • Different levels of support depending on the Product Teams (PTs) • EMI/IGE requested to provide information about PT support channels to be used after 01-05-2013 • Revision of TP SLA to allow different levels of support according to the needs of PTs • EMI and IGE SLAs replaced by SLAs between EGI and PT institutes Future directions of EGI operations

  7. Software Vulnerability Handling • Today • coordinated release and exchange of information about vulnerabilities • agreed response time by TP depending on the vulnerability • PT participation to risk assessment activities (RAT) • Individual new SLAs will be negotiated with PTs or groups of PTs Future directions of EGI operations

  8. Reduced software support • Product support may be retired or will be limited to a subset of user communities • Logical File Catalogue • Open call for expression of interest for a DPM community project • Timeline: ~ end of October 2012 • Nagios probes • EMI/IGE requested to contact individual PTsfor information • … Future directions of EGI operations

  9. Medium-term 1/3 • NGI_GR: Lightweight EGI/NGI operations for increasing sustainability • More automation (NGI_CZ) • Simplification of procedures (NGI_CH) • NGI_AEGIS: keep current distributed operations structure , and keep and continue with decentralization  but… • Federation as a mechanism to save on costs human services that cannot be automated (NGI_CZ) • Central coordination and/or provisioning of services for VOs? WMS, LFC, top-BDII, VOMS, etc. • Aggregation of cpu and storage resources to reduce the number of small sites (NGI_IT) • Coordinated pool of resource at EGI level  resource allocation tools and procedures (NGI_IT) Future directions of EGI operations

  10. Medium-term 2/3 • NGI_IT/IberGrid • more innovation of operations to keep abreast of user requirements (extended portfolio of services for users) • Strengthening of infrastructure integration activities • Service agnostic operations procedures and tools • NGI_PL • Standard procedures and technologies to support operations in order to reduce costs • service management conformant to ITIL best practices • NGI_CZ • More active participation to middleware evolution Future directions of EGI operations

  11. Medium-term 3/3 • Policy actions (NGI_CH) • Ensure EU medium term investment through a dedicate infrastructure program • Facilitate the establishment of medium/long term national sustainability program that would ensure the continuation of the individual NGIs Future directions of EGI operations

  12. Conclusions • Short-term activities driven by the need of new supported technology • SHA2, GLUE2, … • Medium-term activities to ensure • NGI operations sustainability • Reduced cost of operations Future directions of EGI operations

More Related