1. Collaboration ed. 11/11/2009gLite Open Collaboration1 The gLite Open Collaboration “WLCG Overview Board” M. Mazzucato gLite Collaboration Board Chair

2. Collaboration ed. 11/11/2009gLite Open Collaboration2 The gLite Open Collaboration Will preserve and evolve the EGEE gLite middleware in the new scenario of the European Grid Initiative (EGI) and National Grid Initiatives (NGIs) Will foster harmonization and common enhancements with other stacks for EGI: UNICORE, ARC, dCache… Will allow gLite partners to continue to speak with one voice and to evolve and support EGEE users and in particular WLCG ones INFN as EGEE JRA1 leader was put in charge of establishing the new Collaboration

3. Collaboration ed. 11/11/2009gLite Open Collaboration3 Status Agreed by all Jra1 and SA3 EGEE partners to set up the gLite Collaboration –Via a Collaboration Agreement –Contributing an effort as the unfunded EGEE III contribution CA finalized after 6 iterations, 2 meetings and mail exchanges of the gLite proto-CB Postponed the creation of a new legal Entity: the gLite Consortium as a second step to be done once its usefulness and context within EGI will be more clear

4. Collaboration The initial committed effort PARTYTOTAL CONTRIBUTED (FTE) CERN 7.6 INFN/IT 6.6 CESNET/CZ 1.5 SWITCH/CH 0.7 NIKHEF/NL 1.2 UH-HIP/FI 1.2 STFC-RAL1.0 PNPI/RU0.5 CESGA + CSIC/SP0.4 ASGC/TW,0.8 TCD/IE,0.7 GRNET/GR,0.6 KISTI/KR.1.0 UCY/Cyprus 0.2 UAB/SP0.2 TOTAL:24,2 ed. 11/11/2009gLite Open Collaboration4

5. Collaboration ed. 11/11/2009gLite Open Collaboration5 The list of components (1) VOMS and VOMSAdmin (INFN) Proxy and attribute certificate renewal (CESNET) Shibboleth interoperability: SLCS, VASH, STS (SWITCH) LCAS/LCMAPS (NIKHEF) gLExec (NIKHEF) Delegation Framework (CERN,UH.HIP, University of Manchester) CGSI_gSOAP (CERN) gsoap-plugin (CESNET) Trustmanager (UH.HIP) Util-java (UH.HIP) Gridsite (CESNET-University of Manchester) Authorization Framework (UH.HIP, INFN, NIKHEF, SWITCH) BDII (CERN) GLUE Schema (CERN) RGMA (STFC-RAL)

6. Collaboration ed. 11/11/2009gLite Open Collaboration6 The list of components (2) CREAM (INFN) CEMon (INFN) BLAH (INFN) WMS (INFN) LB (CESNET) DPM (CERN) GFAL (CERN) LFC (CERN) FTS (CERN) lcg_utils (CERN) EDS and Hydra (UH.HIP) StoRM (INFN) DGAS (INFN/IT), APEL (SFTC-RAL). AMGA (KISTI) GSTAT (ASGC)

7. Collaboration Status of signatures of CA InstitutionSignature pdfSignature original ASGCOngoing CERNok CESGAok CESNETok GRNETok INFNExpected on Friday KISTIok NIKHEFok PNPIok STFCok SWITCHok TCDOngoing UABok UCYok UH-HIPok ed. 11/11/2009gLite Open Collaboration7

8. Collaboration ed. 11/11/2009gLite Open Collaboration8 Summary All current gLite research partners both from JRA1 and SA3 have “agreed” to take part to the gLite Open Collaboration and contribute effort: All gLite components are currently covered –Gridsite will be supported by CESNET in collaboration with the University of Manchester –The Elsag Datamat parts will be taken over by another partner Ongoing transfer of brand and copyright from EGEE to the gLite Collaboration. The new Collaboration with its own effort can preserve the investment made so far in EGI and guarantee minimal maintenance and support There is a lot of interest around to contribute to gLite. New Initiative to get additional EC funding (EMI)

9. Collaboration ed. 11/11/2009gLite Open Collaboration9 The structure:Collaboration Board The Collaboration Board (CB) –Manage the Collaboration –Is constituted by all Partners who sign the Collaboration Agreement Voting Rights of partners proportional to the contributed FTEs with cap –Starting with EGEE III numbers extracted from JRA1 +SA3 workplans –Reviewed by CB every year jointly to the assignment of tasks CB 6/11/09: MM and Ian Bird elected Chair and Vice Chair

10. Collaboration ed. 11/11/2009gLite Open Collaboration10 The structure:The Technical Board (TB) Composed of the Activity Managers. Chaired by the Technical Director Experts may be invited to the TB based on the discussion topics Take decisions on technical matters by consensus –In case of conflict problems go the CB The set up of the TB will be made later to match the EMI project organization

