WIXLIB

The Open Network Operating SystemCarmelo Cascone, Andrea Campanella, Andrea BianciniPolitecnico di Milano, Università degli studi di Milano & ON.Lab, Reti S.p.a.CommTech Talks, DEIB, Politecnico di MilanoOctober 25, 2016#ONOSProject

Outline- Why do we need a network OS?-Motivating the need for Software-Defined Networking- ONOS overview-ArchitectureAPIsApplications- Demo- Deployments and use cases- Community & how to get involved#ONOSProject2

What is ONOS?Open Network Operating System (ONOS) is an opensource Software-Defined Network (SDN) operatingsystem.What is SDN? Why do we need a network OS?#ONOSProject3

Basic network abstractions Data plane Basic packet forwarding functionality Usually implemented in hardwareUses only local information Forward, filter, buffer, mark, rate-limit, and measure packetsf(pkt header, input port) output port or dropUsually abstracted with tables E.g. routing tables, switching tables, ACLs, etc. Control plane This talk & ONOSCompute the configuration of each physical device Data planeRouter or switchE.g routing, isolation, traffic engineeringUsually implemented in softwareBased on global information #ONOSProjectControl planeE.g. f(net topology graph, weights) routing table4

Traditional networking paradigmControl functionsE.g. routing, isolation, traffic engineeringForwarding HWState distribution mechanismE.g. topology, link utilizationControl planeData planeForwarding HWRouter or switch#ONOSProjectStandard protocolStandard protocol 2Standard protocol 3Forwarding HW5

Designing control functionsE.g. to define a new routing protocolGiven a network of arbitrary topology and size.1. Design a distributed algorithm Each device has the same topology view, is aware of link failures.2. Handle communication errors Network is unreliable: packets dropped, arrive out of sync.3. Define a communication protocol4. Wait for standardization5. Wait for vendors to adopt the standardIt takes years. What if there’s a bug?#ONOSProject6

Closed market (until 2008)FeatureFeatureLittle ability for small players andresearchers to implement or trynew features.Operating SystemSpecialized packetforwarding HW#ONOSProjectSame vendor, closed platform7

Software-Defined Networking (2008)What is all about?The “Scott Shenker view”: Define software abstractions that can be reused whenbuilding control plane functions State distribution abstraction Solve the problem once, for every functionForwarding abstraction Control the data plane in a vendor-independent mannerHow? Separation and centralization of the control plane#ONOSProject8

SDN ArchitectureAppAppAppControl planeLogically centralizedi.e. distributedTopology graph metadataHandles state distribution,data plane configurationmanagement, errorrecovery.Network OSForwarding APIForwarding HWForwarding HWData planeForwarding HW#ONOSProjectForwarding HW

Designing control functions with SDNE.g. to define a new routing protocolGiven a network of arbitrary topology and size:1. Write an algorithm over a data structure The topology graph, annotated with metadata2. Program it via a software API3. What if there’s a bug? #ONOSProjectSolve it and push a software update!SDN enables innovation at the speed ofwriting and deploying software!10

SDN VirtualizationAppAppAppVirtualizationControl planeTopology graph metadataNetwork OSForwarding abstractionForwarding HWForwarding HWData planeForwarding HW#ONOSProjectForwarding HW

OpenFlow (2008) The most prominent SDN forwarding abstractionBut not the only one. 1) Install/update rules2) Packet/port notificationselnnhaclrontNetwork OScoMatch-action tablePacket#ONOSProjectIP srcIP destTCP dest.Actions192.168/1610/8any Port 2192.168/16any80 Rate limit, Port 13any192.168/1622 Dropanyanyany Send to controller12

SDN Ecosystem Today Wide adoption in data center networks Google, Facebook, Microsoft, etc. Big service providers starting to transition their networks AT&T “Domain 2.0” project, Verizon, Deutsche Telekom, etc.Becoming more software company White-box switching market New vendors offer cheap, off-the-shelf OpenFlow HW switchesFacebook OCP project open sourced a HW design for a SDN switch New players in the “softwarized” networking market VMware offers an SDN virtualization solution called NSX#ONOSProject13

