ATRIUM Open SDN Distribu5on

ATRIUM Open SDN Distribu5on Saurav Das Principal System Architect, ONF With contributions from ONF Atrium Management team and many others

SDN Provides a Lot of Choices Orchestration SNMP Netconf Cloudstack Openstack CLI Application Load Bal Virtualization L3 CLOS L7 apps Peering Router Controller Proprietary ONOS Ryu ODL RouteFlow Hardware White Box ToR OCP NIC WAN HAL Proprietary P4 OF-DPA Open Flow Open Flow Silicon Cavium Barefoot Broadcom Netronome Corsa

Solu5on: Ver5cally Integrated Stack == SDN Distribu5on SNMP Netconf Cloudstack Openstack CLI L3 CLOS Peering Router Virtualization L7 apps Peering Router Proprietary ONOS Ryu ODL RouteFlow White Box ToR OCP NIC WAN Proprietary P4 OF-DPA Open Flow Open Flow Cavium Barefoot Broadcom Netronome Corsa

1. Integra5on - - - Project Atrium Goals Create ver5cally- integrated open- source stacks From open- source components, OF1.3 & Hardware Enable network operators to download distribu5on from a single loca5on 2. Interoperability - - Enable mul5ple hardware vendors to plugin to stack Allows end- users to select different hardware classes for common use- cases. 3. Deployments - Work hand- in- hand with operators on deployable use cases leading to trials. - Give operators confidence in pure SDN solu5ons

OCP: Open Compute Project; ONL: Open Network Linux; ONIE: Open Network Install Env; BRCM: Broadcom Merchant Silicon ASICs; OF- DPA: OpenFlow Datapath Abstrac5on What is Atrium today? Quagga BGP vlan x vlan y Peering Application E- BGP vlan z E- BGP ONOS OFDPA Driver OpenFlow 1.3 OCP Software - ONL ONIE Indigo OF Agent OF- DPA API OF- DPA BRCM SDK API BRCM ASIC OCP Bare Metal Hardware

What is Atrium today? Quagga BGP vlan x vlan y Peering Application E- BGP vlan z E- BGP ONOS OFDPA Driver OpenFlow 1.3 OF Agent Vendor Hardware

ONF Builds 7 Routers

Hosts (1.0.0.1) Port 8 ip 192.168.90.1/24 Vlan 900 AS65001 Q1 Port eth2.100 ip 192.168.10.1/24 vlan 100 Port 6 ip 192.168.10.101/24 vlan 100 Atrium Demo @ Layer123 Port 10 ip 192.168.90.101/24 Vlan 900 AS65000 Dpid? NoviFlow Port 10 ip 192.168.50.1/24 vlan 500 AS65200 Dpid 0xda7a Edge- Core AS65100 dpid 00002829cc000c80 Corsa Port 11 ip 192.168.70.101/24 Vlan 700 Port 1 ip 192.168.70.1/24 Vlan 700 AS65300 Dpid? Pica8 Port 2 ip 192.168.30.101/24 vlan 300 Port eth3.200 ip 192.168.20.1/24 vlan 200 AS65002 Q2 Port 3 ip 192.168.20.101/24 vlan 200 Hosts (2.0.0.1) port 1 ip 192.168.50.101/24 vlan 500 port 2 ip 192.168.30.1/24 Vlan 300

A Closer Look at Interoperability Different combina5ons of Match- Ac5on Tables form Different OF 1.3 pipelines match action table 0 match action table 1 match action table 2 group table How can a controller manage these differences? How can an applica5on work across these differences? Accton, Quanta (BRCM ASIC) NoviFlow, Netronome (NPU/NFP) Corsa (FPGA) Pica8 (BRCM ASIC) Centec (ASIC)

Solu5on: Flow Objec5ves API Write the app once without pipeline details SDN Applica5on Controller OFDPA Driver SohRouter Driver Flow Objec5ves Corsa Driver Pica8 Driver Centec Driver adapt to specific Pipeline using device driver OpenFlow 1.3 OpenFlow 1.3 Switch Accton, Quanta (BRCM ASIC) NoviFlow, Netronome (NPU/NFP) Corsa (FPGA) Pica8 (BRCM ASIC) Centec (ASIC)

