EGI In SPIRE Report to the EGI Council

EGI In. SPIRE 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 Lo. S to be submitted by 16 th October • All requests presented at EGI Council for approval on 23 rd October • Lo. S written after EGI Council meeting • Recognise different Lo. S 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-In. SPIRE 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-In. SPIRE – Complicates the management structure – Allows involvement in multiple projects

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

Project Structure NA 2: External Relations: Policy, Dissemination and Standards SA 2 Middleware Unit Software Provisioning and Support SA 3 Software Support JRA 1 Operational Tools Operations and Tools SA 1 Operations NA 1: Project Management NA 3 User Support and Services SA 4 Services for HUCs

Funding Project Activities • EGI Global Tasks (EGI. eu functions) – Done by one on behalf of all – Primarily: NA 1, NA 2, NA 3, SA 1 & SA 2 • NGI International Tasks – Mainly SA 1 – Small amount of effort in NA 2 & NA 3 • Other EGI Activities (Effort in NGIs) – SA 3, SA 4, JRA 1

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) Task Description Organisation O-E-1 GOCDB UK O-E-4 Operations Portal France O-E-8 User Requirements Germany O-E-6 Operation of a helpdesk Germany O-E-15 Security Policy UK & Netherlands U-E-5 User Technical Services Spain & Portugal U-E-1 User Forum EGI. eu U-E-3 Event Organisation EGI. eu O-E-5 Grid Operation & Oversight Netherlands & Poland Agree on allocation

Allocated Tasks (Contested) Task Description Organisation O-E-9 Middleware Rollout Spain & Portugal O-E-12 Network Support Italy O-E-14 Core Grid Services Greece O-E-2 Accounting Repositories UK & Spain O-E-10 Resource Allocation Poland O-E-11 Interoperation Sweden O-E-13 Best Practices Finland O-E-16 Security Incident Response UK & Netherlands U-E-6 Informational & High-level tools Greece Agree on allocation

Allocated Tasks (Contested) Task Description Organisation U-E-2 Coordination of SSCs EGI. eu E-E-1 Dissemination EGI. eu E-E-3 Industry Uptake EGI. eu E-E-4 External Relations EGI. eu U-E-9 New Communities & Front Desk EGI. eu O-E-7 Triage of Incoming Problems Germany & Netherlands U-E-8 Training UK O-E-17 Operational Tools Not clear U-E-7 Document Review Not 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 Active. MQ • Bids: – France, Germany, Greece, Italy, Poland & Croatia • Task description will be revised by SA 1 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 (SA 3) – YES: Call for sites with production experience in all EGI related middleware (g. Lite, ARC, UNICORE) – Criteria: Minimal set that covers most middleware and deployment environments • Operational Tools Maintenance & Development (JRA 1) – 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 SA 3 & 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 2848 PM (237 FTE) a year • Bids reviewed to assess reasonable effort – Decided a ‘reasonable’ level of effort – 7 (Armenia) 190 (Italy) PM a year – Total 2281 PM (190 FTE) 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. . . 24 PM? – Cuts 360 PM (12 FTE) to 1921 PM (160 FTE) Agree on following Funding Model 1, 2 or 3

Opt 1: EGI V 2 Activity FTE ME/year EGI. eu From EC From NGI EGI. eu 51 4. 6 2. 0 1. 6 NGI International 191 17. 3 8. 7 8. 6 NGI HUC 40 3. 6 1. 8 NGI Other 18 1. 6 0. 8 TOTAL 300 27. 1 13. 3 12. 8 1. 0 • 25 ME, 24 month project • Increase EGI. eu in Y 2=2. 6 ME

Opt 2: EGI V 2 (Reduce NGI Tasks) Activity FTE ME/year EGI. eu From EC From NGI EGI. eu 51 4. 6 2. 0 1. 6 NGI International 160 14. 4 7. 2 NGI HUC 40 3. 6 1. 8 NGI Other 18 1. 6 0. 8 TOTAL 269 24. 2 11. 8 11. 4 1. 0 • Increase EGI. eu: Y 2=2. 5 ME, Y 3=4 ME • 30 month: ~26. 0 ME • NB: Still need to refine effort for 25 ME • 36 month: ~29. 9 ME

Opt 3: EGI V 2 (Minimal) Activity FTE ME/year EGI. eu From EC From NGI EGI. eu 51 4. 6 2. 0 1. 6 NGI International 160 14. 4 7. 2 NGI HUC 31 2. 8 1. 4 NGI Other 6 0. 5 0. 25 TOTAL 248 22. 3 10. 85 10. 45 1. 0 • Use aligned EC projects (now or next year) • New Operational Tools & development (~10 FTE) • Gateway project (~6 FTE) • Cut SA 4 (-10%) & SA 3 (-25%) • Increase EGI. eu: Y 2=3 M, Y 3=5 M • 36 month: ~26. 55 ME

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 FP 7 – 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 V 2 draft • 8/10/09: V 3 draft: – Integrate comments and put into table format. – Send to consultant for high level feedback. • 15/10/09: Comments on V 3 draft • 19/10/09: V 4 draft: – Polished with completed effort tables and A 2 forms. – Send to consultant for detailed feedback. • • 23/10/09: EGI Council (Brussels) 27/10/09: Comments on V 4 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 1 M€ in year 1 and increase linearly to 2 M€ in year 4 • 90 K€/year staff cost which includes indirect costs • The Heavy User Communities funding is an average of 23 FTE 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-In. SPIRE 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)