What is ONOS? SDN network OS Provides abstractions to make it easy to create apps andservice to control a network. Designed for scalability, high availability, andperformance. Focus on service provider networks, but not limited to it#ONOSProject14

Key Performance RequirementsAppsAppsHigh Throughput: 500K-1M paths setups / second 3-6M network state ops / secondHigh Volume:ONOSGlobal Network View / State 500GB-1TB of network state dataDifficult challenge!#ONOSProjecthigh throughput low latency consistency high availability15

Architectural Tenets High-availability, scalability and performance required to sustain demands of service provider & enterprisenetworks valid also for datacenters Strong abstractions and simplicity required for development of apps and solutions Protocol and device behaviour independence avoid contouring and deformation due to protocol specifics Separation of concerns and modularity allow tailoring and customization without speciating thecode-base#ONOSProject16

ONOS ArchitectureAppsAppsNB Core APIDistributed Core(state management, notifications, high-availability & scale-out)SB Core APIMultiple device Plugins#ONOSProjectMultiple device PluginsMultiple device PluginsMultiple device Plugins17

ONOS InterfacesGUIREST APIONOS applicationsONOS distributed applications platformCommand LineONOS networking coreOSGI / Apache Karaf#ONOSProject18

Distributed CoreAppsAppsNB CoreCore APINBAPIDistributed & scale-out)(state management, notifications, high-availabilityhigh-availability& scale-out)Multiple devicePlugins#ONOSProjectSB CoreCore APISBAPIMultiple deviceMultiple devicePluginsPluginsMultiple devicePlugins19

ONOS Distributed Architecture Distributed Set up as a cluster of instances Symmetric Each instance runs identical software andconfiguration Fault-tolerant Cluster remains operational in the face ofnode failures Location Transparent A client can interact with anyinstance. The cluster presents the abstraction of a singlelogical instance Dynamic The cluster can be scaled up/down to meetusage demands Raft consensus Replicated State Machine#ONOSProject20

ONOS ClusterONOS 1#ONOSProjectONOS 2ONOS 321

ONOS ClusterONOS 1Master#ONOSProjectONOS 2ONOS 3Standby22

ONOS ClusterONOS 1#ONOSProjectONOS 2ONOS 323

ONOS Distributed Primitives EventuallyConsistentMap K, V ConsistentMap K, V Distributed collection of unique elementsAtomicCounter Distributed FIFO queue with long poll supportDistributedSet E Distributed Locking primitiveDistributedQueue E Map abstraction with strong linearizable consistencyLeadershipService Map abstraction with eventual consistency guaranteeDistributed version of Java AtomicLongAtomicValue V #ONOSProjectDistributed version of Java AtomicReference24

State Management in ONOS Core platform featureApplications can focus on business logicONOS exposes a set of primitives to cater to different use casesPrimitives span the consistency continuumshare nothingweakstrong Eventually Consistent Reads are monotonically consistent Low overhead reads and writes 2-3 ms latency for reacting to network events#ONOSProject25

NorthboundAppsAppsNB CoreCore APINBAPIDistributed high-availability& scale-out)(state management, notifications, high-availability& scale-out)SB CoreCore APISBAPIMultiple devicePlugins#ONOSProjectMultiple devicePluginsMultiple devicePluginsMultiple devicePlugins26

Key Northbound Abstractions Network Graph Directed, cyclic graph comprising of infrastructure devices,infrastructure links and end-station hosts Flow Objective Device-centric abstraction for programming data-plane flowsin version and vendor-independent manner Intent Network-centric abstraction for programming data-plane intopology-independent manner#ONOSProject27

Intent Framework Provides interface that focuses on what should bedone rather than how it is specifically programmed network-centric programming abstraction Abstracts unnecessary network complexity fromapplications device-agnostic behavior Maintains requested semantics as network changes persistency High availability, scalability and high performance#ONOSProject28

