$30 off During Our Annual Pro Sale. View Details »

The Mission of Open Networking

Phil Huang
October 16, 2017

The Mission of Open Networking

#edgecore #onf #opnenetworking

Phil Huang

October 16, 2017
Tweet

More Decks by Phil Huang

Other Decks in Technology

Transcript

  1. The Mission of Open Networking Foundation
    Phil Huang 黃秉鈞
    ONF Ambassador Steering Team / [email protected]
    Edgecore Networks Solution Engineer / [email protected]
    Tunghai Uuniversity, Taichung, Taiwan, Oct. 16, 2017

    View Slide

  2. 2
    黃秉鈞 Phil Huang
    • ONF 全球大使七人指導小組
    • Edgecore 解決方案工程師
    • SDNDS-TW 社群共同創辦人
    Ref: https://www.linkedin.com/in/phil-huang-09b09895/
    ONF: Open Networking Foundation

    View Slide

  3. 3
    Ref: https://ambassadors.opennetworking.org/about/

    View Slide

  4. 4

    View Slide

  5. 5

    View Slide

  6. 6
    Ref: https://ambassadors.opennetworking.org/

    View Slide

  7. 7

    View Slide

  8. 8

    View Slide

  9. Partner
    The Ecosystem – 200+ Members Strong
    Vibrant Operator Led Consortium Positioned for Success
    Innovator 110+
    Volunteer
    Volunteers
    Collaborator
    Operators (7) Vendors (10)
    70+
    100s
    ONF (& Stanford) Guru Parulkar
    Network Operators
    AT&T Andre Fuetsch – CTO
    Google Urs Hölzle – SVP
    NTT Comm Dai Kashiwa – Director
    Comcast Rob Howald– VP
    Verizon Srini Kalapala – VP
    China Unicom Shao Guanglu - SVP
    Research & Vendor Community
    Nick McKeown Stanford
    Fabian Schneider NEC
    New ONF Board
    Including 14 Operators:
    Argela/Turk Telecom Microsoft
    China Mobile Swisscom
    SK Telecom Telecom Italia
    ECI Telecom Telefonica
    Facebook TELUS
    Globe Telecom Vodafone
    Goldman Sachs Yahoo

    View Slide

  10. ONF’s Scope
    Control
    (OpenFlow, P4)
    Config
    (NetConf/Yang, OpenConfig)
    Disaggregated boxes:
    Packet switch, ROADM, eNodeB, OLT, RAN …
    Open Source:
    Switch OS, FBOSS,
    SONIC, ONL, ONIE
    Open Source:
    ONAP, Open-O,
    Open Source MANO
    Service APIs: TOSCA, RESTful
    Control
    Plane
    Network Intent-Based APIs
    Programmable
    Forwarding
    Plane
    Solutions
    Platforms
    M-
    CORD
    R-CORD E-CORD
    CORD
    VNFs Standards
    &
    Interworking
    APIs
    Global
    Orchestrators
    10
    New ONF
    Scope of Focus
    ONOS
    Alternative Controllers
    (e.g. ODL)
    Alternative
    VNF Frameworks
    (e.g. OPNFV)

    View Slide

  11. 11

    View Slide

  12. ONOS
    Carrier-grade Open Networking Operating System
    12

    View Slide

  13. What is ONOS?
    13
    Open Network Operating System (ONOS) is an open source
    SDN network operating system. Our mission is to enable
    Service Providers to build real SDN/NFV Solutions.
    Quarterly Releases, 1.11.0 - released 2017-08

    View Slide

  14. Service Provider Networks
    ● WAN core backbone
    o Multi-Protocol Label Switching (MPLS) with Traffic Engineering (TE)
    o 200-500 routers, 5-10K ports
    ● Metro Networks
    o Metro cores for access networks
    o 10-50K routers, 2-3M ports
    ● Cellular Access Networks
    o LTE for a metro area
    o 20-100K devices, 100K-100M ports
    ● Wired access / aggregation
    o Access network for homes; DSL/Cable
    o 10-50K devices, 100K-1M ports

    View Slide

  15. Control & Data Plane Disaggregation
    15
    Ref: https://www.opennetworking.org/images/stories/downloads/sdn-resources/white-papers/wp-sdn-newnorm.pdf

    View Slide

  16. BGP BMv2 ISIS Lisp Netconf OpenFlow OSPF OVSDB PCEP REST SNMP TL1
    ONF ONOS
    16

    View Slide

  17. Key Performance Requirements
    ONOS
    Apps
    Apps
    Global Network View / State
    Global Network View / State
    high throughput | low latency | consistency | high availability
    High Throughput:
    ~500K-1M paths
    setups / second
    ~3-6M network
    state ops / second
    High Volume:
    ~500GB-1TB of
    network state data
    Difficult challenge!

    View Slide

  18. Architectural Tenets
    • High-availability, scalability and performance
    • Strong abstractions and simplicity to develops apps and
    solutions
    • Protocol and device behaviour independence
    • Separation of concerns and modularity

    View Slide

  19. Distributed Core

    View Slide

  20. Control & Data Plane Disaggregation
    20
    Ref: https://www.opennetworking.org/images/stories/downloads/sdn-resources/white-papers/wp-sdn-newnorm.pdf

    View Slide

  21. OSGI / Apache Karaf
    ONOS distributed applications platform
    ONOS networking core
    ONOS applications
    GUI REST API
    Command Line

    View Slide

  22. Manager
    Component
    Manager
    Component
    ONOS Core Subsystem Structure
    Provider
    Component
    Provider
    Component
    App
    Component
    Listener
    notify
    command
    command
    sync & persist
    add & remove
    query &
    command
    App
    Component
    Provider
    Component
    Manager
    Component
    Manager
    Component
    ProviderRegistry
    Provider
    ProviderService
    Service
    AdminService
    Listener
    notify
    register & unregister
    command
    command
    sensing
    add & remove
    query &
    command
    Protocols
    Store Store
    Provider
    Component
    ProviderRegistry
    Provider
    ProviderService
    register & unregister
    sensing
    Protocols
    Service
    AdminService
    Store Store
    sync & persist
    ProviderRegistry ProviderRegistry
    Provider
    Provider
    ProviderService
    ProviderService
    AdminService AdminService
    Service Service
    Listener
    Listener

    View Slide

  23. View Slide

  24. View Slide

  25. tcp:9876

    View Slide

  26. ONOS 1 ONOS 2 ONOS 3
    ONOS Cluster

    View Slide

  27. Closer look...

    View Slide

  28. View Slide

  29. View Slide

  30. View Slide

  31. View Slide

  32. View Slide

  33. Distributed
    Topology
    Store
    Read
    Topology
    State
    Topology State

    View Slide

  34. Topology as a State Machine
    Events are {Switch, Port, Link} {up, down}
    Current
    Topology
    Updated
    Topology
    apply event

    View Slide

  35. ONOS 1 ONOS 2 ONOS 3
    ONOS Cluster
    35

    View Slide

  36. Topology Sharing
    as fast as possible
    as accurate as possible

    View Slide

  37. Northbound
    37

    View Slide

  38. Control & Data Plane Disaggregation
    38
    Ref: https://www.opennetworking.org/images/stories/downloads/sdn-resources/white-papers/wp-sdn-newnorm.pdf

    View Slide

  39. OSGI / Apache Karaf
    ONOS distributed applications platform
    ONOS networking core
    ONOS applications
    GUI REST API
    Command Line

    View Slide

  40. OSGI / Apache Karaf
    ONOS distributed applications platform
    ONOS networking core
    ONOS applications
    GUI REST API
    Command Line

    View Slide

  41. Interact with ONOS: GUI
    UI: :8181/onos/ui

    View Slide

  42. Interact with ONOS: CLI
    $onos

    View Slide

  43. Interact with ONOS: REST and GRPC
    REST APIs: :8181/onos/v1/docs/
    Northbound GRPC with protocol buffers (.proto)
    for ONOS network model

    View Slide

  44. Interact with ONOS
    gRPC:
    - Google remote procedure call
    - Based on protobuf
    - Faster than REST
    - Off-Platform applications
    RESTCONF
    - Rest interface for the XML-based rpc and streaming
    operations

    View Slide

  45. Sounthbound
    45

    View Slide

  46. Control & Data Plane Disaggregation
    46
    Ref: https://www.opennetworking.org/images/stories/downloads/sdn-resources/white-papers/wp-sdn-newnorm.pdf

    View Slide

  47. OSGI / Apache Karaf
    ONOS distributed applications platform
    ONOS networking core
    ONOS extensions
    GUI REST API
    Command Line
    applications
    drivers
    protocols

    View Slide

  48. Southbound Architecture
    • Southbound abstractions, modularity
    • customization without changing the core
    • Protocol and device model independency
    • avoid specifics and dependencies in the core
    • hidden complexity to upper layers
    • testability, extensibility and performance
    ONOS Distributed
    Core
    SB Core API
    NB Core API
    Apps
    Protocols and Drivers

    View Slide

  49. Southbound overview
    Southbound protocols in 1.11.0:
    • OpenFlow until 1.3 + optical extension → 1.5 is in the works.
    • OVSDB
    • NETCONF + YANG →Yang tools and Yang management system
    • SNMP
    • P4 → thrift api for bmv2 softswitch from barefoot networks.
    • BGP, ISIS, OSPF → interoperability with legacy network.
    • PCEP → Path computation element protocol (IETF)
    • REST and RESTCONF
    • LISP
    • TL1
    • gRPC

    View Slide

  50. ONOS Deployments
    50

    View Slide

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

    View Slide

  52. OpenFlow
    OpenFlow
    OF
    Q3 2015
    ONOS Deployment in Australia
    OpenFlow
    Q3 2015
    Korea announces the first
    ONOS deployment
    Q4 2015
    ONOS deployed in Korea
    Q4 2015
    First ONOS
    production deployment
    in South America
    Q1-Q2 2015
    First ONOS Deployments
    South America, US, EU
    Q4 2015 – New connections
    Sidney – Seattle - Miami
    Sao Paolo – Amsterdam
    Q1 2016
    NCTU / Taiwan
    deploys ONOS
    Q1 2016 – New connections
    Miami - Korea
    Miami - Taiwan
    Korea - Taiwan
    Global SDN Deployment Powered by ONOS

    View Slide

  53. OpenFlow
    OpenFlow
    OF
    OpenFlow
    How the testbed works
    eBGP
    AS
    #20080 AS
    #65111
    over L2 dedicated circuits

    View Slide

  54. CORD
    Central Office Re-architected as a Data-center
    54

    View Slide

  55. Have you ever wondered how you can access
    the Internet?

    View Slide

  56. Magic ?

    View Slide

  57. Service providers

    View Slide

  58. Introduction to
    Service Provider
    Network
    COR
    D
    + +
    R-
    CORD

    View Slide

  59. What does a typical service provider network
    look like?

    View Slide

  60. Telco Central Office (CO)
    Mobile
    Residential
    Enterprise
    Central Office
    Can be small or large
    and has different names
    in different contexts
    60
    • CO is a service provider’s gateway to
    its customers
    • There are 1000+ of COs
    • Per CO may support
    § 10K+ residential subscribers
    § 10K+ mobile subscribers
    § 1K+ enterprise customers
    • CO providers a great vantage point
    for service providers

    View Slide

  61. Terminal
    CPE
    Edge Central O!ces Regional Data Centers National Data Centers
    Our Customers have Spoken:
    Need Global (Virtualized) Service Delivery Infrastructure
    CO
    CO
    CO
    CO
    WAN
    Residential /
    Personal
    Access Metro Core
    Regional
    Regional
    Regional
    Regional
    National
    National
    National
    CO
    CORD
    POD
    CORD
    POD
    VNF
    POD
    CORD
    POD
    CORD
    POD
    VNF
    POD
    CORD
    POD
    CORD
    POD
    VNF
    POD
    CORD
    POD
    µPOD
    CPE VNF
    POD
    NFV
    deployment
    PODs
    network-wide
    SDN
    network-wide

    View Slide

  62. https://huroniamuseumblog.files.wordpress.com/2016/07/2006-0020-2495.jpg

    View Slide

  63. You can still find those wires nowadays…

    View Slide

  64. Residential Network
    64
    PC CPE ONU OLT BNG Internet
    Home Roadside CO

    View Slide

  65. Mobile Network
    65
    Phone eNB BBU SGW BGW Internet
    User Field CO

    View Slide

  66. Enterprise Network
    66
    PC CPE EE TE ROADM
    Office CO
    ROADM
    CO
    Metro
    Net

    Internet

    View Slide

  67. Challenges
    • Source of high CAPEX and OPEX
    • Lack of programmability inhibits innovation
    • Limits ability to create new services and revenue
    ØHard to create innovative services
    67

    View Slide

  68. Knock knock. It’s CORD.

    View Slide

  69. What is CORD?
    69
    Central Office Re-architected as a Datacenter
    SDN + NFV + Cloud
    Open Source Software
    Commodity Hardware
    (Servers, White-Box Switches, I/O Blades)
    Large
    number of
    COs
    Evolved over
    40-50 years
    300+ Types
    of
    equipment
    Huge source
    of
    CAPEX/OPEX

    View Slide

  70. CORD Aims to Deliver
    70
    Agility of a cloud provider
    Software platforms that enable rapid creation of new services
    Economies of a datacenter
    Infrastructure built with a few commodity building blocks using
    open source software and white-box switches

    View Slide

  71. Design Philosophy -> Tangible Value
    71
    SDN NFV
    Cloud
    Extends the agility of micro-services to the access network
    Supports legacy VNFs and
    pushes the limits of disaggregation
    Interconnects VNFs and is
    a source of innovative services
    XaaS

    View Slide

  72. Service Provider Driven
    72

    View Slide

  73. Leaf-Spine Fabric
    ONOS Controller Cluster
    Underlay
    Control
    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
    Open Source
    SDN-based
    Bare-metal
    White Box
    White Box
    Why Leaf-Spine fabric?

    View Slide

  74. Traditional Service Provider Network
    74
    Aggregation
    Switch

    OLT

    ONU
    ONU
    Splitter
    Splitter

    BNG
    Switch
    Internet
    Reliability ☹
    Scalability ☹
    Flexibility ☹
    Cost

    View Slide

  75. Data Center Leaf-Spine Fabric
    75
    Reliability
    Scalability
    Flexibility
    Latency Cost
    Bandwidth
    Spine
    Leaf

    View Slide

  76. Underlay Fabric - Open Hardware & Software Stacks
    White Box SDN Switch
    Accton 6712
    Spine Switch
    32 x 40G ports downlink to leaf switches
    40G QSFP+/DAC
    GE
    mgmt.
    White Box SDN Switch
    Accton 6712
    Leaf Switch
    24 x 40G ports downlink to servers
    and OLTs
    8 x 40G ports uplink to different spine switches
    ECMP across all uplink ports
    GE
    mgmt.
    BRCM ASIC
    OF-DPA
    Indigo OF Agent
    OF-DPA API
    OpenFlow 1.3
    OCP: Open Compute Project
    ONL: Open Network Linux
    ONIE: Open Network Install Environment
    BRCM: Broadcom Merchant Silicon ASICs
    OF-DPA: OpenFlow Datapath Abstraction
    Leaf/Spine Switch Software Stack
    OCP
    Software
    -
    ONL
    ONIE
    OCP Bare Metal Hardware
    BRCM SDK API
    ONOS

    View Slide

  77. White Box
    Access Devices
    ONOS Controller Cluster
    Underlay
    Control
    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
    Open Source
    SDN-based
    Bare-metal
    White Box
    White Box
    R,E,M-
    Access
    vOLT
    Control
    E.g. AT&T Open GPON 48-port,
    1RU

    View Slide

  78. Metro Routers & vRouter
    ONOS Controller Cluster
    vRouter
    Control
    Underlay
    Control
    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
    Open Source
    SDN-based
    Bare-metal
    White Box
    White Box
    R,E,M-
    Access
    Metro
    Router
    vOLT
    Control

    View Slide

  79. Compute Powers
    ONOS Controller Cluster
    vRouter
    Control
    Underlay
    Control
    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
    Open Source
    SDN-based
    Bare-metal
    White Box
    White Box
    R,E,M-
    Access
    Metro
    Router
    vOLT
    Control
    vSG
    vSG
    vSG
    VNF
    VNF
    VNF
    VNF
    VNF VNF
    VNF
    VNF VNF VNF
    VNF
    VNF

    View Slide

  80. Virtual Network
    ONOS Controller Cluster
    vRouter
    Control
    Underlay
    Control
    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
    Open Source
    SDN-based
    Bare-metal
    White Box
    White Box
    R,E,M-
    Access
    Metro
    Router
    vOLT
    Control
    vSG
    vSG
    vSG
    VNF
    VNF
    VNF
    VNF
    VNF VNF
    VNF
    VNF VNF VNF
    VNF
    VNF
    OVS OVS OVS OVS OVS
    Overlay
    Control

    View Slide

  81. Service Orchestration
    ONOS Controller Cluster
    vRouter
    Control
    Underlay
    Control
    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
    Open Source
    SDN-based
    Bare-metal
    White Box
    White Box
    R,E,M-
    Access
    Metro
    Router
    vOLT
    Control
    vSG
    vSG
    vSG
    VNF
    VNF
    VNF
    VNF
    VNF VNF
    VNF
    VNF VNF VNF
    VNF
    VNF
    OVS OVS OVS OVS OVS
    Overlay
    Control
    XOS (Orchestrator)

    View Slide

  82. Service Model
    Instance
    Instance =
    (VM | Container |
    Container-in-VM)
    Slice =
    (Instances[ ] + Networks[ ])
    vOLT
    Controller
    vSG
    Controller
    vRouter
    Subscriber
    “Service Graph” =
    (TenantRoot + Services[ ] + Tenants[ ])
    Controller
    Service =
    (“Controller” + Slices[ ])
    Instance Instance
    Controller

    View Slide

  83. On-boarding Services
    Controller
    vSG
    Controller
    vRouter
    Residential
    Subscribers vOLT
    Controller
    Controller
    vCDN
    vCE
    Controller
    Enterprise
    Customers
    Controller
    vOAM
    Mobile
    Subscribers vBBU
    Controller Controller
    vSGW
    Extensible By Design!

    View Slide

  84. Use Cases
    ONOS Controller Cluster
    vRouter
    Control
    Underlay
    Control
    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
    Open Source
    SDN-based
    Bare-metal
    White Box
    White Box
    R,E,M-
    Access
    Metro
    Router
    vOLT
    Control
    vSG
    vSG
    vSG
    VNF
    VNF
    VNF
    VNF
    VNF VNF
    VNF
    VNF VNF VNF
    VNF
    VNF
    OVS OVS OVS OVS OVS
    Overlay
    Control
    XOS (Orchestrator)
    Residential Mobile Enterprise

    View Slide

  85. Metro
    Router
    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
    Open Source
    SDN-based
    Bare-metal
    White Box
    White Box
    R,E,M-
    Access
    Final CORD Architecture
    85
    ONOS Controller Cluster
    vRouter
    Control
    XOS (Orchestrator)
    vSG
    VNF
    VNF VNF
    VNF
    vSG VNF
    VNF
    VNF
    VNF
    vSG VNF
    VNF VNF
    VNF
    OVS OVS OVS OVS OVS
    Residential Mobile Enterprise
    Underlay
    Control
    Underlay
    Overlay
    Control
    Overlay
    vOLT
    Control

    View Slide

  86. ONF Community
    Open and Community-Driven
    86

    View Slide

  87. 87
    Ref: https://ambassadors.opennetworking.org/ambassadors/

    View Slide

  88. ONOS Build 2017, Seoul
    88

    View Slide

  89. Ambassador Dinner
    89

    View Slide

  90. Global SDNFV Tech Conference 2017, Beijing
    90

    View Slide

  91. Global SDNFV Tech Conference 2017, Beijing
    91

    View Slide

  92. Join us!
    92

    View Slide

  93. Thank you!
    • https://www.opennetworking.org/

    View Slide