Upgrade to Pro — share decks privately, control downloads, hide ads and more …

An introduction of Open Source Networking, SDN ...

Hung-Wei Chiu
December 24, 2017

An introduction of Open Source Networking, SDN and ONF

The slides of first meetup hold by SDNDS-TW and Cloud Native User Group Taiwan

Hung-Wei Chiu

December 24, 2017
Tweet

More Decks by Hung-Wei Chiu

Other Decks in Technology

Transcript

  1. WHO AM I • Hung-Wei Chiu (邱宏瑋) • hwchiu@linkernetworks.com •

    Blog: hwchiu.com • Experience • Software Engineer at Linker Netowrks • Software Engineer at Synology (2014~2017) • Co-Found of SDNDS-TW • Open Source experience • SDN related projects (mininet, ONOS, CORD, Floodlight)
  2. Hyperledger ODPi R Consortium Linux Node.js Foundation OpenAPI JS Foundation

    Open Mainframe Open Project MAMA Let’s Encrypt! CII OpenDaylight OPNFV ONAP CORD/ONOS FRR OvS, IO Visor PNDA, SNAS.io OpenSwitch, OSC FD.IO, DPDK AllJoyn/IoTivity EdgeX Foundry Zephyr Project AGL Dronecode Yocto Project Tizen Cloud Foundry CNCF OCI Xen Project THE LINUX FOUNDATION LEADS OPEN SOURCE MOMENTUM Cloud, Containers & Virtualization Embedded/IOT/Auto Networking & Orchestration Platforms & Applications Blockchain, Data, Analytics * Few examples only 4
  3. OPEN SOURCE NETWORKING • The Linux Foundation • Foster innovation

    across the entire open source networking ecosystem. • Coordinate across multiple open source projects. • Initiatives and identify key areas for collaboration to create an open source networking stack.
  4. 6

  5. 7

  6. OPEN SOURCE NETWORKING • You can build your solution from

    those open source projects. • For example. If you want to choose a software switch in your networking. • You can use one of the following open source project. • OpenvSwitch • FD.io • io.Visor • You can also integrate those with DPDK to support high performance.
  7. OTHER EXAMPLE • An example from the Open Source Networking

    Day London • Combine some open source projects together • OpenStack • OpenDayLight • FD.io • OPNFV • ONAP • Reference: Open Source Networking Days
  8. KEY ELEMENT OF OPEN SOURCE ARCHITECTURES › Controller for ONAP

    › 30/38 SDN scenarios in OPNFV › Proposed “Nirvana Stack” Optical Data Plane ASIC Data Plane Server Control Plane (CPU) Network OS Control Plane Software Orchestration, Management, Policy, Services Residential & Business Products/Services Service Provider Stack Option ONAP
  9. OPEN SOURCE NETWORKING LANDSCAPE 11 Product, Services & Workloads Disaggregated

    Hardware Network Control Operating Systems Cloud & Virtual Management Orchestration, Management, Policy Application Layer / App Server IO Abstraction & Data Path System Integration & Test Automation Network Data Analytics Automation of Network + Infrastructure + Cloud + Apps + IOT Linux Foundation Hosted Outside Linux Foundation Standards Infrastructure Software Services SW Components + Data Plane Acceleration + Open HW (OPNFV, FDIO, OCP) • Lower CapEx • Test automation – Ease of Deployment Network Service Orchestration (ODL, OPNFV, ONAP) • Common hardware-software management • Easy VNF onboarding • Common model across clouds Closed-Loop Automation, Standards Harmonization • Analytics integration (ONAP + PNDA) • Framework alignment with MEF, TMF
  10. 12

  11. Before we talk about the SDN. Let we see the

    history of programmable network.
  12. SDN HISTORY • Software-Defined Networking (SDN) • Stanford Professor Nick

    McKeown publish a paper in 2008. • OpenFlow: Enabling Innovation in Campus Networks • OpenFlow first version 1.0 in 2009 • Open Network Foundation (ONF) in 2011
  13. SDN HISTORY • Google publish a paper related to SDN

    in 2013 • B4: Experience with a Globally-Deployed Software Defined WAN • How about Taiwan? • As I know, NCTU starts to study the SDN around 2012/2013. • We start to contribute to those SDN related open source projects from 2013 • Controller • Floodlight, Ryu,Trema, ONOS • Network Emulator • mininet
  14. SDN • The physical separation of the network control plane

    from the forwarding plane, and where a control plane controls several devices.
  15. THE SDN ARCHITECTURE • Directly programmable • Agile • Centrally

    managed • Programmatically configured • Open standard-based and vendor-neutral
  16. THE SDN ARCHITECTURE • Network control is directly programmable because

    it is decoupled from forwarding functions. Data Plane Switch Application Controller Control Plane Control Protocol Application Control Plane Data Plane Switch Cisco/Juniper/…
  17. THE SDN ARCHITECTURE • Northbound API • Restful • gRPC

    Northbound API Southbound API • Southbound API • Openflow • OVSDB • SNMP • Netconf • P4 • …
  18. SUMMARY Servers Servers Switches (e.g .. Openflow) TOR Swithes DC

    Gateways (Edge Routers) Infrastructure Layer Flow Optimizer Network Policy Topology viewer Load Balancer Bandwidth Application Layer Control Layer Automation GUI L2/L3 Cluster L3VPN ACL/QoS DHCP Southbound plugins – Ovsdb, Netconf, Openflow, etc.. Northbound API Southbound API
  19. SDN Architecture Application Layer Control Layer Infrastructur e Layer SDN

    Controller Network Devices Network Devices Network Devices Cloud Orchestration Business Application SDN Application (e.g.. OpenStack, CloudStack, Kubernetes) OpenFlow, OVSDB, NetConf, P4… Restful, gRPC …
  20. KEY ELEMENT OF OPEN SOURCE ARCHITECTURES › Controller for ONAP

    › 30/38 SDN scenarios in OPNFV › Proposed “Nirvana Stack”
  21. ONF • Open Networking Foundation • Non-profit organization • For

    Menber • Led consortium driving transformation of network infrastructure. • Serves as the umbrella for a number of projects building solutions • Leveraging network disaggregation • White box economics • Open source software • Software defined standards
  22. ONLAB • Open Networking Lab • Non-profit organization. (501 C3)

    • For Public • Build tools and platforms that enable and accelerate SDN and make them available through open source. • Educate the public on the benefits of SDN • Provide thought leadership to ensure continued innovation around SDN
  23. 29

  24. THE ECOSYSTEM • 200+ Members Strong Vibrant Operator Led Consortium

    Positioned for Success • Partner • Collaborating Innovator • Innovator • Collaborator
  25. THE ECOSYSTEM Partner 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
  26. 37

  27. WHAT IS ONOS? • Open Network Operating System (ONOS) •

    An open source SDN network operation system • SDN controller
  28. We have a SDN controller (ONOS) now. How can we

    use it in a real environment ?
  29. CORD • Central Office Re-architected as a Data-center • It’s

    too complicated to explain the whole detail of CORD. • We just describe its architecture.
  30. Reference: http://slideplayer.com/slide/11272061/ White Box White Box White Box White Box

    White Box White Box White Box White Box White Box White Box White Box White Box OVS OVS OVS OVS VNF VNF VNF VNF VNF VNF VNF VNF VNF VNF VNF VNF
  31. 44

  32. SUMMARY Open Source Networking is no longer about components… it

    is about multiple communities coming together to build a new world.