Intent ExampleHost to Host Intent#ONOSProject29

Intent ExampleHost to Host Intentsubmit()Intent Service API#ONOSProject30

Intent ExampleHost to Host IntentCOMPILATIONPath Intent#ONOSProjectPath Intent31

Intent ExampleHost to Host IntentCOMPILATIONPath IntentPath IntentINSTALLATIONFlow Rule BatchFlow Rule BatchFlow Rule Batch#ONOSProjectFlow Rule Batch32

SouthboundAppsAppsNB CoreCore APINBAPIDistributed high-availability& scale-out)(state management, notifications, high-availability& scale-out)SB CoreCore APISBAPIMultiple devicePlugins#ONOSProjectMultiple devicePluginsMultiple devicePluginsMultiple devicePlugins33

Southbound overviewSouthbound protocols: OpenFlow 1.0-1.3OVSDBNETCONF YANGSNMPP4 bmv2BGP, ISIS, OSPFPCEPRESTLISP#ONOSProjectAppsNB Core APIONOS Distributed CoreSB Core APIProtocols and Drivers34

ONOS SB architecture outline driver name "default "manufacturer "ON.Lab"DriverhwVersion "0.0.1" swVersion "0.0.1" On-demand activation behaviour api InterfacePathimpl ImpementationPath / Define device’s capabilities /driver Encapsulate specific logic and codeGoals of ONOS southbound: Abstractions, modularity, interoperability Live use of new devices Customization without changing the core Hidden complexity to upper layers#ONOSProject35

ApplicationsAppsAppsNB CoreCore APINBAPIDistributed high-availability& scale-out)(state management, notifications, high-availability& scale-out)SB CoreCore APISBAPIMultiple devicePlugins#ONOSProjectMultiple devicePluginsMultiple devicePluginsMultiple devicePlugins36

Developing ONOS applicationsONOS applications: Interact with the northbound Java or REST interface Device and protocol agnostic Augment ONOS though modularity Provide GUI, REST, CLI and distributed stores. Shape the network. Easy to start with auto generated basic code via mavenarchetypes.#ONOSProject37

Example Applications SDN-IP Peering Abstracts the SDN network as a BGP Autonomous System Video Streaming / IpTV Establish multicast forwarding from a sender to set of receivers Virtual Network Gateway (vBNG) Provide connectivity between a private host and the Internet Bandwidth Calendaring Establish tunnels with bandwidth guarantees between two points at agiven time Multi-level (IP / Optical) Provisioning #ONOSProjectProvision optical paths/tunnels with constraints38

Demo#ONOSProject39

Deployments&Use Cases#ONOSProject40

Motivation and Goals#ONOSProject41

Global SDN Deployment Powered by ONOSQ3 2015Korea announces the firstONOS deploymentOFOpenFlowQ1-Q2 2015First ONOS DeploymentsSouth America, US, EUQ1 2016 – New connectionsMiami - KoreaMiami - TaiwanKorea - TaiwanQ4 2015 – New connectionsSidney – Seattle - MiamiSao Paolo – AmsterdamQ4 2015ONOS deployed in KoreaQ1 2016NCTU / Taiwandeploys ONOSOpenFlowQ4 2015First ONOSproduction deploymentin South AmericaOpenFlowQ3 2015ONOS Deployment in Australia#ONOSProject42

Enabling network innovation with new appsCastor Provides L2/L3 connectivity for Internet Exchange Points (SDXs). Developed and deployed in AARNET.SDX L2/L3 Provides L2/L3 connectivity for Internet Exchange Points (SDXs). Developed and deployed by GEANT.VPLS L2 broadcast overlay networks on demand. Ready to be deployed at AmLight.SDN-IP Transforms a SDN into a transit IP network. SDN AS uses BGP to communicate with neighbors. L3 connectivity without legacy routers. Deployed by AmLight, Internet2 (upgrading), KREONET, NCTU.#ONOSProject43