Accelerating Open Source SDN and NFV

Transcription

1 Accelerating Open Source SDN and NFV February 4, 2014

2 Overview Why Software-Defined Networking (SDN) matters What is OpenDaylight and what does OpenDaylight do? The open source difference How to get involved 2

3 Networks are Evolving Software Defined Networking (SDN) resets business opportunities Applications and services that ride on, optimize, exploit, and manage the network Enterprise apps Security, load balancing, etc. services Software Defined Networking is a software layer that makes the network more programmable, agile, and efficient APIs So#ware- Defined Network (SDN) Pla5orm Open protocols with enablement for proprietary extensions A network that provides the physical connectivity Focus Area for OpenDaylight Physical Network Physical Network 3

4 What is the OpenDaylight Project? The OpenDaylight Project is a collaborative open source project that aims to accelerate adoption of Software-Defined Networking (SDN) and create a solid foundation for Network Functions Virtualization (NFV) for a more transparent approach that fosters new innovation and reduces risk. Founded by industry leaders and open to all, the OpenDaylight community is developing a common, open SDN framework consisting of code and blueprints. 4

5 OpenDaylight Project Goals Code: To create a robust, extensible, open source code base that covers the major common components required to build an SDN solution and create a solid foundation for Network Functions Virtualization (NFV) Acceptance: To get broad industry acceptance amongst vendors and users Community: To have a thriving and growing technical community contributing to the code base, using the code in commercial products, and adding value above, below and around. 5

6 Broad Industry Support for OpenDaylight 6

7 Industry Value A broad SDN code base that anyone can use, plug into or contribute new enhancements A common environment for users and application developers Accelerated innovation by avoiding duplication of basic infrastructure Faster and higher quality development through sharing of resources 7

8 Why Open Source? Flexibility Choice Innovation Control Open source is more flexible and can evolve as new technologies and innovations appear, not based on any single vendor's purposes. Examples: Hadoop, Linux, Apache, OpenStack 8

9 OpenDaylight Governance Membership open to all Business leadership: Board of Directors Governance, marketing, operations Technical leadership: Technical Steering Committee (TSC) Technical direction, project selection, technical decisions Meritocracy and transparency Project life-cycle management 9

10 The Code A wide array of technologies contributed by leading companies and developers Pre-existing code, newly created code specifically for OpenDaylight Roughly bi-annual coordinated release cycles First release planned for December 2013 Eclipse Public License (EPL) 10

11 Project Framework 11

12 Architectural Framework GUI CLI multi-tenant virtual networks L4-L7 service abstractions OpenStack Quantum integration CloudStack ovirt network applications, orchestration, and services OpenDaylight APIs (REST) topology mgr base network service functions stats mgr switch / device mgr fwding virtual network manager L4-L7 service manager service abstraction layer (plug-in mgr., capability abstractions, ) storage services extensions / addn l svcs inter-controller comm controller platform OpenFlow Open switch API SAN (SMI-S) other std. protocols (ONF, IETF, ) vendor-specific interfaces southbound interfaces & protocol plugins hw-independent interfaces and data models virtual forwarding enhancements data plane interfaces and enhancements (virtual switches, physical device interfaces) 12

13 Major Architectural Feature: Service Abstraction Layer (SAL) 13

14 SAL Plugin Design Process 14

15 Project Lifecycle Schematic proposed All project graduation reviews managed by TSC new projects (not yet part of OpenDaylight) bootstrap temporary entry point for projects during startup phase incuba-on nascent projects mature core projects core to OpenDaylight platform successful, active projects, perhaps with limited community 15

16 Projects in the Hydrogen Release Project Description Originator (others) Controller Modular, extensible, scalable, and multi-protocol SDN controller based on OSGi Cisco (IBM, RedHat, NEC, etc.) Virtual Tenant Network Multi-tenant network virtualization application using OpenFlow NEC YANG Tools Java-based NETCONF and YANG tooling for OpenDaylight projects Cisco OpenFlow Protocol Library OF 1.3 protocol library implementation Pantheon (IBM, Cisco, Ericsson) OpenFlow Plugin Integration of OpenFlow protocol library in controller SAL Ericsson, IBM, Cisco Affinity Metadata Service APIs to express workload relationships and service levels Plexxi Defense4All DDoS detection and mitigation framework Radware BGP-LS/PCEP OVSDB LISP Flow Mapping Support for traffic engr with BGP-LS (BGP protocol library and topology model) and PCEP (path programming model) OVSDB configuration and management protocol support (e.g., for Open vswitch and other OVSDB servers) LISP (locator/identifier separation protocol) plugin, LISP mapping service (can be used to implement virtual networks) Cisco Univ. of Kentucky ConteXtream SNMP4SDN SNMP protocol support; APIs to manage commodity Ethernet switches Industrial Technology Research Inst. Open DOVE Multi-tenant network virtualization based on overlays, including ctrl plane and OVS-based data plane IBM 16

