CORD Overview - CORD Workshop, GNTC

#onf #gntc #cord

Transcript

1. CORD Overview
   Phil Huang 黃秉鈞
   Edgecore Networks Solution Engineer / phil_huang@edge-core.com
   ONF A-Team / phil@cord-ambassadors.org
   Global Network Technology Conference 2017, Beijing, China, Nov. 29, 2017
   

   View Slide

2. 2
   黃秉鈞 Phil Huang
   • Member of ONF Ambassador Steering Team
   • Edgecore Networks Solution Engineer
   • SDNDS-TW Co-Founder
   Ref: https://www.linkedin.com/in/phil-huang-09b09895/
   ONF: Open Networking Foundation
   

   View Slide

3. ONF – An Operator Led Consortium with
   A Track Record of Impact
   “Nearly 40% of all end-customers
   will have service provided by …
   CORD by mid-2021”
   Roz Roseboro
   Heavy Reading
   “70% of operators worldwide are
   planning to deploy CORD”
   Michael Howard
   IHS Markit
   

   View Slide

4. CORD Overview
   4
   

   View Slide

5. CORD Highlights
   • Network edge is undergoing a major transformation
   • Represents a huge opportunity
   • CORD has emerged as a compelling platform for the new network edge
   • Leverages disaggregation, open source and white boxes
   • Puts SDN, NFV and cloud technologies into a compelling solution
   • Many service providers experimenting and have plans for trials and deployment
   • CORD has a growing community of 60+ companies representing various stakeholders
   • CORD has been demonstrated to support all three domains of use
   • Residential (R-CORD)
   • Mobile (M-CORD)
   • Enterprise (E-CORD)
   

   View Slide

6. Where do Service Providers Face Challenges
   and Spend Their Money?
   6
   Image Source: https://www.telarus.com/uploads/files/795/xlarge/att-network-map.jpg
   Backbone is a relatively small part of the network
   ~ 80% of spend is in the Network Edge
   

   View Slide

7. Central Office – The Most Important
   Infrastructure for Service Providers
   Central Office
   Residential
   Enterprise
   Mobile
   • CO is a service provider’s
   “gateway” to its customers
   • There are 1000s of COs
   • ‘End-to-end’ user experience
   controlled by this facility
   1Central Office can be small or large and has different names in different contexts. 7
   

   View Slide

8. Commodity Clouds
   Users
   Central
   Offices
   This Outdated Edge is Greatest Opportunity for Operators
   Telco & IX Cloud
   

   View Slide

9. Commodity Clouds
   Users
   Edge Cloud
   This Outdated Edge is Greatest Opportunity for Operators
   Telco & IX Cloud
   

   View Slide

10. Commodity Clouds
    Users
    Edge Cloud
    • Subscriber experience dictated from here
    • Human Reaction time: 210ms
    • Latency to Centralized Cloud: 100 – 400ms
    • Emerging Applications Require Edge Processing
    • AR visual overlays
    • Autonomous Vehicle Coordination
    • IoT Battery Life (50-75% improvement with edge processing)
    This Outdated Edge is Greatest Opportunity for Operators
    Edge Processing is Vital
    Telco & IX Cloud
    

    View Slide

11. CORD Mission: Enable the Edge Cloud
    Economies of a datacenter
    Infrastructure built with a few commodity building blocks using
    open source software and white boxes
    Agility of a cloud provider
    Software platforms that enable rapid creation of new services
    All in an Easy to Consume Platform
    11
    

    View Slide

12. CORD High Level Architecture
    12
    Large number of COs
    Evolved over 40-50
    years
    300+ Types of
    equipment
    Huge source of
    CAPEX/OPEX
    SDN NFV
    Cloud
    CORD-XOS Controller
    Mobile
    ROADM
    (Core)
    Metro
    Ethernet
    BBUs PON
    OLTs
    Residential
    Enterprise
    Shared Cloud Infrastructure
    

    View Slide

13. CORD High Level Architecture
    13
    Large number of COs
    Evolved over 40-50
    years
    300+ Types of
    equipment
    Huge source of
    CAPEX/OPEX
    SDN NFV
    Cloud
    CORD-XOS Controller
    Mobile
    ROADM
    (Core)
    Metro
    Ethernet
    BBUs PON
    OLTs
    Residential
    Enterprise
    Shared Cloud Infrastructure
    

    View Slide

