1 / 27

Helix Nebula- The Science Cloud First Review

Helix Nebula- The Science Cloud First Review. Bob Jones - CERN 03 July 2013.

tanek
Télécharger la présentation

Helix Nebula- The Science Cloud First Review

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Helix Nebula- The Science CloudFirst Review Bob Jones - CERN 03 July 2013 • This document produced by Members of the Helix Nebula Partners and Consortium is licensed under a Creative Commons Attribution 3.0 Unported License.Permissions beyond the scope of this license may be available at http://helix-nebula.eu/ • The Helix Nebula project is co-funded by the European Community Seventh Framework Programme (FP7/2007-2013) under Grant Agreement no 312301

  2. Review agenda • 09:30 - 10:00 Project Overview and Management (WP1) • 10:00 - 10:10 Q/A • 10:10 - 10:25 WP2: Engagement and Dissemination • 10:25 - 10:35 Q/A • 10:35 - 10:50 WP3: Representation of Requirements • 10:50 - 11:00 Q/A • 11:00 – 11:30 Coffee Break • 11:30 - 11:45 WP4: Cloud Platform & Provisioning • 11:45 - 11:55 Q/A • 11:55 - 12:25 WP5: Flagship Deployment • 12:25 - 12:35 Q/A • 12:35 - 12:55 WP6: Inter-operability with e-infrastructures • 12:55 - 13:05 Q/A • 13:05 - 14:00 Lunch • 14:00 - 14:30 WP7: Business Models • 14:30 - 14:40 Q/A • 14:40 - 14:55 WP8: Governance Models • 14:55 - 15:05 • 15:05 - 15:35 Summary and Plans for the next period • 15:35 - 15:45 Q/A • Closed session • Feedback from reviewers

  3. Project overview: • Objectives • Consortium • Work Packages • Management • Deliverables/milestones • Financial status • Effort consumption

  4. A European cloud computing partnership: big science teams up with big business • Strategic Plan • Establish multi-tenant, multi-provider cloud infrastructure • Identify and adopt policies for trust, security and privacy • Create governance structure • Define funding schemes To support the computing capacity needs for the ATLAS experiment • Setting up a new service to simplify analysis of large genomes, for a deeper insight into evolution and biodiversity • To create an Earth Observation platform, focusing on earthquake and volcano research Adopters

  5. Overall Objectives The Helix Nebula projectis a preliminarysteptowards a Europeancloud-basedscientific e-infrastructure 1. A platform capable of development through PPP into a scalable science cloud; 2. A flexible governance structure capable of growing alongside the infrastructure itself; 3. Representations of functional and non‐functional requirements including policies for trust, security and privacy; 4. Agreements regarding inter‐operability with other, existing, e‐infrastructures; 5. Three flagships based at CERN, EMBL and ESA (represented by CNR), selected as ‘stretch’ targets highlighting extreme cases of the requirements of the ERA and space agencies; 6. Sustainable business models adhering to and supporting European‐level policies; 7. A roadmap and development plan for addressing issues on the road to 2020.

  6. WorkPackages

  7. Work Packages • WP1: Management & Coordination (CERN) • WP2: Engagement and Dissemination (Cloud Security Alliance) • WP3: Representation of Requirements (CloudSigma) • WP4: Cloud Platform & Provisioning (Atos) • WP5: Flagship Deployment (Logica) • WP6: Inter-operability with e-infrastructures (EGI.eu) • WP7: Business Models (SAP) • WP8: Governance Models (T-Systems) • WP9 (starts M16): Evaluation Roadmap and Development Plan (EMBL) Duration: 2 years Start Date: 01 June 2012 EC co-funding: 1.8 Million €Total budget: ~2.9 Million€ Total effort: 202 person months Proportion of effort by work package

  8. Relationships between work packages WP1 - Coordination WP2 – Engagement and Dissemination

  9. Consortium

  10. EC Project Beneficiaries • 10 beneficiaries within a wider initiative of partners • The Helix Nebula Initiative has grown from 20 partners at the start of the EC project in June 2012to 34 members in June 2013 • The overall initiative: • 15 Suppliers • 13 Adopters • 8 Users • The EC project Beneficiaries: • Suppliers: 7 • Users: 3

  11. Members of the HelixNebula Initiative

  12. Members of the HelixNebulaInitiative (cont.)

  13. Management

  14. Management Structure Signed on 22.06.2012 Signed by all parties in November 2012 Published on 31.05.2012 Amended on 24.04.2013 • Weekly management team teleconferenceschaired by CERN (41 in period 1): • Attended by 3 suppliers + 3 demandsiderepresentatives + 1 invited • Collaboration Board Meetings chaired by EMBL: • 06 July 2012, CERN, Geneva, Switzerland • 18 January 2013, ESRIN, Frascati, Italy

  15. Management Tasks • The pre-financing was distributed in two installments to avoid overspending of funds without achievement of tasks • Successful launch of a dry-run of the financial reporting process covering the first 7 months of the project in order to: • identify any missing information and issues that could arise • Monitor the resourceconsumptionduring the first half of the period • Review of progress and plans at the General Assemblies • The open repository for all Helix Nebula documents on the CERN Document System (CDS) • The contents of the communication tools (website Facebook, Twitter) approved by Mgmt Team. Websitehostedby CloudSigma (at no cost to project) • The AlfrescoShare Entreprise collaboration tool to share documents within the inititiative/projectprovided by EMBL (at no cost to project) • The 21 email lists (hosted EGI.eu and CERN at no cost to project)

  16. Quality Assurance: ReviewProcess Work Package Internal Review • Review procedure documented as Annex 7 of the Consortium Agreement: • All first period deliverables submitted • All milestones achieved and documented Helix Nebula Deliverable Formal Review Consortium Review Management TeamReview Publication EUReview

  17. Grant Agreement Amendment: • Electronic-only transmission and signatures • Use of the electronic-only signature and transmission of financial statements and electronic-only transmission of certificates for all future financial statements (Forms C) and certificates (Forms D and E) • Modification of Annex I – Description of Work • Annex I – Description of Work is modified The revised Table A3 (budget breakdown) and WT8 (project effort and what it costs) of Annex 1, dated 10 April 2013 have been modified to modify the cost of personnel for beneficiary CNR according to the funding scheme: 6 PM funded and 5 unfunded.

  18. Deliverables – Period 1

  19. Milestones

  20. Financial Status

  21. Resources and Funding • The Helix Nebula pilot phase rests on financial support from: • Co-funding by the EC • Significant contribution from members of the overall initiative that are not beneficiaries of the project: • ESA and CNES (220 k – 1.7 FTE for 9 months) • SMEs: SixSquare, Terradue, TheServerLabs involved in TechArch and ServArch • Dante & NRENs: Effort to connect supplier data centres to GEANT • Users’ contribution (First year flagship deployments) to: • The cost of the resources consumed (flat-rate of 420 K) • Manpower (3.7 FTE for 39 Months) • Second Year flagship deployments: Costs according to the price models provided by the suppliers • EC funding focused on: • Coordinating beneficiaries’ efforts and animating the whole initiative • Communication and Outreach

  22. Provisional Financial Status • Based on Beneficiaries’ Cost Claims for Period 1 • Total Costs: 1,038,934 EUR • 63 % of total budgeted costs • Total Requested Contribution: 801,548 EUR • 74% of budgeted requested contribution • Direct personnel costs are 72 % of total costs • Remaining costs are travel, other costs and overheads

  23. Total Cost per Beneficiary

  24. Provisional Financial Status Over-spending beneficiary Task of defining the cloud platform and provisioning required more work than originally foreseen. Has required more highly-skilled and experienced staff than we expected Most under-spending beneficiaries - WP2 cost will be consumed in P2 - Work of a trainee not charged to the EC project - Work completed using effort funded from other sources - Project funded effort will be concentrated on WP5 in P2 - Spent 50% of the WP5 - WP3 effort needed was below expectation - WP2 cost will be used in P2 No impact on DoW. All beneficiaries contributing to project 24

  25. Effort Consumption

  26. Total Effort by Beneficiary Transition from the PoC to the pilot deploymentstook longer thatexpected The unspent effort willbeused in WP5 26

  27. Total Effort by Activity

More Related