EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI SA2 services evolution (after the end of EGI-InSPIRE) Peter Solagna, Michel Drescher – EGI.eu Evolving EGI workshop 10/9/2015 1

EGI-InSPIRE RI Outline Supplier management process, current and future New SA2 task Possible funding changes Conclusions

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

EGI-InSPIRE RI After EMI/IGE suppliers management process PT UMD Integrated UMD Contributing Community repository Platform integrator UMD Software provisioning process URT

EGI-InSPIRE RI UMD Release Team The URT is a proposed new task within SA2 to fill the gap created by the end of EMI and IGE 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 progresses in fixing urgent bugs (security vulnerabilities) –Communicate general requirements to PTs, and get their feedback The effort to run this task has been estimated as 0.5FTE The effort may be variable depending on the number of products integrated in UMD, and the number of Platform Integrators UMD software provisioning (including verification and integration in a single release) has a cost, the full UMD process must be applied for products where the added value is beneficial for the infrastructure

EGI-InSPIRE RI Possible funding changes for current services Task codeService/ActivityEvolution of funding Current allocation (PM) Proposed re- allocation (PM) TSA2.2Quality criteria definitionReduce178 TSA2.3Quality criteria verificationReduce2015 TSA2.4 Software provisioning infrastructure Constant16 IT-SupportConstant16 TSA2.2 Quality criteria definition The quality criteria document will be consolidated during next year Major updates will be related to new products TSA2.3 Quality criteria verification The number of products following the full verification process will decrease Less frequent releases from PTs Give access to PTs to a subset of the verification testbed to perform integration testing (new activity) TSA2.4 Software provisioning infrastructure No changes

EGI-InSPIRE RI Conclusions 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 Proposed new task (URT) to carry out the coordination activities necessary for inclusion of stable platform releases within UMD SA2.2 and SA2.3 can run with a smaller effort –If a more loose verification process for a subset of the current UMD set of products is acceptable