14. CORD High Level Architecture
    14
    Large number of COs
    Evolved over 40-50
    years
    300+ Types of
    equipment
    Huge source of
    CAPEX/OPEX
    SDN NFV
    Cloud
    CORD-XOS Controller
    Mobile
    ROADM
    (Core)
    Metro
    Ethernet
    BBUs PON
    OLTs
    Residential
    Enterprise
    Shared Cloud Infrastructure
    vOLT, vSG,
    vRouter, vCDN
    vRAN & vEPC SD-WAN & VPN
    

    View Slide

15. Service Provider Traction
    North America
    • AT&T: R-CORD, M-CORD (Multi-Service Edge), vOLTHA
    • Verizon: M-CORD
    • Sprint: M-CORD
    • Comcast: R-CORD
    • CenturyLink: R-CORD
    • Google: Multi-access CORD
    Asia & Australia
    • China Unicom: M-CORD, E-CORD
    • China Mobile: M-CORD and E-CORD
    • NTT, NTT East: IP+Optical, R-CORD
    • SK Telecom: M-CORD
    • Telstra: M-CORD
    • Reliance Jio: M-CORD
    Europe
    • Deutsche Telekom: R+M-CORD (Hybrid
    CORD)
    • Telefonica: R-CORD, M-CORD
    • Telecom Italia: M-CORD
    • Colt: R-CORD
    • Turk Telekom/Netsia: M-CORD & ONOS
    SDN Control
    Interest continues to grow on a
    monthly basis.
    Many successful POCs and lab trials
    and a few field trials
    

    View Slide

16. CORD Differentiators and Value Prop
    • Unique and strong partnership
    • ONF + Service Providers + Vendors + a growing collaborating community
    • Integrated solutions platform for “service” delivery
    • Complete integrated platform: ONOS, Trellis, XOS, Docker, OpenStack, …
    • A common platform for three critical (and massive) domains of use
    • Residential, enterprise and mobile
    • Leverages merchant silicon and white boxes
    • Not only for servers and switches but also for access (GPON, LTE/cellular, …)
    • Designed to be Customized
    • Vendors and Operators can customize, add VNFs, and deliver superior solutions faster
    16
    

    View Slide

17. CORD Within the
    Open Source Landscape
    17
    

    View Slide

18. Commodity Core
    Clouds
    Users
    Edge Cloud
    Amazon/Google
    Telco
    Cloud
    Telco
    Cloud
    Telco
    Cloud
    Multi-Tiered Cloud
    Telco Core Cloud
    CORD
    CORD
    CORD
    CORD
    CORD
    

    View Slide

19. Specialized Edge Datacenters with Centralized Orchestration
    CORD = Edge Optimized Cloud
    – Unique Capabilities for the Edge
    • Subscriber Access
    • Real-time response and control
    • Combination of Micro-Services and Fabric-Services
    CORD Central Office
    CORD Central Office
    CORD Edge Cloud
    Edge Service
    Edge Service
    Edge Service
    Edge Service
    Composite-VNFs
    Users Telco Cloud
    (e.g. AT&T AIC)
    Users
    Users
    CORD exposes a set of
    Edge Services to ONAP
    

    View Slide

20. Not All Services Should be Run on a Server
    • CORD Service Building Blocks
    – Micro-Services - Images that run in containers on servers
    – Fabric-Services - Functions that run in switches
    • CORD Service Graphs chain micro-services and fabric-services
    – Elements run on servers (x86 or ARM)
    – Elements run in the OpenFlow (or P4) enabled dataplane
    • Different price/performance ratio
    CORD Service
    Micro-Service
    Fabric-Service Fabric-Service
    Micro-Service
    XOS Service Graph
    • CORD Edge Services can be instantiated and
    controlled by a global orchestrator
    • As the dataplane becomes more programmable (P4),
    even more functionality can be moved into
    the fabric
    

    View Slide

21. Open Source Landscape
    CORD’s Relationship to OPNFV
    21
    

    View Slide

