EGI InSPIRE Report to the EGI Council Steven Newhouse On behalf of the Editorial Board

Discussion points Letter of Support Conference Location Project Membership Project Structure Global Task Allocation Budget & Project Goals

Letters of Support All requests for LoS to be submitted by 16 th October All requests presented at EGI Council for approval on 23 rd October LoS written after EGI Council meeting Recognise different LoS types: –Middleware, Collaboration, SSCs Document with the Steering Committee for review Agree and provide feedback on the criteria

Conference Location Proposal to have two large annual meetings –User focussed –Infrastructure focussed Work with other providers to make this more focused on all e-infrastructures –User Forum continues in this direction Planning for a 600 person event needs to start now –Meet in Amsterdam Autumn 2010 –Future events decided by EGI through bidding European e-Infrastructure Meeting in Amsterdam, Autumn 2010

Project Structure & Membership 1.Requirement that ALL funded partners must be represented through the EGI Council –Restriction EGI-InSPIRE projects to ‘NGI’ JRUs or equivalent –Simplifies the management structure –Limits flexibility 2.EGI Council manages EGI.eu and EGI.eu is a partner in EC projects –Allows EGI.eu participation beyond EGI-InSPIRE –Complicates the management structure –Allows involvement in multiple projects

EGI-InSPIRE EGI.eu (Management) Management Issues EGI Council EGI Council Executive EGI.eu EGI.eu EGI.eu NGIs NGI/EIRO NGIs/EIROs NGIs & EIROs EGI-InSPIRE Collaboration Board Project Management Board Partners Project Partners EC Project n Collaboration Board Project Management Board Partners Project Partners EGI.eu/NGI/EIRO Staff Agree on single or multi-project model

Project Structure NA1: Project Management NA2: External Relations: Policy, Dissemination and Standards SA3 Software Support SA2 Middleware Unit SA1 Operations JRA1 Operational Tools SA4 Services for HUCs NA3 User Support Software Provisioning and Support Operations and Tools User Support and Services

Funding Project Activities EGI Global Tasks (EGI.eu functions) –Done by one on behalf of all –Primarily: NA1, NA2, NA3, SA1 & SA2 NGI International Tasks –Mainly SA1 –Small amount of effort in NA2 & NA3 Other EGI Activities (Effort in NGIs) –SA3, SA4, JRA1

Received NGI Information Spain Ireland Bulgaria Croatia Switzerland Finland Slovakia The Netherlands Greece Belgium Serbia Romania Latvia UK Armenia Georgia Moldova NGIs not providing information will not be in the project. Please provide details ASAP.

Global Task Allocation Recall the procedure: –Open bidding & review of proposals –74 proposals from 14 NGIs for 34 tasks Proposed allocations passed to EGI CSC –One proposal: Technical check –Competing Proposal: Check, Reviewed, Ranked Reviewers: Experts from NGIs & SSCs

Allocated Tasks (Single bid) TaskDescriptionOrganisation O-E-1GOCDBUK O-E-4Operations PortalFrance O-E-8User RequirementsGermany O-E-6Operation of a helpdeskGermany O-E-15Security PolicyUK & Netherlands U-E-5User Technical ServicesSpain & Portugal U-E-1User ForumEGI.eu U-E-3Event OrganisationEGI.eu O-E-5Grid Operation & OversightNetherlands & Poland Agree on allocation

Allocated Tasks (Contested) TaskDescriptionOrganisation O-E-9Middleware RolloutSpain & Portugal O-E-12Network SupportItaly O-E-14Core Grid ServicesGreece O-E-2Accounting RepositoriesUK & Spain O-E-10Resource AllocationPoland O-E-11InteroperationSweden O-E-13Best PracticesFinland O-E-16Security Incident ResponseUK & Netherlands U-E-6Informational & High-level toolsGreece Agree on allocation

Allocated Tasks (Contested) TaskDescriptionOrganisation U-E-2Coordination of SSCsEGI.eu E-E-1DisseminationEGI.eu E-E-3Industry UptakeEGI.eu E-E-4External RelationsEGI.eu U-E-9New Communities & Front DeskEGI.eu O-E-7Triage of Incoming ProblemsGermany & Netherlands U-E-8TrainingUK O-E-17Operational ToolsNot clear U-E-7Document ReviewNot clear Agree on allocation

Remaining Tasks - Middleware Technical: –Document Process (M-E-1) –Define & Verify Quality Criteria (M-E-3) Process Support: –Tools (M-E-2) –Repository (M-E-4) Coordination: –Execute Plan (M-E-4) –Grid Planning & MCB (U-E-4)

Middleware Tasks - Next Steps The Technical, Process Support & Coordination Tasks should be grouped The Coordination Tasks should be at EGI.eu The Technical tasks should not be co-located with a major software supplier to EGI Who should be allowed to bid? 1.NGIs that previously bid for any of these tasks 2.All NGIs ‘MU Coordination Tasks’ at EGI.eu ‘Technical Tasks’ not with Software Provider Agree on who is allowed to bid

Remaining Task – O-E-3 Repositories for monitoring and performance –Has changes considerably since the Blueprint –Move to regional monitoring structure –Move to ActiveMQ Bids: –France, Germany, Greece, Italy, Poland & Croatia Task description will be revised by SA1 during EGEE’09 Bidding NGIs will be asked to review their bids with the new task definition –Selection made using same process for other tasks Agree on process for O-E-3

