EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI Future support of EGI services Tiziana Ferrari/EGI.eu Future support of EGI Services1

EGI-InSPIRE RI 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 Services2

EGI-InSPIRE RI 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 Services3

EGI-InSPIRE RI 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 Services4

EGI-InSPIRE RI 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 Services5

EGI-InSPIRE RI Global task roadmap of the EGI Council Future support of EGI Services6 Action number DeadlineActivity ( 1 Workshop in January 2013 Identify and prioritise the current operational EGI Global Tasks and associated activities that can be continued and the new activities that need to be sustained on the available resources to maintain an operational infrastructure that is open to all research communities. 2 EGI Council April 2013 Discussion of possible different funding models and levels of participation fee coming from the EGI Council. Review the EGI2020 Strategy accordingly. 3 EGI Council April 2013 Define the process by which EGI Global Tasks are going to be delivered after the EGI-InSPIRE project will be selected. 4 July 2013 Request and assess proposals from the EGI Community to provide the post EGI-InSPIRE EGI Global Tasks using the approved selection process. 5 EGI Council September 2013 Prepare a transition plan for any EGI Global Tasks that will be migrating in April 2014 and define a timeline relating to their migration that can be reviewed regularly by EGI.eu.

EGI-InSPIRE RI 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 Services7

EGI-InSPIRE RI 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 Services8

EGI-InSPIRE RI 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 Services9

EGI-InSPIRE RI Current suppliers management process TCB UMD Software provisioning Technical coordination Release management Technical coordination Release management PT Software releases Requirements Future support of EGI Services10

EGI-InSPIRE RI After EMI/IGE suppliers management process PT UMD Integrated UMD Contributing Community repository Platform integrator UMD Software provisioning process UMD Release Team UMD Release Team Future support of EGI Services11

EGI-InSPIRE RI 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 Services12