1 / 44

TNC 2011

TNC 2011. Pau Minoves (Technical Manager) Prague, May 2011. 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€

veta
Télécharger la présentation

TNC 2011

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. TNC 2011 Pau Minoves (Technical Manager) Prague, May 2011

  2. 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

  3. Challenges VISION • Provide a software implementation and tools for providing and managing routers and IP networks as services. • Open project consideration • Public documentation • Open mailing list • Feedback and involvement are welcomed MISSION • 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 • Ether project (Ethernet and MPLS) • Argia project (Optical network devices) • Providing the service to 3 virtual research communities • Mantychore will be deployed over the infrastructure of: • 2 NRENS • NORDUnet, HEAnet • 3 initial users. • UNI-C, TCD, University of ESSEX www.mantychore.eu

  4. 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

  5. Objectives www.mantychore.eu

  6. Users and use cases www.mantychore.eu

  7. UserCommunity Grid Site 5 Grid Site 6 Grid Site 3 Enhanced IP Network as a Service 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 Health Data Network Hub Connection Agreement System router router router Authorized User router www.mantychore.eu

  8. Virtual CPE – Scenario 1 Provider’s domain (HEAnet) • Providers enforce parts of the CPE configuration • i.e. BGP policies. • Delegation of partial configuration rights to clients. • Internal IGP • VRRP • Firewall • … • Automatic provisioning of new clients. • Reduce need for new hardware deployments. CPE Client A domain Client B domain PhysicalRouter LogicalRouter SA1 Software Refinement

  9. Virtual CPE – Scenario 2 Provider’s domain (Health Data Net.) MPLS LSP’s Provider’s domain (UNI·C) • Providers enforce parts of the CPE configuration • i.e. BGP policies. • Delegation of partial configuration rights to clients. • Internal IGP • VRRP • Firewall • … • Automatic provisioning of access to provider LSP channels. • Directly or via a VPN. • Reduce need for new hardware deployments. • Reporting to existing accounting infrastructure. CPE Client A domain PhysicalRouter LogicalRouter VPN SA1 Software Refinement

  10. Virtual CPE – Scenario 2 Provider’s domain (Health Data Net.) MPLS LSP’s Provider’s domain (UNI·C) • Providers enforce parts of the CPE configuration • i.e. BGP policies. • Delegation of partial configuration rights to clients. • Internal IGP • VRRP • Firewall • … • Automatic provisioning of access to provider LSP channels. • Directly or via a VPN. • Reduce need for new hardware deployments. • Reporting to existing accounting infrastructure. CPE Client A domain PhysicalRouter LogicalRouter VPN SA1 Software Refinement

  11. Distributed and Private Cloud – Scenario 1 • Thisscenariowill use Grid-Irelandnodesto test complexcloud-likesharing of resources and flexible networks. • A gridsiteisformedby: • Infrastructurenodes • Workernodes • Currently, onlyinfrastructurenodeshaveconnectivity. SA1 Software Refinement

  12. Distributed and Private Cloud – Scenario 1 • Weforesee a twostageimplementation: • At a firststage: • Use of a L3 VPN • Policies at TCD. • Lowimpact • Willallowthe. gridsitetomeet at a NREN-managedlogicalrouter • Workednodes, willbeabletobeaggregated in a flexible cloud. SA1 Software Refinement

  13. Distributed and Private Cloud – Scenario 1 • Weforesee a twostageimplementation: • At a firststage: • Use of a L3 VPN • Willallowthe. gridsitetomeet at a NREN-managedlogicalrouter • Workednodes, willbeabletobeaggregated in a flexible cloud. SA1 Software Refinement

  14. Distributed and Private Cloud – Scenario 1 • We foresee a two stage implementation: • At a second stage: • Institutional IT departments will be involved in the setup. • Implement L2 solutions where possible. • Avoid tunneling overhead. SA1 Software Refinement

  15. Distributed and Private Cloud – Scenario 2 • Threeactorsinvolved: • Virtual Machine IaaSProvider – NREN or comercial operator. • Offer virtual privateclouds. • Configurable useraddressingspace. • L2 access. • Network IaaSProvider – NREN • SUnet. • Redundant Full meshLSPs. • Campus • Computing resourcesconsumer. • RouterpartiallymanagedbyMantychore. • Mainrequirement: • Network transparency. • Avoidanyreconfiguration of >L4 services. VM migration SA1 Software Refinement

  16. Mantychorevs new Amazon VPC • Amazon VPC launched dynamic networks on March‘11 • Amazon VPC has four templates: • A) VPC with public subnet. • B) VPC with public and private subnet. • C) VPC with Internet and VPN access. • D) VPC with VPN only access. • Mantychore will implement: • D -> C -> A. • Base technologies • Support IPv6 is being studied. • VPNs both at L3 and L2 (MPLS, pure-VLAN). • Open Source. • Inspect the source code. • Adapt, customize. • Deploy on your own infrastructure. • Integrate with existing deployed systems. SA1 Software Refinement

  17. Ultra High Definition Applications • Deployment of next generation multimedia applications • 3D, UHD • Stream producers and consumers. • 3D medical applications. • 3D virtual tourism. • Flexibility to adjust, network independent of underlying infrastructure. • Bandwidth on Demand. Physical topology USERS USERS GLASGOW Logical topology ESSEX JANET UK-IP USERS USERS CARDIFF USERS USERS SA1 Software Refinement

  18. THE TOOLSET www.mantychore.eu

  19. Mantychore Architecture • External Interface. • Pluggable(so REST easilysupported) • Currently Web Servicesbased. • Easytointegratewithotherexisting middlewares • Likecloudprovisioning. • A comprehensive GUI for desktop and Web (WIP). Resources WS Fuse ServiceMix OtherMiddleware or GUI ROADM WS Router WS Desk. IP Network WS … Web ReportingSystem SA1 Software Refinement

  20. Mantychore Architecture • Integrationwithexistinginfrastructure. • Foraccess control: • Use SAML tointegratewithexistingidentityproviders. • Forreporting • Integrationwithexisting ticket/bug systems. • Integrate Mantychore withtheorganization’scurrentworkflow and tools. • Infrastructureoperators: • Mantychore offersOperators a CLI tomanagemantychoreservices. • Profilesfeatureallowstheoperatortomodifyoroverridetheconfigurationthatissenttothenetworkequipment • Importanttoenforceinstitutionalpolicies. Resources WS Fuse ServiceMix Conf. Engine Protocol ROADM WS Router WS IP Network WS Exitinginfrastructure Access Control … ReportingSystem SA1 Software Refinement

  21. Technologies • Testing • Development FUSE ESB Kernel • Security Console Logging Provisioning Deployer Admin Spring DM OSGI Framework SA1 Software Refinement

  22. MARKETPLACE www.mantychore.eu

  23. WP6 Overall Objective • Study, design and simulation of the necessary algorithms for the implementation of the MANTYCHORE marketplace mechanism • Enable the automatic negotiation and reservation of resources between users and providers. • The capability to automatically select, orchestrate and reserve the best resources for a given request • To use the marketplace in order to allow the NRENs to announce their own infrastructure as resources of MANTYCHORE services • Users from virtual research communities will be able to access resources from several providers JRA1 Infrastructure resources marketplace

  24. Technical Progress • Study and analysis of existing and state of the art work • Review of projects and framework relevant to L3 virtualization and virtual IP resource allocation • XBONE • PLanetLab • VIOLIN • AUTOI • AGAVE • Review of existing network brokering mechanisms • Internet2 approach: NARB (Network Aware Resource Broker) • Grid approach: Market-Oriented Grid algorithms JRA1 Infrastructure resources marketplace

  25. Technical Progress • Definition of market place based use case • The use case will be based on UK Ultra-high Definition (UHD) consortium network infrastructure • The UK Ultra-high Definition (UHD) consortium is a networked infrastructure for the development and deployment of next generation networked multimedia applications and services. It consists of five members namely: University of Essex (Essex), University of Strathclyde (Glasgow), Digital Design Studio (Glasgow), University of Cardiff (Cardiff), and Technium CAST (Bangor). • The current setup is made up of three networked nodes – Essex, Glasgow, and Cardiff – which are interconnected via the JANET UK network, and is investigating the development and deployment of interactive UHD 3D media applications in the medical and cultural heritage/ virtual tourism domains. JRA1 Infrastructure resources marketplace

  26. Technical Progress • Definition of market place based use case • Use case emulated infrastructure Emulated Infrastrcuture2 Emulated Infrastrcuture1 JRA1 Infrastructure resources marketplace

  27. GREEN IT www.mantychore.eu

  28.      Scope of JRA2 • MANTYCHORE-GSN collaboration has the objective to design necessary experiments and tests which eventually check the viability of the movement of services (virtual machines (VMs and applications)) using flexible device configuration utilities such as Infrastructure as a Service and Bandwidth on Demand solutions. • Perform the integration between GSN and MANTYCHORE (physical integration between the GSN and the NRENs infrastructure and also the services integration). EPA building rooftop, Ireland Dunhill, Ireland JRA2 Zero-carbon emission virtual infrastructures

  29. GSN Objectives • Initiate a consortium of industry, universities and government agencies with the common goal of reducing greenhouse gas (GHG) emissions arising from information & communication technology (ICT) services • Create tools, protocols, procedures, and use cases for a growing network of ICT service providers that offers customers the lowest price and greenest services JRA2 Zero-carbon emission virtual infrastructures

  30. GSN Node & Network GSN associates and MANTYCHORE • GSN / Mantychore Integration team meetings active focusing on • Test Case Generation • Solution Integration requirements and benefits analysis • Training JRA2 Zero-carbon emission virtual infrastructures

  31. IBBT GSN Node JRA2 Zero-carbon emission virtual infrastructures

  32. Joinus! ENLARGE the USER COMMUNITY www.mantychore.eu

  33. 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

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

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

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

  37. Jointhecommunity • [WP3] www.mantychore.eu

  38. SurveyAvailable • Wehave (short) surveyavailable. • WewouldlovetohearyourthoughtsonMantychore and ifyouthinkitwouldfityou. • Orwhatitwouldneedtofityou. • Plus wehavesomeipad/laptop sleevesavailable. • But do itforscience, right? ;) www.mantychore.eu

  39. Findus • You can alsotakethesurvey online at: • Orfind i2CAT’s booth at: • Between DANTE and RIPE NCC. • http://fi2.cat/tnc2011survey www.mantychore.eu

  40. Thanks for listening QUESTIONS?

  41. Backup SLIDES

  42. Protocol Architecture • M2M network • Web Service • User Access • Http • Resource control • Juniper- Netconf • Cisco- WSMA (on coming) Mantychore Server WP4- SOFTWARE REFINEMENT

  43. Federation Architecture • Users can configure resources from external domains • Create/configure • Logical switches • Logical routers • IP networks • Provisioning L1 & L2 WP4- SOFTWARE REFINEMENT

  44. Complete Gantt WP4- SOFTWARE REFINEMENT

More Related