11. Collaboration The European Middleware Initiative(EMI) Promoted by EGI-DS and created by the 3 Consortia: ARC, gLite and UNICORE + dCache to put together the current providers of the e-Infrastructures that will merge in EGI: –EGEE -> gLite –DEISA/PRACE -> UNICORE –NDGF-> ARC An attempt to promote the sustainable development of an open source community in Europe ed. 11/11/2009gLite Open Collaboration11

12. Collaboration ed. 11/11/2009gLite Open Collaboration12 Mirco Mazzucato CD INFN 12 The reference model A no-profit Organization –With Profit and no-profit partners Common development activities An open source source licence See Linux, Apache… Organization No-profit New general services Institution Research Institutions& Universities Institution Private Companies Open Source Licence Institution Teams of developers Institution Commercial Services for companies Components for e-Infrastructures

13. Collaboration EMI: The next step New common EC project (ARC, gLite Unicore, dCache) to maintain what exists in EGI and simplify access via harmonization and common innovation and evolution Project Director: Alberto Di Meglio- CERN WLCG -> Additional funding for the gLite maintenance and the service evolution in the EGI era ed. 11/11/2009gLite Open Collaboration13

14. Collaboration ed. 11/11/2009gLite Open Collaboration14 : The Project objectives GENERAL: 1: Simplify the usage of services over distributed computing and data infrastructures 2: Increase the interoperability, manageability and usability of the services by developing or integrating new functionality as needed 3: Support efficient, reliable operations of EGI/ PRACE by maintaining the middleware distribution and providing increasingly reliable, stable, and scalable software 4:Strengthen the participation of the user communities in the definition and evolution of middleware services 14

15. Collaboration ed. 11/11/2009gLite Open Collaboration15 EMI: Innovative Technical Objectives Simplify, unify and extend the security model Introduce transparent interoperability between HTC and HPC (special focus on MPI) Introduce interoperability with clouds-based infrastructures using what exists already when available Open to external providers Introduce new resource management methods based on existing virtualization solutions Users will get their specific virtual environments EMI Overview 15

16. Collaboration ed. 11/11/2009gLite Open Collaboration16 EMI: Innovative Technical Objectives (2) Unified messaging system in support of monitoring, accounting and generic information exchange among services Add standard service monitoring interfaces usable by open source and commercial monitoring systems Strengthen standards formats for accounting Investigate and add technologies to simplify user access Add portlet functionality in all services to support users’ gateways and portals EMI Overview 16

17. Collaboration ed. 11/11/2009gLite Open Collaboration17 EMI-EGI working model Middleware Collaboration Board (MCB) to agree requirements and deployment roadmaps Representatives of Operations, Middleware, Users In EMI work assigned to Product Teams (PT) Every PT is responsible to execute its own testing All testing is done publicly and transparently against pre- defined criteria including deployment ones agreed with EGI WLCG is a strong Heavy user Community of EGI Express requirements and feedback via MCB Tests and test results of components are stored in the EMI test repository (ETICS)  SLAs enforcement available for EGI and sites to start deployment 17

18. Collaboration ed. 11/11/2009gLite Open Collaboration18 EMI: Administrative Structure 22 (+2) Institutes currently agreed as partners in the EMI project –ARC (6): KU, NIIF, LU, UiO, UPJS, UU –gLite (11+2): CERN, CESNET, CSIC/CESGA, INFN, NIKHEF, SFTC-RAL, SWITCH, UH.HIP, GRNET, TCD –(2) KISTI (Korea) and ASGC(Taiwan) as non EU collaborators –UNICORE (4): CINECA FZJ, ICM, TUD –DESY –4 year project with most of effort concentrated in 3 years –12-13 M€ requested EC contribution ( 75 FTE ; 50% co- funded by partners as in EGEE) 18

19. Collaboration The workpackages NA1 - Administrative and Technical Management NA2 - Outreach and Collaborations SA1 - Maintenance and Support SA2 - Quality Assurance JRA1 – Middleware Development and Evolution JRA2 – Interoperability, Integration and Testbeds ed. 11/11/2009gLite Open Collaboration19

20. Collaboration ed. 11/11/2009gLite Open Collaboration20 Conclusions The gLite Open Collaboration has been established Investments and achievements made in the EGEE project series will be the base for a further more sustainable step forward in the EGI era –WLCG is the EGI major user community and through the MCB will continue to steer the EMI/gLite effort –All current components requested by WLCG are included in the EMI component list The EMI project will provide harmonization with ARC and UNICORE and further common innovative evolution of the gLite components