Introduction to Open Source Network and Software Defined Network

Transcript

1. OPEN NETWORKING AND SDN HUNG-WEI CHIU
2. WHO AM I • Hung-Wei Chiu (邱宏瑋) • hwchiu@linkernetworks.com • 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, Floodlight, awesome-sdn)
3. OUTLINE • Open Networking • Open Source Networking • Open Compute Project • What is SDN and ONF
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 • Reference: Open Source Networking Days
8. KEY ELEMENT OF OPEN SOURCE ARCHITECTURES › Controller for ONAP › 30/38 SDN scenarios in OPNFV › Proposed “Nirvana Stack”
9. OPEN SOURCE NETWORKING LANDSCAPE 9 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
12. OPEN COMPUTER PROJECT • OCP • Founded 2011 • Global community for Open IT hardware Network Storage Telco Data Center Server Open Rack Hardware Management
14. OCP, NETWORKING (SCOPE) • Fully disaggregated and open networking HW & SW • Operating System – Linux based operating system & developer tools, and ReST API’s • Fully automated configuration management & bare metal provisioning • Universal & Multi-Form Factor Switch motherboard hardware • Fully open integration & connectivity • Energy efficient power & cooling designs • Software Defined Networking (SDN)
15. SUB PROJECTS • Subprojects of OCP Networking • Open Network Install Environment (ONIE) • Open Network Linux (ONL)
16. EXAMPLE: WEDGE 100 Facebook Design CPU intel/AMD/… ASIC Broadcom/Mellanox/… Hardware Software NOS: Open Network Linux Forwarding Agent: FBOSS BMC: OpenBMC Switch as a Server
17. OCP NETWORKING SOFTWARE • Switch Abstraction Interface – SAI • Define API to provide a vendor-independent way of controlling forwarding elements, such as a switching ASIC, and NPU or a software switch in a uniform manner. • Open Network Linux – ONL • Linux distribution (Debian) with added driver and configuration for running bare metal switches. • Open Network Install Environment – ONIE • Open install environment for bare metal network switch • ONIE enable a bare metal network switch ecosystem where end users have a choice among different network operation systems
18. BUILDING ON BARE METAL Bare metal switch Bare metal switch U-Boot & ONIE Bare metal switch U-Boot & ONIE Network OS Bare metal switch U-Boot & ONIE Network OS Application Bare metal switch Bare metal server U-Boot & PXE Bare metal server U-Boot & PXE Linux,Windows, etc Bare metal server U-Boot & PXE Linux,Windows, etc Application Server Switch
21. SUMMARY • White Box Switch = Hardware + ONIE • Open Networking = Apps + NOS +White Box
22. ONIE
23. WHITE BOX SWITCH MODEL Switch Data Plane Control Plane Applications Switch Data Plane Switch Data Plane Linux OS Applications Switch Control Plane Applications Control Protocol Traditional Switch SDN-based System Open Networking Switch
24. Before we talk about the SDN. Let we see the history of programmable network.
25. Reference:The Road to SDN: An Intellectual History of Programmable Networks
26. 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
27. SDN HISTORY • Google publish a paper related to SDN in 2013 • B4: Experience with a Globally-Deployed Software Defined WAN • How aboutTaiwan? • Industry • Hardware/Agent • Campus • NCTU • Government • ITRT/III • Contributor (Software) • Almost from NCTU …
28. SDN • The physical separation of the network control plane from the forwarding plane, and where a control plane controls several devices.
29. THE SDN ARCHITECTURE • Directly programmable • Agile • Centrally managed • Programmatically configured • Open standard-based and vendor-neutral
30. 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/…
31. THE SDN ARCHITECTURE • Northbound API • Restful • gRPC Northbound API Southbound API • Southbound API • Openflow • OVSDB • SNMP • Netconf • P4 • …
32. 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
33. 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
34. 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
35. 2016/10/19 • ONF + ON.LAB  ONF • For Member X For Public -> For Member
40. THE ECOSYSTEM • 200+ Members Strong Vibrant Operator Led Consortium Positioned for Success • PARTNER • COLLABORATING INNOVATOR • INNOVATOR • COLLABORATOR
41. 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
42. ONF’S SCOPE Disaggregated boxes: Packet switch, ROADM, eNodeB, OLT, RAN … Programmable Forwarding Plane Open Source: ONAP, Open-O, Open Source MANO Global Orchestrators New ONF Scope of Focus Control Plane ONOS Control (OpenFlow, P4) Config (NetConf/Yang, OpenConfig) Alternative Controllers (e.g. ODL) Solutions Platforms M- CORD R- CORD E-CORD CORD VNFs Alternative VNF Frameworks (e.g. OPNFV) Service APIs: TOSCA, RESTful Network Intent-Based APIs Standards & Interworking APIs
44. SUMMARY Open Source Networking is no longer about components… it is about multiple communities coming together to build a new world.