Example: Filtering Objec5ve Filter è only Permit or Deny op5ons On match fields of packet header Router port: X Permit: MAC 1, VLAN 1, IP 1, 2, 3 Permit: MAC 1, VLAN 2, IP 4, 5 Flow Objec5ves Corsa Driver OF- DPA Driver T0 mac T2 port- vlan T4/5 T6 ip T0 port T1 Port- vlan T2 mac T4 ip

Example: Next Objec5ve Next è next hop for forwarding Similar to OF 1.3 group, but bkt Corsa Driver NEXT- HOP Flow Objec5ves Indirect group bkt Group chain OF- DPA Driver à Flow- ac5ons NoviFlow & Pica8 Drivers

Atrium Pre- release Deployment

Atrium Post- release Operator Engagements phase 1 Trial Lab (white-label box) <--> Trial AS6539 (white-label box) Trial LAB ASN xxxx Bell Canada ASN 6539 ebgp exchange Trial1 Network Trial2 Network prefixes ibgp Advertise Trial1 Prefix Accept Trial2 Prefix Trial2 Network dis core Peer (White-label router) ebgp ASXXXX AS6539 RC ibgp Peer RC (White-label router) ibgp Static (by link IP default route address) RR Core RR Core Core OSPF +ibgp mesh dis Trial1 Network Trial Lab network setup is for demonstration only, some details maybe simplified

Atrium Post- release Operator Engagements

1. Project Atrium today - Mo5va5on - Atrium release 15/A Outline 2. Project Atrium next - What is coming in the next release 15/B? 3. Project Atrium roadmap - Tenta5ve: projects under discussion LEARN MORE & JOIN THE COMMUNITY: hlps://groups.opensourcesdn.org/wg/atrium/dashboard

What s Coming in the 15/B Release? 1. Con5nued Improvements on the 15/A release (ONOS based) - Hardening & Stability - Performance - Missing features: untagged, run5me- config, sta5c- routes - Hardware Automated Test Infrastructure 2. Atrium Router on OpenDaylight - Por5ng from ONOS to ODL - ODL will also use FlowObjec5ves and device drivers - Community con5bu5ons: Wipro & Criterion LEARN MORE & JOIN THE COMMUNITY: hlps://groups.opensourcesdn.org/wg/atrium/dashboard

Open- Source Leaf- Spine Fabric (L3 Clos) Internally the Fabric uses MPLS Segment Rou5ng

Open- Source Leaf- Spine Fabric (L3 Clos) Internally the Fabric uses MPLS Segment Rou5ng SPRING-OPEN Segment Routing on Bare Metal Hardware Learn more:

L2 IXP Fabric No broadcast, multicast, STP, OSPF, etc. Route Server 1 MAC per port, 1 MAC per VLAN per port

Atrium Router Stack + L3 Clos Fabric = Chassis Routers BGP App SDN Controller

Support MEF E- Line Services Cust. A Cust. A Cust. B EPL/ EVPL Segment- Routed Pseudowires Cust. B

This is just the star5ng point! TE Global Controller BGP ONOS IGP BGP ONOS IGP BGP ONOS IGP

And more Generic L2 Enterprise Network Smart Ci5es/ IoT Packet- Op5cal

Summary Integra5on, Interoperability & Deployments - Atrium 1 st release brings together ONOS, Quagga, OCP components (ONL, ONIE) and OFDPA with white- boxes + vendor equipment - Open SDN Distribu5on (2015/A release: June 30 th ) - ONF builds 7 routers! - Key architectural contribu5on: Flow Objec5ves & Device Drivers - Pre release deployment in Sydney. - More coming as we engage operators Atrium 15/B release - - - Improved 15/A router built around ONOS ODL based Atrium router Atrium leaf- spine L3 Clos fabric Many more projects in the horizon

ONOS Architecture Applications (distributed) Segment Routing Flow Objectives I-BGP Speaker/RIB BGP Router Optical I-BGP Speaker/RIB SDN-IP Core Services (distributed) Driver X Driver Y Driver Z Flow Rule Service Group Service Packet Service Device Service Mastership Service Link Service Topology Service Host Service Stats Service Intent Service Providers Netconf Provider PCEP Provider Host Provider LLDP Provider OpenFlow Provider (1.0, 13) TL-1 Providers