22. Both Leverage Many Common Upstream Open Source Projects
    Single Pre-Integrated Platform
    Easy to Extend and Customize
    Lots of Different NFVI Options
    Includes Ready-to-Deploy Services
    Vendor VNFs Easy to Add
    VNFs Out-of-Scope
    1 Platform
    3 Solutions (Residential, Enterprise & Mobile)
    63 Scenarios (combinations)
    Various combinations of projects upon which
    VNFs and Solutions can be Developed
    CORD
    OPNFV
    Addressing needs of the NFV Space
    Similarities Differences
    Compare and Contrast with
    

    View Slide

23. CORD Learning Labs
    Now Available as Beta
    23
    

    View Slide

24. Announcing - CORD Primer Learning Labs
    Total Lab
    Duration
    12 Hrs
    Lab I 4 Hrs
    Lab II 4 Hrs
    Lab III 4 Hrs
    $125
    $125
    $125
    CORD Network Management
    CORD Virtual Networks
    CORD Services Framework
    Hands-on CORD learning and skill development
    Developed and Hosted by Criterion Networks in collaboration with ONF
    Online subscription-based pricing model
    

    View Slide

25. CORD Primer Learning Labs Outline
    Lab I. Network Management (4 Hrs) Lab II. Virtual Networks (4 Hrs) Lab III. CORD Services Framework (4 Hrs)
    1. Create standard SDN topologies with OVS 1. Openstack Keystone for user/tenant creation 1. CORD Overview
    2. Add OpenFlow rules for port based forwarding (using ovs-ofctl) 2. Openstack Glance for image management 2. XOS Overview
    3. Add OpenFlow rules for IP/ARP based forwarding (using ovs-ofctl) 3. Openstack Nova for flavor/key/security groups creation 3. Explore XOS GUI
    4. Use of Iperf to simulate huge traffic in SDN 4. Explore Openstack Horizon dashboard 4. Verify Openstack services are up and running
    5. Openflow Multi-table rules to convert OVS as NAT router 5. Vxlan Networking using OVS 5. verify XOS services are up and running
    6. Create custom SDN topologies 6. Vxlan Networking using Linux Bridge 6. Verify ONOS services are up and running
    7. Bring up ONOS controller and activate apps
    7. Explore Openstack Neutron ML2 configuration for ONOS
    integration
    7. R-CORD use-case: vSG with one client1
    a. Verify vSG tenant created as part of bring up
    b. Create a client1 with c-tag and s-tag
    c. Verify client can receive Private IP address and Ping Internet
    8. ONOS controller with reactive forwarding app
    8. Create tenant network in openstack and verify VTN app
    8. Packet walkthrough from subscriber1 to Internet via vSG
    container1
    9. Explore ONOS commands for verifying topology and flows
    9. Create VMs and verify OpenFlow rules in OVS (Overlay
    Networking) for connectivity
    9. Bring up one more client2 with same s-tag but different c-tag
    10. Explore ONOS GUI
    10. Packet walkthrough from subscriber2 to Internet via vSG
    container2
    11. Connect leaf-spine topology with ONOS and packet forwarding 11. Bring up one more client3 with different s-tag and c-tag
    12. ONOS REST API
    12. Packet walkthrough from subscriber3 to Internet via vSG
    container3
    

    View Slide

26. Open for Beta Users – Invite Only
    Registration/Sign-on Page:
    https://academy.criterionnetworks.com
    Limited to 25 users
    Intended for Motivated Users - Nominal Price ($50)
    Beta users providing feedback will receive full refund
    

    View Slide

27. Accessing CORD Learning Labs
    1
    User goes to Academy Portal
    2 3 4
    Clicks on the Training tab on the
    Academy Portal
    Clicks on Learning Labs on the Training page Lands on the CORD Learning Labs
    platform showing a list of CORD labs
    5
    User selects CORD Network
    Management Lab from the available
    Labs.
    6 7 8
    User clicks the Launch button to
    launch the Network Management
    Lab.
    Lab gets launched and available in a
    matter of a few minutes.
    User completes the Lab modules
    using detailed instruction steps.
    When done with a lab, fill out survey for a full refund of any fees paid:
    https://www.surveymonkey.com/r/cordlab1
    https://www.surveymonkey.com/r/cordlab2
    https://www.surveymonkey.com/r/cordlab3
    Registration/Sign-on Page:
    https://academy.criterionnetworks.com
    

    View Slide

