atrium - open networking foundation · 2017-07-21 · atrium open sdn distribution (v 2015/a) the...

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

Upload: others

Post on 02-Feb-2020

3 views

Category:

Documents


0 download

TRANSCRIPT

© Open Networking Foundation. All rights reserved.

ATRIUM OPEN SDN DISTRIBUTION (v 2015/A)The Open Networking Foundation was formed in 2011 to promote

HKVW[PVU�VM�VWLU�:VM[^HYL�+LÄULK�5L[^VYRPUN��(Z�[OL�PUK\Z[Y`�JVU[PU\LZ�[V�IL�[YHUZMVYTLK�I`�:+5�HUK�5L[^VYR�-\UJ[PVUZ�Virtualization, open source software has emerged as a vital element to

]HSPKH[L�\ZL�JHZLZ�HUK�PTWSLTLU[H[PVUZ��

(Z�H�YLZ\S[��U\TLYV\Z�:+5� �5-=�VWLU�ZV\YJL�WYVQLJ[Z�OH]L�WYVSPMLYH[LK��LHJO�N\PKLK�I`�P[Z�V^U�TLTILYZOPW��WYPVYP[PLZ��HUK�[PTL[HISL��>P[O�[OL�HKKLK�JOHSSLUNL�VM�PUOLYLU[S`�KP]LYZL�OHYK^HYL�WSH[MVYTZ��UL[^VYR�VWLYH[VYZ�HYL�JVTWLSSLK�[V�HKKYLZZ�[OL�PUJYLHZPUNS`�complex task of integration of their applications, controllers, and data

WSHULZ��VM[LU�^P[O�H�KPZ[PUJ[�Z[HJR�MVY�LHJO�\ZL�JHZL�

65-�([YP\T�YLWYLZLU[Z�H�ZL[�VM�VWLU�ZV\YJL��ZVM[^HYL�KPZ[YPI\[PVUZ�KLZPNULK�[V�LUHISL�6WLU�:+5�HWWSPJH[PVUZ��([YP\T�HPTZ�[V�ZPTWSPM`�HUK�HJJLSLYH[L�VWLU�:+5�HKVW[PVU�I`�THRPUN�P[�LHZ`�[V�I\PSK�HWWSPJH[PVUZ�PU�H�T\S[P�]LUKVY�LU]PYVUTLU[��:PT\S[HULV\ZS �̀�P[�ZLY]LZ�HZ�HU�PUK\Z[Y`�SL]LS�VWLU�[LZ[ILK�[V�PU]LZ[PNH[L�HUK�]HSPKH[L�:+5�JVUJLW[Z�� Figure 1��ILSV^��THWZ�([YP\T�PU[V�[OL�65-�:+5�HYJOP[LJ[\YL�

BENEFITS• 7YL�X\HSPÄLK�HUK�

PU[LNYH[LK�([YP\T�6WLU�SDN stacks accelerate

HUK�ZPTWSPM`�L]HS\H[PVU�MVY�:+5�(WWSPJH[PVUZ�V]LY�OpenFlow

• 7PWLSPUL�HIZ[YHJ[PVU�SH`LY�supports multiple SDN

Controller Frameworks

and OpenFlow switch

implementations

• Open Source reference

WSH[MVYT�VќLYZ�MLLKIHJR�mechanism for open

source components

adopted

-PN\YL��!�([YP\T�6WLU�:+5�+PZ[YPI\[PVU�THWWPUN�PU[V�65-�:+5�(YJOP[LJ[\YL

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

Proprietary

White Box

Proprietary

Load Bal

SNMP

Cavium

OF-DPA

OCP

Ryu

L3 CLOS

Cloudstack

Broadcom

P4

ToR

ONOS

Virtualization

Netconf

Barefoot

Open Flow

NIC

ODL

L7 apps

Openstack

Netronome

Open Flow

WAN

RouteFlow

Peering Router

CLI

CorsaSilicon

HAL

Hardware

Controller

Application

Orchestration

SDN  Provides  a  Lot  of  Choices  

This is very daunting for users

Proprietary

White Box

Proprietary

Load Bal

SNMP

Cavium

OF-DPA

OCP

Ryu

L3 CLOS

Cloudstack

Broadcom

P4

ToR

ONOS

Virtualization

Netconf

Barefoot

Open Flow

NIC

ODL

L7 apps

Openstack

Netronome

Open Flow

WAN

RouteFlow

Peering Router

CLI

Corsa

Anchor Stack Provides a Solution

Proprietary

White Box

Proprietary

L3 CLOS

SNMP

Cavium

OF-DPA

OCP

Ryu

Virtualization

Cloudstack

Broadcom

P4

ToR

ONOS

Peering Router

Netconf

Barefoot

Open Flow

NIC

ODL

L7 apps

Openstack

Netronome

Open Flow

WAN

RouteFlow

Peering Router

CLI

Corsa

Solu5on:  Ver5cally  Integrated  Stack    ==  SDN  Distribu5on  

Project  Atrium  Goals  1. Integra5on  

-­‐   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  

ONOS

What  is  Atrium  today?  

vlan  x  vlan  y  

vlan  z  E-­‐BGP  

E-­‐BGP  

BRCM  ASIC  

OF-­‐DPA  

Indigo  OF  Agent  

OF-­‐DPA    API  

OpenFlow  1.3  

OCP Software

- ONL ONIE

OCP Bare Metal Hardware

BRCM  SDK  API  

OCP:  Open  Compute  Project;  ONL:  Open  Network  Linux;  ONIE:  Open  Network  Install  Env;    BRCM:  Broadcom  Merchant  Silicon  ASICs;  OF-­‐DPA:  OpenFlow  Datapath  Abstrac5on  

OFDPA Driver

Peering Application

Quagga  BGP  

ONOS

What  is  Atrium  today?  

vlan  x  vlan  y  

vlan  z  E-­‐BGP  

E-­‐BGP  

Vendor Hardware

OpenFlow  1.3  

OF  Agent  

OFDPA Driver

Peering Application

Quagga  BGP  

ONF  Builds  7  Routers  

Atrium  Demo  @  Layer123  

Q1  

Hosts  (1.0.0.1)   Hosts  (2.0.0.1)  

NoviFlow  

Edge-­‐Core  

Corsa  

Q2  Pica8  

AS65200  Dpid  0xda7a  

AS65000  Dpid  ?   AS65002  

AS65100  

AS65001  

AS65300  Dpid  ?  

dpid  00002829cc000c80    

 

Port  eth3.200  ip  192.168.20.1/24  vlan  200  

Port  6  ip  192.168.10.101/24  vlan  100  

Port  3  ip  192.168.20.101/24  vlan  200  

Port  eth2.100  ip  192.168.10.1/24  vlan  100  

port  1  ip  192.168.50.101/24  vlan  500  

port  2  ip  192.168.30.1/24  Vlan  300  

Port  2  ip  192.168.30.101/24  vlan  300  

Port  10  ip  192.168.50.1/24  vlan  500  

Port  8  ip  192.168.90.1/24  Vlan  900  

Port  10  ip  192.168.90.101/24  Vlan  900  

Port  11  ip  192.168.70.101/24  Vlan  700  

Port  1  ip  192.168.70.1/24  Vlan  700  

A  Closer  Look  at  Interoperability  

Accton,  Quanta  (BRCM  ASIC)  

NoviFlow,  Netronome  (NPU/NFP)  

Corsa  (FPGA)  

Pica8  (BRCM  ASIC)  

Centec  (ASIC)  

A Closer Look At Interoperability

Broadcom

Chip SDK

OF - Agent

match action table 0

match action table 1

match action table 2

group table

NPU Vendor X

Chip SDK

OF - Agent

1. OF-DPA1.routing 2. switching

Different combinations of match action tables form different OpenFlow pipelines.

How do controllers manage these differences ?

Different  combina5ons  of    Match-­‐Ac5on  Tables  form  Different  OF  1.3  pipelines    

How  can  a  controller  manage  these  differences?  

How  can  an  applica5on  work  across  these  differences?  

Anchor Stack Introduces OpenFlow Drivers

Broadcom

Chip SDK

OF - Agent

NPU Vendor X

Chip SDK

OF - Agent

ONOSBGP - Routing

Pipeline Abstraction Layer

Vendor X Driver OF DPA Driver

Drivers use human intelligence to bridge the interoperability GAP.

They are specific to the following parameters:

1. Driver per pipeline ( HW-TTP concept) 2. Driver per application type ( SW-TTP concept) ( Routing, Switching, Overlays )

3. Driver sets per framework ( ODL, ONOS, RYU )

Enables

Portability of hardware across frameworks Portability of hardware across application types

Anchor Stack Introduces OpenFlow Drivers

Broadcom

Chip SDK

OF - Agent

NPU Vendor X

Chip SDK

OF - Agent

ONOSBGP - Routing

Pipeline Abstraction Layer

Vendor X Driver OF DPA Driver

Drivers use human intelligence to bridge the interoperability GAP.

They are specific to the following parameters:

1. Driver per pipeline ( HW-TTP concept) 2. Driver per application type ( SW-TTP concept) ( Routing, Switching, Overlays )

3. Driver sets per framework ( ODL, ONOS, RYU )

Enables

Portability of hardware across frameworks Portability of hardware across application types

SDN    Applica5on  

Flow  Objec5ves  

OFDPA  Driver  

Controller  

Switch  

OpenFlow  1.3   OpenFlow  1.3  

Write  the  app  once  without  pipeline  details  

adapt  to  specific  Pipeline  using    device  driver  

Accton,  Quanta  (BRCM  ASIC)  

NoviFlow,  Netronome  (NPU/NFP)  

Corsa  (FPGA)  

Pica8  (BRCM  ASIC)  

Centec  (ASIC)  

Anchor Stack Introduces OpenFlow Drivers

Broadcom

Chip SDK

OF - Agent

NPU Vendor X

Chip SDK

OF - Agent

ONOSBGP - Routing

Pipeline Abstraction Layer

Vendor X Driver OF DPA Driver

Drivers use human intelligence to bridge the interoperability GAP.

They are specific to the following parameters:

1. Driver per pipeline ( HW-TTP concept) 2. Driver per application type ( SW-TTP concept) ( Routing, Switching, Overlays )

3. Driver sets per framework ( ODL, ONOS, RYU )

Enables

Portability of hardware across frameworks Portability of hardware across application types

Anchor Stack Introduces OpenFlow Drivers

Broadcom

Chip SDK

OF - Agent

NPU Vendor X

Chip SDK

OF - Agent

ONOSBGP - Routing

Pipeline Abstraction Layer

Vendor X Driver OF DPA Driver

Drivers use human intelligence to bridge the interoperability GAP.

They are specific to the following parameters:

1. Driver per pipeline ( HW-TTP concept) 2. Driver per application type ( SW-TTP concept) ( Routing, Switching, Overlays )

3. Driver sets per framework ( ODL, ONOS, RYU )

Enables

Portability of hardware across frameworks Portability of hardware across application types

SohRouter  Driver  

Corsa  Driver  

Pica8  Driver  

Centec  Driver  

Solu5on:  Flow  Objec5ves  API  

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  

 Corsa  Driver  

               

 OF-­‐DPA  Driver  

               

T0  mac  

T2  port-­‐vlan  

T4/5   T6  ip  

T0  port  

T1  Port-­‐vlan  

T2  mac  

T4  ip  

Flow  Objec5ves  

Example:  Next  Objec5ve  

•  Next  è  next  hop  for  forwarding  •  Similar  to  OF  1.3  group,  but  …  

NEXT-­‐  HOP  

               

Corsa  Driver  

bkt  

Indirect  group  

               

NoviFlow  &  Pica8  Drivers  

à  Flow-­‐ac5ons    

               

bkt  

OF-­‐DPA  Driver  Group  chain  

Flow  Objec5ves  

!

Atrium  Pre-­‐release  Deployment  

Atrium  Post-­‐release  Operator  Engagements  White-Box Open-Source Router Trial phase 1 – Trial Lab (white-label box) <--> Trial AS6539 (white-label box)

Trial LAB ASN xxxx Bell Canada ASN 6539

Core dis

Core Core OSPF

+iBGP mesh Trial1

Network

core

Trial2

Network

dis

eBGP

ASXXXX – AS6539

iBGP

iBGP

(by link IP

address)

Trial Lab network setup is for demonstration only,

some details maybe simplified

Static

default route

RC

RC

RR

RR

Advertise

Trial1 Prefix exchange

Trial1 Network

Trial2 Network

prefixes

Accept

Trial2 Prefix

eBGP iBGP

Peer

(White-label router) Peer

(White-label router)

White-Box Open-Source Router Trial phase 1 – Trial Lab (white-label box) <--> Trial AS6539 (white-label box)

Trial LAB ASN xxxx Bell Canada ASN 6539

Core dis

Core Core OSPF

+iBGP mesh Trial1

Network

core

Trial2

Network

dis

eBGP

ASXXXX – AS6539

iBGP

iBGP

(by link IP

address)

Trial Lab network setup is for demonstration only,

some details maybe simplified

Static

default route

RC

RC

RR

RR

Advertise

Trial1 Prefix exchange

Trial1 Network

Trial2 Network

prefixes

Accept

Trial2 Prefix

eBGP iBGP

Peer

(White-label router) Peer

(White-label router)

Atrium  Post-­‐release  Operator  Engagements  

Outline  1.    Project  Atrium  today  

-­‐  Mo5va5on  -­‐  Atrium  release  15/A  

2.   Project  Atrium  next  -­‐  What  is  coming  in  the  next  release  15/B?  

3.   Project  Atrium  roadmap    -­‐        Tenta5ve:  projects  under  discussion      

hlps://groups.opensourcesdn.org/wg/Atrium/dashboard    

LEARN  MORE  &  JOIN  THE  COMMUNITY:  

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  

 

hlps://groups.opensourcesdn.org/wg/Atrium/dashboard    

LEARN  MORE  &  JOIN  THE  COMMUNITY:  

Open-­‐Source  Leaf-­‐Spine  Fabric  (L3  Clos)  Policy$Driven$Traffic$Engineering$

Learn more: https://wiki.onosproject.org/display/ONOS/Segment+Routing

SPRING-OPEN Segment Routing on Bare Metal Hardware

Internally  the  Fabric  uses  MPLS  Segment  Rou5ng    

Open-­‐Source  Leaf-­‐Spine  Fabric  (L3  Clos)  

Learn more: https://wiki.onosproject.org/display/ONOS/Segment+Routing

SPRING-OPEN Segment Routing on Bare Metal Hardware

Internally  the  Fabric  uses  MPLS  Segment  Rou5ng    

Outline  1.    Project  Atrium  today  

-­‐  Mo5va5on  -­‐  Atrium  release  15/A  

2.   Project  Atrium  next  -­‐  What  is  coming  in  the  next  release  15/B?  

3.   Project  Atrium  roadmap    -­‐        Tenta5ve:  projects  under  discussion      

hlps://groups.opensourcesdn.org/wg/Atrium/dashboard    

LEARN  MORE  &  JOIN  THE  COMMUNITY:  

L2  IXP  Fabric  

Route Server

1 MAC per port, 1 MAC per VLAN per port

No broadcast, multicast, STP, OSPF, etc.

Atrium  Router  Stack    +  

L3  Clos  Fabric    =  

Chassis  Routers  SDN  

Controller  

BGP   App  

Support  MEF  E-­‐Line  Services  

Cust.  A  

Cust.  B  

Cust.  A  

Cust.  B  

EPL/  EVPL  

Segment-­‐Routed  Pseudowires  

This  is  just  the  star5ng  point!  

ONOS  

BGP   IGP  

ONOS  

BGP   IGP  

ONOS  

BGP   IGP  

Global  Controller  

TE  

And  more  …  

•  Generic  L2  Enterprise  Network  •  Smart  Ci5es/  IoT  •  Packet-­‐Op5cal  

Summary  Integra5on,  Interoperability  &  Deployments  

-­‐  Atrium  1st  release  brings  together  ONOS,  Quagga,  OCP  components  (ONL,  ONIE)  and  OFDPA  with  white-­‐boxes  +  vendor  equipment  

-­‐  Open  SDN  Distribu5on  (2015/A  release:  June  30th)    -­‐  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

OpenFlow Provider (1.0, 13)

Netconf Provider

PCEP Provider

TL-1 Providers P

rovi

der

s C

ore

Ser

vice

s (d

istr

ibut

ed)

Appli

cati

ons

(dis

trib

uted

)

Host Provider

LLDP Provider

Topology Service

Link Service

Device Service

Host Service

Intent Service

Stats Service

Flow

Rule

S

ervi

ce

Gro

up

Ser

vice

Pac

ket

Ser

vice

Segment Routing SDN-IP BGP Router

Flow Objectives

Driver X Driver Y Driver Z

Optical

Mastership Service

I-BGP Speaker/RIB

I-BGP Speaker/RIB

Outline  1.    Project  Atrium  today  

-­‐  Mo5va5on  -­‐  Atrium  release  15/A  

2.   Project  Atrium  next  -­‐  What  is  coming  in  the  next  release  15/B?  

3.   Project  Atrium  roadmap    -­‐        Tenta5ve:  projects  under  discussion      

hlps://groups.opensourcesdn.org/wg/Atrium/dashboard    

LEARN  MORE  &  JOIN  THE  COMMUNITY: