ONOS and CORD. About the Platforms, Deployments and their Communities. Taipei, November 25th 2016

Transcription

1 ONOS and CORD About the Platforms, Deployments and their Communities Taipei, November 25th 2016

2 Outline Who we are and what is our mission The platforms Roadmaps Deployment updates Communities How do I get involved?

3 Who we are, our mission Prepared by David Boswell for Board meeting on March 18, 2016

4 Open Networking Lab (ON.Lab) Nick McKeown Scott Shenker Guru Parulkar Larry Peterson KP, Mayfield, Sequoia Professor, Stanford Professor, UC Berkeley Chief Scientist, ICSI Executive Director ONF, ON.Lab, Executive Director ONRC Consulting Professor, Stanford Robert Kahn Professor Princeton (Emeritus)

5 Our Mission ONOS & CORD are building a better network We are pursuing our vision of what networking could be for the public good We want to fix closed, proprietary, complex, expensive and inflexible networks We want networks that are enabling innovation rather than impeding innovation Join us on our mission!

6 What are known for Mininet OpenVirtex (OVX) Open Networking Operating System Central Office Re-architected as Datacenter

7 The platforms #CORDProject #ONOSProject

8 ONOS Open Network Operating System (ONOS) is an SDN Operating System for Service Providers that has Scalability, High Availability, High Performance and Abstractions, to make it easy to create apps and services. The platform is based on a solid architecture and has quickly matured to be feature rich and production ready. 8

9 ONOS Architecture Apps CORD SDN-IP VPLS Packet-Optical NB Core API Distributed Core (state management, notifications, high-availability & scale-out) SB Core API Providers Providers Providers Providers Protocols Protocols Protocols Protocols

10 SDN-IP CORD OpenStack Integration Load Balancer Segment Routing DHCP Server Virtual Tenant Networks Service Function Chaining Distributed DPI Fault Management Virtual Private LAN TL1 OSPF PCEP IS-IS SNMP OVSDB REST P4 LISP BGP OpenFlow NETCONF

11 CORD CORD (Central Office Re-architected as a Datacenter) combines NFV, SDN, and the elasticity of commodity clouds. It aims to bring datacenter economics and cloud agility to the Telco Central Office. 11

12 CORD CORD aims to deliver to Service Providers Economies of a Data Center: Infrastructure built with a few commodity building blocks using open source software and white boxes Agility of a cloud provider: Software platforms that enable rapid creation of new services 12

13 CORD 13

14 Roadmaps #CORDProject #ONOSProject

15 ONOS: Near-Term Roadmap Dynamic Configuration (in progress) Virtualization (in progress) GUI Scalability (in progress) In-Service Software Upgrade grpc API Federation (hierarchical & peering) Intent Subsystem 2.0 (a.k.a Intent Domains) Distributed Platform & Network Core Separation

16 Getting there... Brigades - harnessing the power of community Started with 4 brigades help to make forward progress on key ONOS roadmap items ON.Lab & TST acting mostly as shepherds Deployments Brigade Dynamic Configuration Brigade Virtualization Brigade GUI Brigade Number of brigades may grow in the future

17 CORD: Near-term roadmap Platform E-CORD Consolidation of tests, bug fixes and installation process Field trials E/M CORD soon running on the CORD platform zero-touch provisioning M-CORD Connectionless EPC for IoT device: replacing SGW&PGW data plane with single OVS open EPC with disaggregated MME

18 Deployment updates #CORDProject #ONOSProject

19 Motivation and Goals REN, Network Operators and Users ONOS community Create a global SDN network Demonstrate ONOS in real networks Provide L0, L2 and L3 connectivity, without legacy equipment in the network core Test High performance, HA and scalability in real networks Enable network and services innovation Learn and improve Requirements/Learning/Bug Fixes Agile collaboration model ONOS and Use Cases

20 Global SDN Deployment Powered by ONOS Q Korea announces the first ONOS deployment OF OpenFlow Q1-Q First ONOS Deployments South America, US, EU Q New connections Miami - Korea Miami - Taiwan Korea - Taiwan Q New connections Sidney Seattle - Miami Sao Paolo Amsterdam Q ONOS deployed in Korea Q NCTU / Taiwan deploys ONOS OpenFlow Q First ONOS production deployment in South America OpenFlow Q ONOS Deployment in Australia

21 How the testbed works? OF OpenFlow AS #20080 AS #65111 ebgp OpenFlow over L2 dedicated circuits OpenFlow

22 ONOS deployment requirements What RENs ask for A simple solution that works Layer 0/1: Lambda / OTN allocation Layer 2: Connect multiple end-points + MEF standards + NSI Layer 3: Internal and International BGP Peering Network slicing / Virtualization What SPs ask for All above.. Yang, NetConf support Simplify and reduce CAPEX/OPEX in Access and Metro Networks As always High performances, HA, scalability Being Carrier Grade

23 RENs, Action Plan XOS (E-CORD) Ability for both Users and Operators to allocate end-to-end resources at multiple layers.. Orchestrator SDN-IP / SDX-L3 / Castor - BGP peering between internal Users - International peering OpenFlow switches Layer 3 VPLS + CE + BoD CORD / ONOS Applications - Point-to-Point Circuits - Broadcast L2 networks on demand Layer 2 Packet-Optical Optical circuits Layer 0 /1 #ONOSProject 23

24 The Federated Testbed Initiative Goal: Create a federated 5G playground for the industry. Experiment SDN, NFV and cloud technologies in a multi-domain, multi-vendor environment, looking forward to 5G. Based on the SoftFIRE testbed infrastructure Integration of ONOS and CORD Control of the infrastructure Act as platform to evaluate for Users Driven by EIT Digital First Participants: Deutsche Telekom Ericsson Fraunhofer FOKUS IEEE Politecnico di Torino TIM (JolNET) University of Surrey

25 CORD is real: PoC and Deployments Residential CORD 1 year from PoC to Field Trial June 2016: Field Trial with Large SP OpenCloud CORD deployment on Internet2 CORD pods installed in university campuses 5 universities already connected [R,E,M] CORD PODs at ON.Lab Demonstrated at ONS 2016 and major events #ONOSProject 25

26 ONOS & CORD communities Prepared by David Boswell for Board meeting on March 18, 2016

27 ON.Lab s Community Team David Boswell and William Quiviger have been hired to accelerate the growth of the ONOS and CORD communities Both have years of experience at Mozilla and other open projects They re bringing proven best practices that are helping quickly scale the community and increase community members impact

28 ONOS and CORD Member Growth 30+ new collaborators so far in 2016 and more are joining every month

29 Partners Leading service providers make ONOS & SDN/NFV solutions relevant to them Leading vendors help make ONOS and SDN/NFV solutions real & ready for deployment

30 ONOS Collaborators Collaborating organizations help grow the community and grow the impact

31 CORD Collaborators Some collaborators are also involved in ONOS and some are involved in CORD only

32 Community Building Empowering partners and collaborators (Ambassadors, Brigades) Building internal capacity to work with community Expanding community infrastructure

33 Summary Platforms ONOS and CORD are out as Free, Open Source Projects Compelling applications validated (Packet-optical, VPLS, SDN-IP, SDX-L2/L3, Castor) Deployments ONOS and (~)CORD has been extensively tested and deployed Global SDN Deployment: ~60 OF switches, 12 institutions connected across 5 continents Community New community managers Impressively growing community Lots of events: meetups, workshops, conferences New programs to participate to: ambassadors, brigades Future work From demo and field trials to production (this is happening at AmLight!) E-CORD, M-CORD implementations soon public New use-cases, new deployments Commercial operator field trials, 5G federated testbed Focus on stability, performances and scalability

34 How do I get involved?

35 Contribution Opportunities Coding Documentation Spreading the word Deployments And more Find this on the wiki at:

36 In depth

37 Dynamic Configuration Introduce model-driven configuration capabilities YANG Compiler registry of compiled models; translates between representations YANG Store compiles YANG models into Java DTO classes & schema meta-data YANG Runtime service & device configuration via standard & custom models service to distribute and persist model schemas & instance data NETCONF & RESTCONF apps facilitate configuration interactions using standard protocols

38 Virtualization ONOS as network hypervisor Produces SDN-capable virtual networks with topology and without implicit connectivity connectivity is explicitly programmed via REST & OpenFlow APIs permits arbitrary topologies, from Big Switch to isomorphic Protocol independent & modular using OVX model aimed at virtualization for off-platform apps on-platform apps can be network-aware, not network-specific manual or programmatic network embedding support for arbitrary data-plane virtualization mechanisms

39 GUI Scalability Enhancements Allow users to use GUI in large network deployments Nested & customizable layouts focus on usability and flexibility of topology layouts manage amount of information on the screen via zooming in/out physical layouts, e.g. geographical map, floor-plan, rack logical layouts, e.g. spine-leaf Customizable icon scaling allows users to adjust the density of information on screen Revised GUI glyphs for map entities & buttons Global search

40 In-Service Software Upgrade Mechanism for gradually upgrading an ONOS cluster upgrades cluster one node at a time without downtime Requires portable serialization for cluster comms upgraded nodes must be able to speak the old language

41 grpc API Allow fine-grained & high-performance interactions between ONOS and off-platform apps presently available only for on-platform apps via Java API REST API suitable only for relatively low-frequency & coarse interactions Enables apps to be run on or off platform permits compute resource isolation off-platform apps as micro-services Allows ONOS apps to be written in other languages

42 Cluster Federation Coordination mechanism for multiple ONOS clusters permits peer-to-peer & hierarchical arrangements aims to support different administrative domains Peer-to-peer variant being developed by GEANT

43 Intent Subsystem 2.0 Based on networks comprising of regions with different technologies & limitations Offers composable network-centric primitives different regions of network can use different means to satisfy an intent multiple intent domains within a single administrative domain e.g. tunnel, default route, {broad multi any}cast efficient use of network resources via shared use of primitives Offers apps to negotiate/select from alternatives presently only one intent solution is implicitly selected

44 Platform & Core Separation Separate the distributed network-agnostic platform from the network-aware core subsystems Presently the separation is logical, but there exist some (albeit weak) ties between the two Requests for such platform from Fermi & Oakridge Labs, among others provides significant benefits in context of SDN as well