1 / 12

Future support of EGI services

Future support of EGI services. Tiziana Ferrari/EGI.eu. EGI Services. Operations coordination Security operations coordination Technology coordination Repository of validated software Core grid services supporting users and operations Technical support to users and operators

koen
Download Presentation

Future support of EGI services

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 support of EGI services Tiziana Ferrari/EGI.eu Future support of EGI Services

  2. EGI Services • Operations coordination • Security operations coordination • Technology coordination • Repository of validated software • Core grid services supporting users and operations • Technical support to users and operators • Policy development • Outreach and marketing Future support of EGI Services

  3. Funding until April 2014 • EGI-InSPIRE • Global Tasks • 25% EC • 25% EGI.eu (NGI membership fees) • 50% NGI • NGI International Task • 33% EC • 67% NGI Future support of EGI Services

  4. EGI Council Strategy • Global tasks • EC projects (Horizon 2020) • support of development, innovation and collaboration • Community funding • NGI International tasks • National funding Future support of EGI Services

  5. Evolving EGI workshop • EGI Global tasks prioritization • I Critical for the daily running of the production infrastructure • II Desirable to avoid degradation of service over time • III Desirable to ensure continuation of service, improvement of quality of service and expansion • Classification will be used to decide on future funding schemes – Apr 2013 Future support of EGI Services

  6. Global task roadmap of the EGI Council Future support of EGI Services

  7. Operational services • Changes foreseen for services interacting with the TPs with specialized support being the area mostly affected  assessment of impact in PY4 • Several coordination functions can continue with a reduced level of funding  increase efficiency by reducing distribution across partners • Review current security operations coordination funding levels • IRTF, security threat risk assessment, SVG • Emerging support services for federated cloud • Operational tools • Reduce operational costs in favour of proactive maintenance • Different potential of future innovation  ensure sufficient effort for proactive maintenance for all tools Future support of EGI Services

  8. New UMD structure (1/2) • After the end of EMI and IGE, UMD needs a new structure to be scalable with more PIs who are less coordinated (more independent) than before • UMD software provisioning (verification and staged rollout in a single release) • will be applied to products where the added value is mostly beneficial for the infrastructure • UMD quarterly releases • Give access to PTs to a subset of the EGI verification testbed to perform integration testing (new activity) Future support of EGI Services

  9. New UMD structure (2/2) Three main categories of contributions to UMD: • Core products  needed to provide the core infrastructure capabilities. E.g.: accounting, information system or user authentication • Software verification and release in UMD performed centrally by EGI • Contributing products  Platform Integrators (PI) will integrate a set of products composing the platform. • Platform should contain products certified to work together • Products should be integrated with the core platform • Software verification is performed by the PI following the EGI guidelines • Platforms are released in UMD in a repository separated from the core one • Platform Integrator will mediate communications between EGI and product teams, acting as contact point • Community products  user communities will use dedicated repositories (provided as a service by EGI) to distribute community specific components. • The release process is entirely controlled by the communities Future support of EGI Services

  10. Current suppliers management process PT PT PT PT Technical coordination Requirements Release management PT PT TCB Software releases UMD Software provisioning Requirements PT PT PT PT Software releases Technical coordination PT PT Release management Future support of EGI Services

  11. After EMI/IGE suppliers management process PT PT UMD Integrated UMD Release Team UMD Software provisioning process PT PT PT PT UMD Contributing Platform integrator PT PT PT PT Community repository PT PT Future support of EGI Services

  12. UMD Release Team Functions of UMD Release Team • Integrate the releases of individual product teams and platform integrator into UMD • Coordinate a periodic (bi-weekly or monthly) phone call with the PTs and the platform integrators • Collect upcoming release plans from PTs • Support for the integration activities of the PTs (to ensure that new releases do not break existing products) • Track the progress in fixing urgent bugs (security vulnerabilities) • Communicate general requirements to PTs, and get their feedback Future support of EGI Services

More Related