17 Hydrogen Release Management GUI/CLI VTN Coordinator D4A Protection OpenStack Neutron Network Applications Orchestration & Services OpenDaylight APIs (REST) Base Network Service Functions Affinity Service OpenStack Service Topology Stats Switch FRM Host Tracker ARP Handler LISP Service OVSDB Neutron VTN Manager odmc Controller Platform Service Abstraction Layer (SAL) (plug-in mgr., capability abstractions, flow programming, inventory, ) OpenFlow NETCONF OVSDB SNMP BGP PCEP LISP Southbound Interfaces & Protocol Plugins OpenFlow Enabled Devices Open vswitches Additional Virtual & Physical Devices Data Plane Elements (Virtual Switches, Physical Device Interfaces) VTN: Virtual Tenant Network odmc: open Dove Management Console D4A: Defense4All protection LISP: Locator/Identifier Separation Protocol OVSDB: Open vswitch Data Base Protocol BGP: Border Gateway Protocol PCEP: Path Computation Element Communication Protocol SNMP: Simple Network Management Protocol

18 Base Edition Management GUI/CLI Network Applications Orchestration & Services OpenDaylight APIs (REST) Base Network Service Functions Topology Stats Switch FRM Host Tracker ARP Handler Controller Platform Service Abstraction Layer (SAL) (plug-in mgr., capability abstractions, flow programming, inventory, ) OpenFlow NETCONF OVSDB Southbound Interfaces & Protocol Plugins OpenFlow Enabled Devices Open vswitches Additional Virtual & Physical Devices Data Plane Elements (Virtual Switches, Physical Device Interfaces) VTN: Virtual Tenant Network odmc: open Dove Management Console D4A: Defense4All protection LISP: Locator/Identifier Separation Protocol OVSDB: Open vswitch Data Base Protocol BGP: Border Gateway Protocol PCEP: Path Computation Element Communication Protocol SNMP: Simple Network Management Protocol

19 Virtualization Edition Management GUI/CLI VTN Coordinator D4A Protection OpenStack Neutron Network Applications Orchestration & Services OpenDaylight APIs (REST) Topology Base Network Service Functions Stats Switch FRM Host Tracker ARP Handler Affinity Service OVSDB Neutron OpenStack Service VTN Manager odmc Controller Platform Service Abstraction Layer (SAL) (plug-in mgr., capability abstractions, flow programming, inventory, ) OpenFlow NETCONF OVSDB Southbound Interfaces & Protocol Plugins OpenFlow Enabled Devices Open vswitches Additional Virtual & Physical Devices Data Plane Elements (Virtual Switches, Physical Device Interfaces) VTN: Virtual Tenant Network odmc: open Dove Management Console D4A: Defense4All protection LISP: Locator/Identifier Separation Protocol OVSDB: Open vswitch Data Base Protocol BGP: Border Gateway Protocol PCEP: Path Computation Element Communication Protocol SNMP: Simple Network Management Protocol

20 Service Provider Edition Management GUI/CLI D4A Protection Network Applications Orchestration & Services OpenDaylight APIs (REST) Topology Base Network Service Functions Stats Switch FRM Host Tracker ARP Handler Affinity Service LISP Service Controller Platform Service Abstraction Layer (SAL) (plug-in mgr., capability abstractions, flow programming, inventory, ) OpenFlow NETCONF OVSDB SNMP BGP PCEP LISP Southbound Interfaces & Protocol Plugins OpenFlow Enabled Devices Open vswitches Additional Virtual & Physical Devices Data Plane Elements (Virtual Switches, Physical Device Interfaces) VTN: Virtual Tenant Network odmc: open Dove Management Console D4A: Defense4All protection LISP: Locator/Identifier Separation Protocol OVSDB: Open vswitch Data Base Protocol BGP: Border Gateway Protocol PCEP: Path Computation Element Communication Protocol SNMP: Simple Network Management Protocol

21 Getting Started and Involved Developer documentation is at wiki.opendaylight.org List of current projects in various states Links to documentation on current projects, e.g., how to get/build code, architecture, etc. Information on proposing new projects for OpenDaylight Open mailing lists: lists.opendaylight.org Discussion groups on specific projects Cross-project discussions Announcements #opendaylight IRC channel at freenode.net 21

22 Resources More information and to join: Keep informed and join the #OpenDaylight #ODSummit 22