1. www.egi.eu EGI-InSPIRE RI-261323 EGI-InSPIRE www.egi.eu EGI-InSPIRE RI-261323 WP5 Review Michel Drescher EGI.eu SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 1

2. www.egi.eu EGI-InSPIRE RI-261323 Activity Overview This slide will be provided by the PO It will summarise the activity in tables by: –The # partners, # people, # countries –The # PM and #FTE per country It will summarise the activity in graphics by: –The % effort of the activity within the project –The geographical spread across Europe SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 2

3. www.egi.eu EGI-InSPIRE RI-261323 Objectives 1.Establish agreements with key software providers 2.Maintain the UMD Roadmap 3.Define general and component specific quality criteria to be applied to software components 4.Verify the software components against these criteria 5.Provide a repository for the software components within UMD and the related support tools 6.Provide a distributed support unit within the EGI Helpdesk infrastructure with expertise on the deployed middleware in production use. SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 3

4. www.egi.eu EGI-InSPIRE RI-261323 Tasks SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 4 TaskDescription TSA2.1 Management and coordination of the activity. Management of the relationships with external Technology Providers. Collate and distribute prioritised requirements Maintain UMD Roadmap and release schedules Hold Coordinate and chair meetings with Technology Providers for resolution of issues and conflicts. TSA2.2 Develop, maintain and publicise generic Acceptance Criteria Develop, maintain and publicise component-specific Acceptance Criteria TSA2.3 Validate contributed software against Acceptance Criteria Provide component acceptance reports summarising the verification TSA2.4 Provide infrastructure for EGI.eu Provide necessary infrastructure for the Software Provisioning process TSA2.5 Establish and maintain a second level support unit (the “DMSU”) Establish and maintain consultancy relationships with EGI Operations and external Technology Providers

5. www.egi.eu EGI-InSPIRE RI-261323 Insert slides that describe: The work done and results achieved Quality of the results Attainment of the objectives & milestones The issues that arose How they were dealt with The impact of the WP’s work SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 5

6. www.egi.eu EGI-InSPIRE RI-261323 EGI Software Supply Chain EGI Software Supply Chain We set out to 1.Drive and steer the evolution of middleware –Based on installed software –Prioritise collected requirements –Provide UMD Roadmap updates –Publish EGI Software Quality Criteria SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 6 TCB OMB UCB Production Infrastructure Production Infrastructure

7. www.egi.eu EGI-InSPIRE RI-261323 We set out to 2.Establish a software supply chain model –Technology Providers as suppliers –Verify deliveries, assemble a unified middleware (UMD) –Resource centres as customers SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 7 Technology Providers Resource Centres Repository Acceptance Testing Acceptance Testing Staged Rollout EGI Software Supply Chain

8. www.egi.eu EGI-InSPIRE RI-261323 Defining business Processes –What are the triggers and terminal conditions? –Who is responsible for which step? Interactions –Who/what are the triggering actors processes? –Which information is passed-in, and out? Artefacts –What needs documentation? –Where is it available? SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 8

9. www.egi.eu EGI-InSPIRE RI-261323 Processes Middleware evolution –Requirements capturing and processing –UMD Roadmap maintenance and publication –Technology Provider release schedule coordination –Establishing relationships with Technology Providers EGI Software supply chain –Quality Criteria maintenance –Acceptance testing (Criteria verification) –Middleware helpdesk processes –Software Provisioning SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 9

10. www.egi.eu EGI-InSPIRE RI-261323 Interactions With the User communities: –In the TCB through prioritised requirements With the Operations community –In the TCB through prioritised requirements –Via the SVG/RAT for security vulnerabilities –Via the DMSU for software incidents and problems –With Resource Centres using the Software Repository With Technology Providers –In the TCB for new requirements –In Task Forces for Software Quality, and Repositories SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 10

11. www.egi.eu EGI-InSPIRE RI-261323 Artefacts Middleware evolution –UMD Roadmap –Standards evolution and roadmap –MoUs and SLAs with Technology Providers Software Supply Chain –UMD Release Schedule –Quality Criteria documentation –Verification reports, and guidelines –StagedRollout reports –Software Provisioning tracking artefacts SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 11

