European Middleware Initiative EMI Alberto Di Meglio CERN

European Middleware Initiative (EMI) Alberto Di Meglio (CERN) Project Director

EMI Workshop • Agenda • Objectives • Next steps 8/4/2010 EMI Workshop 2

EMI Workshop Agenda • Two main parts – Introduction and presentation of related projects • We need to understand the broad context and the relationships with other Infrastructure-related projects • Fundamental input to the rest of the discussion – Discussion of EMI concepts, procedures, tools, short-term objectives, etc • Anything we need to take off in three weeks time 8/4/2010 EMI Workshop 3

EMI Workshop Objectives • More in details – Start getting to know each other – Assess the current status of the project – Identify areas of discussion • Global tasks (release management, support, QA, tools, repository, SLAs, etc) • Technical interaction with EGI (releases, 3 rd level support, security, etc) • Product Teams (what, who, why, how) – Define the next steps and milestones 8/4/2010 EMI Workshop 4

Current Status • Currently in the negotiation phase (revision of the Do. W, of deliverables and milestones, fine tune budget and effort, contractual documents, etc) • Starting date: May 1 st • Duration: 3 years • Kick-off meeting planned for the fourth week of May (tentatively 24 -26 or 26 -28 May) • Some technical preparation meetings may be required before that 8/4/2010 EMI Workshop 5

Project Structure Administrative and Technical Management Quality Assurance Dissemination and Communication 8/4/2010 Maintenance and Support Development, Integration and Evolution EMI Workshop 6

Project Execution Project Director Project Executive Board (PEB) Technical Director Project Technical Board (PTB) Technical Area Coordinators 8/4/2010 Work Package Leaders EMI Workshop 7

Project Execution Project Executive Board (PEB) Release Manager Engineering Management Team PT 1 PT 2 PTn EGI, PRACE, etc Security Experts Manage ‘standard changes’: release management, bug triaging, QA analysis 8/4/2010 EMI Workshop 8

Technical Areas 8/4/2010 Compute Services A-REX, UAS-Compute, WMS, LB, CREAM, MPI Data Services ARC SE, d. Cache, Sto. RM, UAS-Data, DPM, LFC, FTS, Hydra, AMGA Security Services UNICORE Gateway, UVOS/VOMSAdmin, ARGUS, SLCS, gl. Exec, Gridsite, Proxyrenewal Infrastructure Services Messaging, accounting, monitoring, virtualization/clouds support, Information systems and providers EMI Workshop 9

Project Execution Project Technical Board (PTB) CS PT 1 PT 2 SS DS PTn IS EGI, PRACE, etc Experts Working groups or domain experts Manage the technical roadmap: major functional changes, standardization, interoperability, common services definition, etc 8/4/2010 EMI Workshop 10

Overall Structure Project Executive Board (PEB) Project Technical Board PT 8/4/2010 PT PT PT Development and Evolution PT EMI Workshop Security Services Maintenance and Support Data Services Compute Services Quality Assurance PT PT Infrastructure Services EMT PT 11

Quality Assurance Improve Release Stress tests Common test and Scalability tests certification Maintenance and Support process Functional tests and tool chain Regression tests shared by all Deployment tests middleware Packages providers, Unit tests the repository, Build the testbeds Development and Evolution Design Monitor 8/4/2010 Metrics EMI Workshop 12

Releases and Release Policies This (mainly) applies to EMI releases • Major releases: once or twice per year, may contain non-backward compatible changes This (mainly) applies to individual components • Minor releases: a few times per year, fully backward compatible, may contain new functionality and fixes • Revisions: every week or two weeks, only bug fixes • Emergency: as needed, only very specific bug fixes, use emergency release procedures 8/4/2010 EMI Workshop 13

Product Teams - Why • PTs are not independent from EMI, they are the executive arm of EMI and are collectively responsible to achieve its technical objectives • They provide a transparent and direct method to assign responsibility for a service within the context of the EMI distribution • They introduce more flexibility in the organization by delegating the task execution from the WP leader to technical domain experts 8/4/2010 EMI Workshop 14

Product Teams - What • PTs perform the required technical tasks from design to release through implementation, testing and certification and provide 3 rd-level support for one or more EMI products • During the lifetime of a product they report their effort to either JRA 1 (Development) or SA 1 (Support and Maintenance) • They participate to the technical roadmap definition via the PTB and to the release management via the EMT 8/4/2010 EMI Workshop 15

Product Teams Accountable for the service Service A Release, maintenance and 3 rd-level support Integration, interoperability Development 8/4/2010 EMI Workshop 16

Product Teams - How “This slide is intentionally left blank” 8/4/2010 EMI Workshop 17

Thank you 8/4/2010 EMI Workshop 18