Components Selection Validation Integration Deployment What it could mean inside EGI

Disclaimer All views expressed are mine and not necessarily reflect CERN’s / EGEE’s / WLCG’s view 2

What I have been doing so far I have been involved in: Edg Integration, testing, deployment, operations LCG/EGEE-I Operations (shift to distributed operations), deployment, testing, interoperability EGEE-II Selection, integration, testing, configuration (shift to distribution) Interoperability and standardization Data management, Information Systems software development Activity coordination (SA3 coordinator) EGEE-III Proposal 3

Is this wanted? According to the survey: Yes 4

Components Selection Probably the most complex aspect in EGI Now: Project wide selection via TCG Only core components Vos + operations + developers Regions (proto NGIs) add some components VO driven Operations (monitoring) driven Interoperations between projects with similar middleware OSG, ARC, gLite Higher level software developed by VOs 5

Components Selection EGI (as I see it) NGIs strive for greater independence in terms of middleware Co-hosting and different stacks will be common gLite || ARC || UNICORE || OMII || ??? || ????? Some similar, some quite different Standards are just emerging and will help at t+3 More high level services from VOs Many sources for a new middleware components 6

Components Selection Process: Stakeholder centric Vos, resource providers, operations decide Small central activity to drive this process Organize communication Maintain requirements Maintain (formal) acceptance criteria Support, licenses,…. Maintain state of integration …….. Distributed throughout EGI Evaluation of new components based on requirements and criteria Providing “Glue” to integrate components Information system support Security policy implementation Interoperability 7

Validation The project can’t realistically validate All middleware On all platforms Against all interoperating stacks In all deployment scenarios There will be no place with the required complete knowledge The Renaissance is over And combinatory kills the most industrious……. What can be done? 8

Validation Focus on core components and reference environments Provide different levels of validation for different components Class 1) Doesn’t harm critical components Class 3) Fulfills basic requirements Class 4) Works with existing infrastructure Class 5) Performance, stability and security validated Class 6) ?????? Same component can be available on different platforms at different levels 9

Validation Who will do what? Small central team Organizing the work Ensure that results can be transferred between partners Maintaining work plans (in line with selection results) Communication Process definition Tracking state of components Who (NGI, VO) works on what aspect How far is the validation process for component x Maintaining/developing acceptances criteria Repository for validation documentation Traceability Repository for validation tools Test infrastructure coordination Validate that validation is following the agreed practice 10

Validation Who will do what? NGI or VO centric teams For core components Validate components In line with EGI policies and processes To the agreed level Develop tools for validation Tests, testbeds, etc. Contribute to the process development Contribute to the component/platform classification For local or VO specific middleware Same as above, but much more independently Push results to central “component state” repository 11

Integration Build and Configuration Management Same as before: Focus on core components And generic tools Central team to ensure common approach (not define it, but maintain it) Run services that support it like: build systems, repositories, etc. Configuration management infrastructure Maintain accepted dependency lists Track state ( Platforms, components) NGI & VO centric Platform support Individual component support (core and higher levels) Build definitions Configuration Dependency management 12

Deployment Focus on core components Central team to ensure common approach (not to define it, but maintain it) Maintain the definition of what a release package is Verify for core components that the component/update material is complete And in line with EGI standards Announce core component releases Organize deployment support Provide repositories for documentation and components Link to operations for core services NGI & VO centric Deployment support for individual components and or deployment scenarios Organizing role out of components in their region/VO 13

Summary and Clarification EGI will be a much more divers world than EGEE Users, middleware, platforms,(goals) The central activities do not need to be co-located What forces integration to be where component selection is done? Central activities to: Coordinate Maintain state, policies Run tools, repositories …. Ensure that agreed procedures are followed All other partners Concentrate on environments relevant to them Shape policies and procedures 14

The End