Share
Embed
Transcript
50 slides
-
ONOS The Open Source SDN Network Opera3ng
System for Service Providers Prajakta Joshi ([email protected] ) Madan Jampani ([email protected]) May 7th, 2015 AT&T Talk -
Goals of this talk • Introduce you to
ONOS, its architecture, use cases, community • Highlight what differen3ates ONOS, why it is championed by service providers and rapidly gaining trac3on with the broader community • Get you intrigued enough that you want to get your hands on ONOS right aPer this talk! J (When that happens, you can download ONOS code at hSp://bit.ly/download-‐onos ) -
Agenda • ONOS, its architecture, use cases and community
Prajakta • Deep Dive 1: ONOS distributed core Madan • Deep Dive 2: ONOS performance Madan • Q&A -
Dec, 2014 Open Source Avocet Release 2+ Years
R&D Clean-‐slate Design Mar, 2015 Scalability Performance, HA Blackbird Release June 2015 SDN/NFV Solu3on POCs Cardinal Release ONOS Journey so far Well architected & modular Easy to use GUI Tutorial VM Videos: ONOS + Use Cases Central Office Re-architected as Datacenter • CO fabric control • Network Function as a Service • vCPE over vOLT Packet Optical Convergence SDN-IP Peering Performance leadership • 1M+ Flow Ops/sec • Scales with ONOS servers • Sub 100ms to react to network events • HA: non-stop operation with component failures -
Open Source ONOS Ecosystem ON.LAB SERVICE PROVIDER PARTNERS COLLABORATORS
VENDOR PARTNERS COMMUNITY -
ONOS Community: A Snapshot In ~4 months:
Unique ONOS user IP addresses: ~1900 IPv6, NETCONF, v6 tes3ng, ONOS OPNFV project and others already being driven by community around the globe. map.onosproject.org -
ONOS Architected for Service Providers • Scalability, High Availability
& Performance • Northbound & Southbound Abstrac3ons • Modularity -
NB – Application Intent Framework Southbound Core API Protocols Adapters
Apps Protocols Adapters Protocols Adapters Protocols Adapters ONOS Instance 1 ONOS Instance 2 ONOS Instance 3 ONOS Instance N Distributed Core (performance, scale-out, availability, state management, notifications) ONOS Distributed Architecture -
Scale-‐Out Design w/ Mul3ple ONOS Instances ONOS Apps Apps
Global Network View / State Global Network View / State Each instance is identical One can add and remove instances seamlessly Each instance is a master for a subset of switches It works like a single system for apps and network devices ONOS Instance 1 ONOS Instance 2 ONOS Instance 3 -
ONOS Architecture Tiers Northbound - Application Intent Framework (policy
enforcement, conflict resolution) OpenFlow NetConf . . . Apps Apps Distributed Core (scalability, availability, performance, persistence) Southbound (discover, observe, program, configure) Northbound Abstraction: - network graph - application intents Core: - distributed - protocol independent Southbound Abstraction: - generalized OpenFlow - pluggable & extensible -
ONOS Architecture Tiers Northbound - Application Intent Framework (policy
enforcement, conflict resolution) OpenFlow NetConf . . . Apps Apps Distributed Core (scalability, availability, performance, persistence) Southbound (discover, observe, program, configure) Northbound Abstraction: - network graph - application intents Core: - distributed - protocol independent Southbound Abstraction: - generalized OpenFlow - pluggable & extensible -
Distributed Core Southbound “Provision 10G path from
Datacenter 1 to Datacenter2 optimized for cost” Intents translated and Compiled into specific instructions for network devices. Applica3on Intent Framework: Abstrac3ons, APIs, Policy Enforcement, Conflict resolu3on Distributed Core Southbound Core API OpenFlow NETCONF Southbound Interface ONOS Applica3on Intent Framework I want to define “what” I need without worrying about “how”… -
Intent Example COMPILATION INSTALLATION Flow Rule Batch Flow Rule
Batch Flow Rule Batch Flow Rule Batch Path Intent Path Intent Host to Host Intent -
ONOS Architecture Tiers Northbound - Application Intent Framework (policy
enforcement, conflict resolution) OpenFlow NetConf . . . Apps Apps Distributed Core (scalability, availability, performance, persistence) Southbound (discover, observe, program, configure) Northbound Abstraction: - network graph - application intents Core: - distributed - protocol independent Southbound Abstraction: - generalized OpenFlow - pluggable & extensible -
Network State Topology Link Usage Flows Intents Flow Stats
Different types of network states have different characteristics Configuration Switch to Controller assignment -
State and Proper3es State Properties Network Topology Eventually consistent,
low latency access Flow Rules, Flow Stats Eventually consistent, shardable, soft state Switch - Controller mapping Distributed Locks Strongly consistent, slow changing Application Intents Eventually consistent, durable Immutable Resource Allocations Strongly consistent, durable Immutable -
Key to Performance/Scalability: Effec3ve Distributed State Management
172.16.0.0 172.16.0.0 172.16.0.0 172.16.0.0 Application Intents - immutable - durable & replicated Global Network View - eventually consistent - fully replicated Flow Table Entries - strongly consistent - partitioned Optimistic Replication - gossip based - anti-entropy Optimistic Replication - gossip based - anti-entropy - partial ordering Master/Backup Replication 172.16.0.0 172.16.0.0 172.16.0.0 172.16.0.0 172.16.0.0 172.16.0.0 172.16.0.0 172.16.0.0 Switch è Master Switch è Master Switch è Master Switch to Controller -‐ strongly consistent -‐ replicated for durability Consensus for strong consistency Switch è Master Switch è Master Switch è Master Resource Assignment -‐ strongly consistent -‐ par33oned for scale Consensus for strong consistency -
ONOS Architecture Tiers Northbound - Application Intent Framework (policy
enforcement, conflict resolution) OpenFlow NetConf . . . Apps Apps Distributed Core (scalability, availability, performance, persistence) Southbound (discover, observe, program, configure) Northbound Abstraction: - network graph - application intents Core: - distributed - protocol independent Southbound Abstraction: - generalized OpenFlow - pluggable & extensible OpenFlow - 2014 NetConf – May 2015 TL1 – June 2015 (Demos) PCEP – June 2015 (Demos) OVSDB – mid- 2015+ -
Manager Component ONOS Architecture -‐ Modularity Adapter Component Adapter
Component App Component Service AdminService Listener notify command command sync & persist add & remove query & command App Component Adapter Component Manager Component AdapterRegistry Adapter AdapterService Service AdminService Listener notify register & unregister command command sensing add & remove query & command Store Store Protocols sync & persist Adapter Component AdapterRegistry Adapter AdapterService register & unregister sensing Protocols -
ONOS Performance
Detailed explana3on and results @ hSp://onosproject.org/soPware/blackbird-‐whitepapers/ hSps://wiki.onosproject.org/display/ONOS11/Blackbird+Performance+Evalua3on -
ONOS/SDN Control Plane Performance Metrics • Device &
link sensing latency o A, B • Flow rule opera3ons throughput o C • Intent opera3ons throughput o D • Intent opera3ons latency o E -
ONOS Performance numbers: Best In Class • Device &
link sensing latency o Less than 100ms o ONOS processing less than 10ms • Flow rule opera3ons throughput o 500K to 3M ops/sec • Intent opera3ons throughput o 150k ops/sec • Intent opera3ons latency o Less than 50ms First gen results; Will get even beSer! Comprehensive stress tes3ng ahead… -
Core Packet-‐Op3cal Metro Packet-‐Op3cal Wired Access
Wireless Access Access Central Office Built like a Data Center Network Interface ! Network Interface ! Enterprise Access Wireless Access Wired Access Wireless Access Wired Access Wireless Access Enterprise Access Wireless Access Network Interface ! Network Interface ! Network Interface ! Network Interface ! POP Built like a Data Center Network Interface ! Network Interface ! Network Interface ! Network Interface ! Service Provider Network of the Future -
SDN Control Plane -‐ ONOS I O
I O Metro Core Link I O Access Link I O Commodity hardware Fabric Spine Switches Leaf Switches Central Office re-imagined as Datacenter NFV Orch Large number of COs Evolved over 40-50 years Huge source of CAPEX/OPEX Architect with commodity hardware and manage the fabric/ infrastructure with ONOS (SDN Control plane) -
White Box White Box White Box White
Box White Box White Box White Box White Box White Box White Box White Box White Box White Box White Box ONOS Leaf-Spine L3 Fabric White Box White Box Central Office fabric control with ONOS Elephant flow rerouting Traffic Steering Network Virtualization L3 Clos Fabric Control (Segment Rou3ng) -
VM VM VM VM VM VM VM VM VM VM
VM Service 1 Service2 VM VM VM VM VM VM VM VM VM VM VM VM VM VM Service 3 Service2 Service 1 NFaas: From VMs to Services VNF VMs Service Abstraction Service Composition -
Commodity servers + NFaaS = CAPEX and OPEX savings
Centralized Control & Management Plane – ONOS + OVX + XOS PGW XCODE NLA CDN BNG CDN CG-‐NAT Firewall VPN WanEx DSA IDS Mobile Customers Residential Customers Enterprise Customers I O Access Link Central Office with NFaaS (NFV) -
Traditional GPON- let’s also virtualize OLT and CPE OLT 10
GigE (LAG) 2.5 Gb/s 1.25 Gb/s Eth Agg CPE PC Phone ONT FTTP CPE PC Phone ONT PON Splitter . . . STB w DVR Broadband Network Gateway GPON Optical Line Terminator (OLT) Source Tom Anschutz © 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. -
Standard HV " Router " Standard HV
" Server " SW BRAS " Standard HV " PON MAC Card " PON " OLT " MACs Standard HV " Switch " Standard HV " Switch " Standard HV Server " Standard HV Server Standard HV PON MAC Card " PON " OLT " MACs PON MACs is moving to standalone HW Spine & Leaf switches " GPON OLT Everything but the MACs can be virtualized and moved to NFVI running over standard: • Fabric Switches • Storage • Servers NFV OLT Standard" Equipment Source – Tom Anschutz © 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Virtualizing the OLT (vOLT) -
I O I O Metro Core Link I
O Access Link Commodity hardware Fabric Spine Switches Leaf Switches Control Apps Mgmt Apps | Config Apps | vBNG vCPE PON OLT MACs vOLT XOS + OVX Subscriber 1 Whitebox Switch ONU Replace complex residen3al gateway with commodity switch 20K-100K subscribers " ONU Whitebox Switch SDN Control Plane -‐ ONOS Subscriber 2 Central Office DHCP LDAP RADIUS Control Data Central Office Re-architected as Datacenter -
Datacenter 1 Packet Network Op3cal Network ONOS
(Multi-layer SDN Control) Datacenter 2 Failure handling – move traffic to different path “Provision 10G path from Datacenter 1 to Datacenter 2 optimized for latency” Lower CAPEX, OPEX, better utilization Bandwidth on Demand Bandwidth Calendaring Pay per network feature, QOS Multilayer Packet/optical SDN control Multi-layer SDN control -
MPLS/optical SDN control with Cap-Grow-Drain Cap Grow Drain
ONOS ONOS ONOS MPLS Network MPLS Network MPLS Network Op3cal Network Op3cal Network Op3cal Network Segment Rou3ng (for MPLS network) Op3cal control Segment Rou3ng (for MPLS network) Op3cal control Segment Rou3ng (for MPLS network) Op3cal control Whitebox switches Whitebox switches Whitebox switches Whitebox switches Whitebox switches New SDN Edge Send Big Flows to op3cal network Cap-‐Grow-‐Drain = Bring SDN to backbone without fork liP upgrade Whitebox switches -
... ONOS Cluster • BGP speaker HA • ONOS/SDN-IP HA
• External BGP router/ connection HA • external networks across SDN island SDN-IP enables communication between: • SDN network and external IP networks ONOS ONOS ONOS SDN-‐IP SDN-‐IP SDN-‐IP Seamless peering with SDN-IP -
Other POCs/Use Cases • NTT/NEC: Mul3-‐domain, Mul3-‐vendor, Mul3-‐Layer
Packet Op3cal • SK Telecom POC-‐ cloud • China Unicom POC • DirecTV: SDN-‐based Mul3cast distribu3on of video • Segment Rou3ng • ONF Anchor Stack • IP RAN…. -
ONOS Deployment (R&E) Around the Globe • I2 (US)
– deployed and connected several universi3es • Peering between ESnet (US) – AARNet (Australia) deployed • AARNet (Australia) likely to deploy in a na3on-‐wide network • DREAMER (Europe) • KREONET/KISTI (Korea) • Peering between FIU – Chile/Brazil – deployed ONOS star3ng to have a global footprint in R&E networks -
ONOS-‐based peering router in Australia and Google’s Vandervecken
SDN controller stack in California successfully exchanging 15,000 routes on trans-‐Pacific link ONOS deployment in Australia hSp://prn.to/1EQ2JQM -
Dec, 2014 Open Source Avocet Release 2+ Years
R&D Clean-‐slate Design Mar, 2015 June 2015 Dec, 2015 ONOS Journey ahead Clean Slate Design è Service Provider Deployment Well architected & modular Easy to use GUI Tutorial VM Videos: ONOS + Use Cases -
Dec, 2014 Open Source Avocet Release 2+ Years
R&D Clean-‐slate Design Mar, 2015 Scalability Performance, HA Blackbird Release June 2015 Dec, 2015 ONOS Journey ahead Clean Slate Design è Service Provider Deployment Best in class results • 1M+ Flow Ops/sec • Scales with ONOS servers • Sub 100ms to react to network events • HA: non-stop operation with component failures -
Dec, 2014 Open Source Avocet Release 2+ Years
R&D Clean-‐slate Design Mar, 2015 Scalability Performance, HA Blackbird Release June 2015 SDN/NFV Solu3on POCs Cardinal Release Dec, 2015 ONOS Journey ahead Clean Slate Design è Service Provider Deployment Central Office Re-architected as Datacenter • CO fabric control • Network Function as a Service • vCPE over vOLT Packet Optical Convergence SDN-IP Peering -
Dec, 2014 Open Source Avocet Release 2+ Years
R&D Clean-‐slate Design Mar, 2015 Scalability Performance, HA Blackbird Release June 2015 SDN/NFV Solu3on POCs Cardinal Release Dec, 2015 ONOS Service Provider partners: Lab Trials and Deployments ONOS Journey ahead Clean Slate Design è Service Provider Deployment -
SoPware Defined Transforma3on of Service Provider Networks Join the
journey @ onosproject.org -
ONOS Resources ¡ Website: onosproject.org ¡ Wiki: wiki.onosproject.org
¡ Mailing lists: hSp://onosproject.org/community/mailing-‐lists/ ¡ Blackbird Performance whitepapers, test methodology, evalua3on: hSp://onosproject.org/soPware/blackbird-‐whitepapers/ ¡ Use cases and solu3ons: hSps://wiki.onosproject.org/display/ONOS/ONOS+Use+Cases ¡ ONOS code download: hSps://wiki.onosproject.org/display/ONOS/Downloads ¡ ONOS Youtube channel: hSp://bit.ly/onosyoutube ¡ Slides hSp://bit.ly/onos-‐slides Much more on the wiki and website…