12. www.egi.eu EGI-InSPIRE RI-261323 Doing business Implementing processes, artefacts and interactions Validate feasibility with small, controllable scope –With internal Technology Providers EGI Trust Anchors, SAM (JRA1) Establish and maintain appliance delivery model –With external Technology Providers (EMI) Re-scope and implement distribution based supply chain Verify principal supply chain with two dry runs Scale out to full enactment of the supply chain Review regularly, and implement adjustments SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 12

13. www.egi.eu EGI-InSPIRE RI-261323 We are not yet done… Processes, Interactions and Artefacts are defined Documentation is of varying quality –Some artefacts are well defined, some are fuzzy –Some processes are executed mostly by intuition Reproducibility of results needs improvement –E.g. impartial provisioning of delivered software –Reporting artefacts vary by producing individuals Technically, objectives are met… SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 13

14. www.egi.eu EGI-InSPIRE RI-261323 Issues in PY1 1.Staffing –Target staffing reached in January 2011 2.Requirements reported as support requests –Rerouted to TCB’s Requirements capturing process 3.Low ratio of ticket resolution in DMSU –Further analysis of tickets ongoing SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 14

15. www.egi.eu EGI-InSPIRE RI-261323 Issues in PY1 4.Criteria Verification not well understood –Task Force Quality Assurance set up –Introducing concepts of formal Acceptance Testing –Continuous education of Technology providers 5.Lack of interaction and pro-activeness of EMI –Task Force Repositories and Automation –Discuss technical issues around software delivery –Large discrepancy between software supply models –On-going, time consuming activity SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 15

16. www.egi.eu EGI-InSPIRE RI-261323 Need a title here Provide open, impartial software evolution plans Provision software for a large community –Avoid duplicated, per-site software assessment –Reduced overall effort for increased sustainability Provide a unified middleware repository –One-stop shop solution in a multi-provider, multi-use case infrastructure –“Off-the-shelf” experience for site administrators Quality in delivery depends on stakeholders SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 16

17. www.egi.eu EGI-InSPIRE RI-261323 Use of Resources SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 17 TaskTask PY1PartnerPY1Q1Q2Q3Q4 TSA1. 1 90%1 – EGI.eu90%20%116%110%116%Delayed employment, compensating TSA2. 2 81%12A – CSIC76%44%84%99%79% 29 – LIP85%0%36%173%133%Delayed employment, compensating TSA2. 3 99%12A – CSIC148%50%196%192%153% 12B – FCTSG92%0%13%112%245%Compensating late employment, Testbed setup 29 – LIP77%0%4%173%133%Delayed employment, compensating TSA2. 4 75% 9 – CESNET91%69%96%102%97% 16A – GRNET47%0%60%48%79% 16B – AUTH42%0% 40%127%Provisioning Workflow maintenance PY2+ 16E – IASA201%281%340%163%22%Implementation Provisioning Workflow in PY1 16F – ICCS33%0% 131%Provisioning Workflow maintenance PY2+ TSA2. 5 77% 9 – CESNET100%97%99%106%96% 10D – JUELICH83%15%82%124%111% 21A – INFN99%81%60%140%117% 36 – UPCH0% 38B – LIU72%0%90%101%97% 41 – NORDUNET33%0% 133%0%

18. www.egi.eu EGI-InSPIRE RI-261323 Plans for next year Continuous review and maintenance of processes, documentation and verification artefacts Streamline publication schedules of UMD Roadmap, Quality Criteria and Criteria mappings for Services Enhance DMSU expertise, analysis toolset and knowledgebase Investigate community orientated software repositories SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 18

19. www.egi.eu EGI-InSPIRE RI-261323 Summary Structural work is finished –Verified by production level use with internal providers Quality of service is itself a process –Establish and formalise regular reviews and improvements EMI as largest Technology Provider… –Shows similarities to monopolies in other ICT sectors –Not ready for multi-provider, multi-use case settings SA2 – Michel Drescher - EGI-InSPIRE EC Review 2011 19