1 / 119

MANTYCHORE Grant Agreement No.: 261527 Intermediate Review

MANTYCHORE Grant Agreement No.: 261527 Intermediate Review. Sergi Figuerola (Project Coordinator) Pau Minoves (Technical Manager) Victor Reijs (NA2 Leader) Brussels, March 2011. Agenda. 13:00 - Welcome and participants presentation. 13:10 - Mantychore project overview.

salome
Télécharger la présentation

MANTYCHORE Grant Agreement No.: 261527 Intermediate 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. MANTYCHOREGrant Agreement No.: 261527Intermediate Review Sergi Figuerola (Project Coordinator) Pau Minoves (Technical Manager) Victor Reijs (NA2 Leader) Brussels, March 2011

  2. Agenda • 13:00 - Welcome and participants presentation. • 13:10 - Mantychore project overview. • 13:20 - Open project considerations. • 13:30 - WP1 Project Management: resource used, Gantt update and general questions/comments. • Clarifications and updates of the DoW. • 13:45 - Overview of the work done on the different work packages. • WP2 Dissemination Exploitation, Standardisation and Liaisons. • WP3 Consolidating user community and User Training. • WP4 Software refinement. • Use Case definition and updates. • WP5 IP Network as a Service for Virtual Research Communities. • WP6 Infrastructure resources Marketplace. • WP7 Zero-Carbon emission virtual infrastructures updates. • 15:45 - Open questions from the reviewer. • 16:00 - End of the meeting. Agenda

  3. Overview Mantychore project OVERVIEW

  4. Mantychore @ a Glance • Mantychore legacy • 2006 – Manticore • 2007 – Manticore II • (also with RedIris, Cisco and Juniper) • 2010 – Mantychore FP7 • ICT-2010 Call 7 • 1.2.3 – Virtual Research Communities • Total Project Cost: 1,564,386€ • EC contribution: 1,399,740€ • Start date: October 2010 • Duration: 30 months • Partners composition • 1 Research Center • 2 NREN • 3 users • 1 commercial operator Overview

  5. Our Challenge VISION • Provide a software implementation and tools for providing and managing routers and IP networks as services. MISION • By means of : • Infrastructure Provisioning: • Marketplace of Physical/logical routers and IP networks • IP Network as a Service: • Creation and configuration of IP networks • L1 and L2 integration • Providing the service to 3 virtual research communities • Mantychore will be deployed over the infrastructure of 2 NRENS and 3 initial users. Overview

  6. User community e-Health, Media and Grid Grid Site 5 Grid Site 6 Grid Site 3 IP Network as a Service Enhanced Grid Site 1 Grid Site 4 Grid Site 2 VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VMs VMs VMs VMs VMs VMs Dedicated IP Networks to support media services (Wales and Scotland), Grid-Ireland “Cloud Layer”, TCD Improving the Health Data Network, Fixed connections + VPNs + MANTICORE managed IP Networks router Site 1 Site 2 router router Health Data Network Hub Connection Agreement System router Authorized User router Overview

  7. Objective 1: Deploy an operational IP Network as a Service Enable HEAnet and NORDUnet to provide IP Network Services to their users through the MANTYCHORE tools, enhancing their service portfolio; thus providing virtual research communities with a useful service that can improve their research activities and optimize the efficiency of use of e-Infrastructures. Mantychore allow third parties to configure network addressing, internal routing, firewalls and external routing policies. Objective 2: Integrated Layer 1-3 services Refine and expand the MANTYCHORE services provided by means of integrating, with IaaS tools, solutions for optical and Ethernet/MPLS networks (Ether); thus being able to provide integrated services at levels 1-3 to the research community. Overview

  8. Objective 3: Marketplace for resource trading Innovate in the business model used in services based on IaaS, establishing a marketplace where all Infrastructure Providers can publish their available resources with their usage conditions (SLA, price), and all customers can automatically negotiate the SLAs getting the best resource combination for their needs. Objective 4: Carbon-neutral e-Infrastructures Use MANTYCHORE services to contribute to the research performed in the GreenStar Network (GSN) project to enable carbon-neutral infrastructures. Objective 5: Commercial Exploitation • Evaluate the likehood of MANTYCHORE services (open source based) in a commercial telco environment and elaborate a business plan focused on this service for telco operators. Overview

  9. Open project CONSIDERATIONS Open Project

  10. Open Project Considerations • Expected benefits • Better external user involvement via increased transparency. • Welcome feedback and involvement. • Better outcome quality via public exposition of results. • i.e. project documentation. • Simplified communication infrastructure. • Closed mailing list for consortium-internal discussions. • Open mailing list for all technical discussions. • Welcome foreign contributions to the project effort. • Collaborate with interested developers. • Allow other projects to inspect our assets and look for reusable contents. Open Project

  11. Open Project Approach • Official Website • Points to all the resources • www.mantychore.eu • Open Wiki • http://jira.i2cat.net:8090/display/MANTECH/Home • Open Mailing list • Open technical • Archives online • http://listas.i2cat.net/cgi-bin/mailman/listinfo/mantychore-technical • Open Source • http://anon:anon@svn.i2cat.net/repos/manticore/ Open Project

  12. Open Project Approach • How to get a copy of the source code News Pointers to all past presentations Archives Open Project

  13. Open Project Approach • Partner only area Pointers to all participation channels Open Project

  14. Open Project Approach • User Documentation • Working Area • Work Packages and Task have spaces here • Deliverables are published here • Public read-only Private area Open Project

  15. Achievement of the project objectives • The project is evolving as expected with two course technical corrections with regards to the DoW. • Course corrections: • IaaS Framework • The work together with Canadian and EU partners has been delayed (>6M) due to other priorities. • Mantychore has decided to fork it and create an internal version suitable for Mantychore requirements. • Functionality integration with GSN is independent. • Done via the external API, so little impact in WP7. • Ether • Currently evaluating integration with OSCARS. • NRENs (NORDUnet) are more interested in MPLS services for cloud scenarios • Some trials on OSCARS are already ongoing in NORDUnet • It may also extend collaboration with GN3, ESnet & Internet2 Overview

  16. Research/performance indicators I • This section presents some of the actions that are taken towards preparing the assessment of the Mantychore indicators (p.36 DoW) • Performance / Research indicators of project results: • Scalability • Field scalability tests will be performed on late stages of T5.1 • Manageability • T4.1 Requirements Analysis has identified operation steps • Continuous feedback and interviews from operator users will help streamline the user experience. • Mantychore will integrate wherever possible with existing infrastructure in order to achieve low administration over-head. Overview

  17. Research/performance indicators II • Deployability • SA2 development team will implement an automatic deployment of updates. • User Manuals will be updated with deployment setup requirements. • Ease of Use • User specific interfaces. • User specific documentation and training. • Reliability • Mantychore has a strong emphasis on keeping the network configuration coherent even in case of failure. • Extensibility • Mantychore, as Manticore 2, implements a modular architecture that supports several extension points. • Mantychore will innovate and allow further customization to adapt to the operator’s own network policies. • Controllability • The ACL system implemented at Manticore 2 will be updated and refined with the current use cases. Overview

  18. NA’s Status

  19. NA1, NA2 and NA3 NA1 – Project Management. NA2 – Dissemination, Exploitation, Standardisation and Liasons. NA3 – ConsolidatingtheUserCommunity and Users Training. NAs

  20. NA Workplan Y1 M15 M14 M13 M12 M11 M10 M1 M3 M2 M4 M0 M6 M8 M5 M9 M7 M1All Project Management procedures in place and operational D1.1Project Presentation M5First version of the project website M6Related events, projects and standards identified. Exploitation, dissemination and standardisation plan is ready D2.1MANTICORE exploitation, dissemination, standardisation and liaison plan M7 Project website ready D2.2Project website D3.1 User manuals M10 First Training completed M11Internal report about the status of the user community Time NAs

  21. NA Workplan Y2 M15 M14 M13 M12 M10 M11 M9 M8 M6 M5 M4 M3 M2 M1 M0 M7 D2.5 Mantychore Software business plan D1.2First Periodic Activity Report • D2.3Report on related research, exploitation and dissemination activities and planning update M2 First project review successfully completed Time NAs

  22. NA Workplan Y2-3 M28 M16 M19 M20 M21 M22 M17 M24 M25 M26 M27 M29 M23 M18 M30 M12User community consolidated D3.2 User community final report M8At least 2 contributions done in workshops or other public events M13 Second training completed M9At least 1 liaison with other projects and groups D1.3Final activity report D2.4Report on standards, exploitation, liaison and dissemination activities M3Final project review successfully completed D1.4Project results evaluation report M4All project documentation completed Time NAs

  23. WP1 NA1 resource used, Gantt update and general questions/comments NA1 Project Management

  24. Project Management - Admin • Proposed changes • Overall Progress • Deliverables • Milestones • PMs (planned vs. spent) • Costs (planned vs. spent) • Plans for the next months NA1 Project Management

  25. Small Changes in tasks and Manpower Distribution (I) • TCD • We propose to move 3 MM from Task 5.2 to 4.1 • Extend Task 4.1 to end on M9 (from M6) • New status • Increase TCD’s WP4 effort from 3 to 6 MM (M1 to M9) • Decrease TCD’s WP5 effort from 19 to 16 MM • The overall effort of TCD will not vary • Positive impact on the progress of the project • HEAnet • Some preparation actions are done before the task starts to improve the efficiency • Task 2.2 – Exploitation (Start: M13, End: M30) preparation activities 0.15 MM before its actual start (M8 to M13) NA1 Project Management

  26. Small Changes in tasks and Manpower Distribution (II) • WP5 • Some preparation actions are done before the start to improve the efficiency • Task 5.1 – Deployment and operation of MANTYCHORE at NRENs (Start: M10, End M30). • Pre-validation: few MM and 2 meetings. • Advance start from M10 to M7 • Impact < 1 MM on actual task • UPC (Third Party of i2CAT) • Re-allocation of a part of the contribution of UPC from WP4 to WP2 (max. 1.5 MM) NA1 Project Management

  27. Project Management - Admin • Proposed changes • Overall Progress • Deliverables • Milestones • PMs (planned vs. spent) • Costs (planned vs. spent) • Plans for the next months NA1 Project Management

  28. Project Management - Admin • Overall Progress • Deliverables • Milestones • PMs (planned vs. spent) • Costs (planned vs. spent) • Plans for the next months NA1 Project Management

  29. Deliverables ü ü ü ü NA1 Project Management

  30. Extra Deliverables ü NA1 Project Management

  31. Project Management - Admin • Overall Progress • Deliverables • Milestones • PMs (planned vs. spent) • Costs (planned vs. spent) • Plans for the next months NA1 Project Management

  32. Milestones ü ü ü ü ü NA1 Project Management

  33. Project Management - Admin • Overall Progress • Deliverables • Milestones • PMs (planned vs. spent) • Costs (planned vs. spent) • Plans for the next months NA1 Project Management

  34. PMs (planned vs. spent) • Resource usage from M1 to M3 • Initially planned 12.12 MM • The actual usage of person months is compared – for the sake of simplicity – to a quasi-linearly planned distribution function. The actual usage will have peaks at specific times during the project lifetime. • Actual mm used 9.55 MM + 0.7 MM in-kind contribution (84.6%) • The usage of human resources is considered in-line with expectations and contributions planned. NA1 Project Management

  35. PMs (planned vs. spent) Actual + In-Kind = 84.6% of Planned Actual = 78.8% of Planned NA1 Project Management

  36. PMs (planned vs. spent) • Use of resources M1 to M3 • The particular case of UESSEX: • Initially planned 1.98 MM • Actually spent 0 MM • Due to some personnel recruiting delays. • But UESSEX has performed an in-kind contribution • 0.7 MM • TCD has participated in planning of training (task 3.2) • In-kind contribution NA1 Project Management

  37. PMs (planned vs. spent) • Use of resources on M1 to M3 • Some partners have spent some resources in the preparation and discussions on tasks not yet started on the Gantt (total 1 MM). • WP3: 0.05 MM (UNI-C) • WP5: 0.17 MM (NORDUnet) + 0.15 (UNI-C) • WP7: 0.12 MM (NORDUnet) + 0.51 MM (HEAnet) NA1 Project Management

  38. PMs (planned vs. spent) NA1 Project Management

  39. PMs (planned vs. spent) NA1 Project Management

  40. Project Management - Admin • Overall Progress • Deliverables • Milestones • Changes • PMs (planned vs. spent) • Costs (planned vs. spent) • Plans for the next months NA1 Project Management

  41. Costs (planned vs. spent) • Other expenditures • Durable equipment: • Actual expenditure 28.03 € • Not yet significant • Some equipment has not been purchased yet • Depreciation applied only on a part of the period • Travel expenses • Actual expenditure 6,829.25 € (8.1% of the travel budget) NA1 Project Management

  42. Costs (planned vs. spent) • Other • Actual expenditure 2,670.39 € ( MGT ? ) • Other expenditures • Consumables • Actual expenditure 663.56 € ( Equipment ? ) NA1 Project Management

  43. Project Management - Admin • Overall Progress • Deliverables • Milestones • Changes • PMs (planned vs. spent) • Costs (planned vs. spent) • Plans for the next months NA1 Project Management

  44. Plans for the next months • QPR – 2, and following reports • Allocate In-kind contributions to strengthen contingency plans • Collaboration with GSN from day one • Changes of MM between WPs (TCD, HEAnet and UPC) • Re-allocation of a part of the contribution of UPC from WP4 to WP2 (1.5 MM) NA1 Project Management

  45. WP2 NA2 Dissemination, exploitation, Standardization and liasions STATUS NA2 Dissemination, exploitation, Standardization and liasions

  46. Overview and tasks 46 • Participants: HEAnet (leader), i2cat, NORDUnet, TID, TCD, UNI-C & University of Essex • Goals: • Provide a web/wiki/blog presence and general external communication deliverables (OK) • Provide frame works, guidelines and support for the other Mantychore WPs to do their dissemination, standardisation and liaisons (OK) • Stimulate project tools/service utilisation by ICT industry and a positive impact on social economic developments • T2.1: Dissemination • Providing press releases and Internet presence. Providing guidelines for papers, presentations and demonstrations • T2.2: Exploitation • One of key activities of Mantychore project. Stimulate project tools/service to be used by ICT industry and a positive impact on social economic developments • T2.3: Standardisation • Provide guidelines, feedback and possible contribution to standards in Mantychore’s environment • T2.4: Liaisons • Provide guidelines for liaisons with related initiatives and/or project, which might benefit from Mantychore NA2 Dissemination, exploitation, Standardization and liasions

  47. Status (I) • T2.1 Disseminiation • Started on October 2010 – March 2013 • Goals: • Milestone M5: First version of the project website • Milestone M6: Related events, projects and standards identified. Exploitation, dissemination and standardisation plan is ready • Deliverable D2.1 : MANTICORE exploitation, dissemination, standardisation and liaison plan  • Milestone M: Project website ready  • Deliverable D2.2: Project website (http://www.mantychore.eu/)  • T2.2 Exploitation • Starts on October 2011 – March 2013 • Status • Some preparational activities have started (like the exploitation plan part of D2.1) NA2 Dissemination, exploitation, Standardization and liasions

  48. Status (II) • T2.3 Standardisation • Started on March 2011 – March 2013 • Status: • Standardisation plan has been made as part of D2.1 • Different levels have been agreed: follow, participate, contribute, liaison • Special interest on NVRG (IRTF) and OGF (IsOD-WG) • http://jira.i2cat.net:8090/display/MANTECH/IRTF+VNRG+-+Threads+and+useful+information+to+participate • T2.4 Liaison • Started on February 2011 – March 2013 • Status: • Liaison plan has been made as part of D2.1 • Different liaison strategies made for Peering organisations, Providers and Users • An MoU with GreenStar Network (GSN) project • Establishing contact with GN3 on three fronts: network virtualisation (GN3-JRA1-T4), GSN use case description (GN3-NA4-T1) and possible use of GEANT BoD in WP7 (GN3-SA2-T2). NA2 Dissemination, Exploitation, Standardization and Liaisons 48

  49. Dissemination criteria • Every Call for papers will be marked with the following criteria. • Regarding the topic: • Strategic value according to DoW (agreed by the WP2 responsible) • 0: minor relevance • 1: relevant • 2: essential • Number of partners participant (more is better): • 0: 1 partner. • 1: 2 partners. • 2: More than 2. • Regarding the targeted forum (universal impact of the action to disseminate): • Higher mark indicates more priority in the action 1 CORE index: http://www.core.edu.au/ NA2 Dissemination, Exploitation, Standardization and Liaisons 49

  50. Procedures • CFP, workshops, journals,… should be announced. • Uploading the information and deadline. • To the Calls Section at http://jira.i2cat.net:8090/display/MANTECH/T2.1+Dissemination • Before submitting, preliminary information should be uploaded to the Wiki (http://jira.i2cat.net:8090/display/MANTECH/Proposals) and contact the responsible person to make a preliminarselection. • 4types of Parameters considered • Universal impact of the publication. • JCR Impact Factor • CORE list • Standarizationimpact • Strategic impact for the Mantychore project. • Target • Scope • Current DoW commitments • Special interest arising from a subset of partners and virtual research communities. • Moreover, associated costs and distance will be included in considerations. • If the proposal is considered as discarded, the reason will be marked at the wiki. • If the proposal is considered as interesting, it will be forwarded to the Coordination Board for final approval. • If agreed, it will directly go to the TEC that will analyze what WPs should lead it and the suggested person to edit it. NA2 Dissemination, Exploitation, Standardization and Liaisons 50

More Related