EMI and GISELA Collaboration Alberto Di Meglio (CERN)

EMI Mission Statement The European Middleware Initiative (EMI) project represents a close collaboration of the major European middleware providers - ARC, gLite, UNICORE and dCache - to establish a sustainable model to support, harmonise and evolve the grid middleware for deployment in EGI, PRACE and other distributed e-Infrastructures 27/01/2011 EMI and GISELA

Collaborations EGI, PRACE, WLCG,OSG, etc Standards ESFRI, EMI Industry SLAs & Support Releases Requirements Standards Industry EMI ESFRI, VRCs Collaborations Collaborations DCI collaborations StratusLab VENUS-C SIENA EDGI IGE 27/01/2011 EMI and GISELA

EMI Middleware Evolution Before EMI 3 years After EMI Applications Integrators, System Administrators Standard interfaces Specialized services, commercial professional support Standard interfaces EMI Reference Services Standards, New technologies (clouds) Users and Infrastructure Requirements 27/01/2011 EMI and GISELA

Release Plan EMI Reference Services Start EMI 1 EMI 2 EMI 3 Major releases Supp. & Maint. Support & Maintenance Support & Maintenance Support & Maintenance 01/05/2010 30/04/2011 30/04/2012 28/02/2013 27/01/2011 EMI and GISELA

Development and Test Plans Release Cycle EMI 1 PTB TCB Technical Plans Requirements Development and Test Plans Certification Development Testing Validation Maintenance Support Release Roll-out/DMSU 30/09/2010 SA1 JRA1 As needed 31/10/2010 SA2 30/04/2011 28/02/2011 JRA1 SA1 27/01/2011 EMI and GISELA

Development and Test Plans Release Cycle EMI 2 PTB TCB Technical Plans Requirements Development and Test Plans Certification Development Testing Validation Maintenance Support Release Roll-out/DMSU 30/04/2011 SA1 JRA1 As needed 30/06/2011 SA2 30/04/2012 28/02/2012 JRA1 SA1 27/01/2011 EMI and GISELA

The Requirement Process EMI categorizes requirements in two classes: Major requirements: new services, major interface changes of existing services, support for new platform requiring substantial modification to major services, etc Minor requirements: any change to improve a service that keeps backward compatibility and is limited in scope to subsets of the whole EMI distribution Major requirements are discussed through high-level collaboration bodies like the EGI TCB or the WLCG MB and normally have to be provided before a major release cycle starts Minor requirements can be submitted at any time by anybody Once a requirement is in principle accepted, any technical discussion needed to implement a solution is discussed directly with the original proposer, who must also engage in validating and using the solution when available 27/01/2011 EMI and GISELA

EMI and GISELA Requirement from GISELA can be submitted to EMI: Via existing high-level bodies, like the EGI TCB Directly EMI is happy with either solution, but we would prefer the first: It is already a managed, tracked collaboration Acts as a central coordination place where duplicate or conflicting requirements can be filtered out and proper prioritization discussed However, for requirements coming from GISELA, we would like to establish a direct technical channel to discuss about implementation and validation for accepted requirements 27/01/2011 EMI and GISELA

EMI and GISELA Possible requirements or collaboration areas of interest to EMI from the GISELA workplan: Support and Customisation of Already Available Services Development and Support of New Services   and in particular: gLite port to Windows OS gLite-ourgrid interop app services on top of gLite (e.g. monitoring & control of WN jobs) adoption of gLite security mechanisms in ourgrid 27/01/2011 EMI and GISELA

EMI and GISELA Next steps: Agree on the best collaboration model Identify which of the aforementioned technical areas are: Requirements Collaboration areas Agree on a number of realistic tasks that EMI and GISELA can run together for mutual benefit Sign an MoU describing the tasks and some reasonable milestones 27/01/2011 EMI and GISELA

Thank you EMI is partially funded by the European Commission under Grant Agreement INFSO-RI-261611 27/01/2011 EMI and GISELA