28. P4 Demo
    Towards the Next Generation of Fabric
    28
    

    View Slide

29. P4 Relationship to ONF Projects
    P4 is Emerging as
    a Follow-On for
    OpenFlow
    

    View Slide

30. Where P4 Fits Into CORD
    CORD-XOS Controller
    Mobile
    ROADM
    (Core)
    Metro
    Ethernet
    BBUs PON
    OLTs
    Residential
    Enterprise
    Shared Cloud Infrastructure
    CORD Fabric can
    migrate
    towards P4
    for greater
    programmability
    

    View Slide

31. Fixed-function data plane pipeline
    P4 Runtime – Enabling Data Plane Pipeline Independence
    A COMPLEX PIPELINE
    THAT DOES EVERYTHING
    ...different vendors in their own way
    Application
    OpenFlow
    Table Management
    Packets
    Requires
    tweaks for
    variations in
    forwarding
    pipelines
    

    View Slide

32. Programmable data plane pipeline
    Fixed-function data plane pipeline
    P4 Runtime – Enabling Data Plane Pipeline Independence
    JUST WHAT
    I NEED
    A COMPLEX PIPELINE
    THAT DOES EVERYTHING
    ...different vendors in their own way
    Application
    Application
    OpenFlow
    Table Management
    Table {
    match
    actions
    }
    P4 program
    Packets
    P4 Runtime
    Table Management
    Packets
    Requires
    tweaks for
    variations in
    forwarding
    pipelines
    P4 Runtime enables
    interface to be
    generated from
    P4 program
    Controller can work
    with a variety of
    data planes without
    modification P4 Runtime Agent
    compile
    gRPC
    

    View Slide

33. Programmable data plane pipeline
    Fixed-function data plane pipeline
    P4 Runtime – Enabling Data Plane Pipeline Independence
    JUST WHAT
    I NEED
    A COMPLEX PIPELINE
    THAT DOES EVERYTHING
    ...different vendors in their own way
    Application
    Application
    OpenFlow
    Table Management
    Table {
    match
    actions
    }
    P4 program
    Packets
    P4 Runtime
    Table Management
    Packets
    Requires
    tweaks for
    variations in
    forwarding
    pipelines
    P4 Runtime is of
    value even if the
    data plane is not
    programmable
    P4 can be used to
    unambiguously
    describe any
    pipeline
    P4 Runtime Agent
    compile
    gRPC
    2
    1
    

    View Slide

34. Live Demo of P4 Runtime
    • Applications can bring their own P4 pipelines
    • ONOS run P4 Runtime to
    § Manage Leaf-spine fabric
    • Google’s ”tor.p4” used as P4 program
    § Pipeline definition
    • Demonstrated on 2 switch types
    § BMv2 software switch
    § Barefoot Tofino hardware switches
    34
    Protobuf: Protocol Buffers – Google’s data interchange format
    

    View Slide

35. CORD Vision for leveraging a P4 Enabled Data Plane
    Virtualization is more than a VNF
    Monolithic VNFs
    Ports of legacy
    systems to x86
    Failed to deliver the
    hoped for economics
    

    View Slide

36. CORD Vision for leveraging a P4 Enabled Data Plane
    Virtualization is more than a VNF
    Monolithic VNFs
    Ports of legacy
    systems to x86
    Micro-Services
    Functions
    disaggregated and
    cloud agility achieved
    Economic crossover
    starts to be achieved
    Failed to deliver the
    hoped for economics
    

    View Slide

37. CORD Vision for leveraging a P4 Enabled Data Plane
    Virtualization is more than a VNF
    Monolithic VNFs
    Ports of legacy
    systems to x86
    Micro-Services
    Functions
    disaggregated and
    cloud agility achieved
    Micro-Services (x86)
    blended with
    P4 Enabled
    Fabric-Services
    Portions of services are run
    in the data plane to achieve
    speed and scale
    100x performance
    improvements possible pushing
    functionality into programmable
    data plane
    Economic crossover
    starts to be achieved
    Failed to deliver the
    hoped for economics
    

    View Slide

38. Thank You
    38
    

    View Slide