Other ‘Global’ Tasks Support for deployed production middleware (SA3) –YES: Call for sites with production experience in all EGI related middleware (gLite, ARC, UNICORE) –Criteria: Minimal set that covers most middleware and deployment environments Operational Tools Maintenance & Development (JRA1) –NO: Maintenance driven by partners that are providing the relevant EGI tasks –YES: New development of operational tools should be agreed. NB: This may need to be in a different project Open bids for SA3 & new Operational Tools

New ‘Global’ Tasks Several new or missing activities have been defined: –Site Security Monitoring Tools –Software Vulnerability Group (a.k.a. GSVG) What is the process for defining other tasks? –Defining new tasks has a budget implication on EGI.eu Any new Global have equal EC/NGI contribution and assessed for inclusion as a persistent Global task in future projects

Budget & Project Goals What do we want out of the project? –Transition to a sustainable model –Keep an integrated worldwide model Demonstrate transition to self funding Need to consider what is core & non-core? –New Operational Tools –Developing Scientific Gateways

Global Task Funding Current expectation is not clear! –EGEE generally has 50% EC contribution Following financial models show increased EGI.eu contribution from NGIs Proposed funding model for Global Tasks –Decrease EC & NGI funding –Increase funding direct from EGI.eu as subcontract EGI.eu funds contracted back to NGIs that provide Global Tasks to the Community

NGI Budget Data Input from 31 NGIs Uncorrected International Tasks –7 (Armenia)  360 (Italy) PM a year –Total 2848PM (237FTE) a year Bids reviewed to assess reasonable effort –Decided a ‘reasonable’ level of effort –7 (Armenia)  190 (Italy) PM a year –Total 2281PM (190FTE) a year

Issues International Tasks are the EXTRA work an NGI has to do to support European collaboration –That does not mean 2 FTE to provide security coordination! O-N-5,6 & 7: NGI e-Infrastructure Oversight, Integration of NGI ticketing system, Triage and monitoring of the incoming tickets –Ranged from 0 (Switzerland)  120 (UK) –Cut to something reasonable... 24PM? –Cuts 360PM (12FTE) to 1921PM (160FTE) Agree on following Funding Model 1, 2 or 3

Opt 1:EGI V2 ActivityFTEME/yearEGI.euFrom ECFrom NGI EGI.eu NGI International NGI HUC NGI Other TOTAL ME, 24 month project Increase EGI.eu in Y2=2.6ME

Opt 2:EGI V2 (Reduce NGI Tasks) ActivityFTEME/yearEGI.euFrom ECFrom NGI EGI.eu NGI International NGI HUC NGI Other TOTAL Increase EGI.eu: Y2=2.5ME, Y3=4ME 30 month:~26.0ME NB: Still need to refine effort for 25ME 36 month:~29.9ME

Opt 3:EGI V2 (Minimal) ActivityFTEME/yearEGI.euFrom ECFrom NGI EGI.eu NGI International NGI HUC NGI Other TOTAL Use aligned EC projects (now or next year) New Operational Tools & development (~10 FTE) Gateway project (~6FTE) Cut SA4 (-10%) & SA3 (-25%) Increase EGI.eu: Y2=3M, Y3=5M 36 month: ~26.55ME

Other Options Move other activities into other projects –Gateways, New Operational Tools,... Reduce the level of activity in other areas: –NGI International Tasks –HUCs Increase the EC contribution for NGI tasks –5% increase a year? Availability of further funds in FP7 –YES: For EGI related projects –NO: For the support of EGI itself Further cuts to make a 4 year project?

Remaining Schedule 30/9/09: Comments on V2 draft 8/10/09: V3 draft: –Integrate comments and put into table format. –Send to consultant for high level feedback. 15/10/09: Comments on V3 draft 19/10/09: V4 draft: –Polished with completed effort tables and A2 forms. –Send to consultant for detailed feedback. 23/10/09: EGI Council (Brussels) 27/10/09: Comments on V4 draft 30/10/09: Version submitted into EPSS 6/11/09: Version submitted into EPSS 13/11/09: Version submitted into EPSS 20/11/09: Version submitted into EPSS 24/11/09: CALL CLOSES

Other Issues?

From the previous EGI Council Steering Committee meetings the following constraints have been imposed on the budget simulation: 4 year project EGI.eu contributions start at 1M€ in year 1 and increase linearly to 2M€ in year 4 90K€/year staff cost which includes indirect costs The Heavy User Communities funding is an average of 23FTE only over the first 3 years The minimum EC contribution to EGI.eu related activities is 25% The NGI contribution to EGI.eu related activities is 50% The NGI contribution to NGI International Tasks is 67%

The EGI-InSPIRE project has staff in four different categories: Activity A: EGI Global Tasks coordinated by EGI.eu on behalf of the community and undertaken by staff employed directly by EGI.eu. Activity B: EGI Global Tasks coordinated by EGI.eu on behalf of the community and undertaken by staff employed by NGIs. Activity C: NGI International Tasks undertaken by staff in each NGI in order to interface into the operations coordinated by EGI.eu Activity D: Other activities undertaken by staff within the project located within the NGIs (primarily HUCs)