Interop_NY_OpenDayLight_2013

advertisement
OpenDaylight:
Open Source SDN Platform
Inder Gopal, Vice President, Networking Development and
Technical Strategy, IBM
David Meyer, SP CTO and Chief Scientist, Brocade
@opendaylightsdn #opendaylight
Agenda
Why SDN matters
What OpenDaylight is and does
The open source difference
How to get involved
Networks are Evolving
Software Defined Networking (SDN) reset business opportunities
Applications and services that ride on,
optimize, exploit, and manage the
network
Focus Area
for OpenDaylight
Enterprise apps
A Software Defined Network
platform that makes the network
more programmable, agile, and
efficient
Security, load
balancing, etc. services
API’s
Software Defined Network (SDN)
Platform
Open protocols with enablement for proprietary extensions
A network that provides the
physical connectivity
Physical Network
Physical Network
3
Why SDN?
SDN is not a product or an endpoint. It's an
architectural approach.
By 2016, SDN will account for a remarkable
35% share of the Ethernet switching market in
the datacenter, up from almost negligible
penetration in 2012.
Source: IDC, December 2012
4
What Is OpenDaylight?
OpenDaylight is a community-led and industrysupported open source framework to advance
Software-Defined Networking (SDN).
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.

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.
6
Broad Industry Support for
OpenDaylight
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
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
9
OpenDaylight Open 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
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)
11
Project Framework
12
Architectural Framework
GUI
multi-tenant
virtual
networks
CLI
integration
L4-L7
service
abstraction
s
OpenStack
Quantum
CloudStack
oVirt
…
network
applications,
orchestration,
and services
OpenDaylight APIs (REST)
topology
mgr
stats
mgr
switch /
device
mgr
fwding
…
virtual network
manager
storage
services
L4-L7 service
manager
extensions /
addn’l svcs
service abstraction layer
(plug-in mgr., capability abstractions, …)
OpenFlow
1.0
1.3
Open
switch
API
SAN
(SMI-S)
hw-independent interfaces
and data models
other std. protocols
(ONF, IETF, …)
vendor-specific
interfaces
virtual
forwarding
enhancements
inter-controller
comm
base network service functions
controller
platform
southbound interfaces
& protocol plugins
data plane interfaces and
enhancements
(virtual switches,
physical device interfaces)
Major Architectural Feature:
Service Abstraction Layer (SAL)
https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:FAQ
SAL Plugin Design Process
Project Life Cycle Schematic
All project graduation reviews managed by TSC
proposed
new projects (not yet
part of OpenDaylight)
“bootstrap”
temporary entry point for
projects during startup
phase
incubation
core
nascent projects
mature
successful, active
projects, perhaps with
limited community
projects core to
OpenDaylight platform
Project
Projects in the OpenDaylight “Hydrogen”
Release
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
Support for traffic engr with BGP-LS (BGP protocol library and topology model) and
PCEP (path programming model)
Cisco
OVSDB
OVSDB configuration and management protocol support (e.g., for Open vSwitch and
other OVSDB servers)
Univ. of Kentucky
LISP Flow Mapping
LISP (locator/identifier separation protocol) plugin, LISP mapping service (can be used
to implement virtual networks)
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 OVSbased data plane
IBM
17
Service Provider Edition
DDoS
Protection
Management
GUI/CLI
Network Applications
Orchestration & Services
OpenDaylight APIs (REST)
Affinity
Service
Base Network Service Functions
Topology
Mgr
Stats
Mgr
Switch
Mgr
Host
Tracker
Shortest
Path
Forwarding
LISP
Service
Network
Config
Controller Platform
Service Abstraction Layer (SAL)
(plug-in mgr., capability abstractions, flow programming, inventory, …)
OpenFlow
1.0
1.3
SNMP
NETCONF
OpenFlow Enabled
Devices
Open vSwitches
BGP-LS
PCEP
LISP
Additional Virtual &
Physical Devices
Southbound Interfaces
& Protocol Plugins
Data Plane Elements
(Virtual Switches,
Physical Device
Interfaces)
Virtualization Edition
VTN
Coordinator
Management
GUI/CLI
OpenStack
Neutron
DDoS
Protection
Network Applications
Orchestration & Services
OpenDaylight APIs (REST)
Affinity
Service
Base Network Service Functions
Topology
Mgr
Stats
Mgr
Switch
Mgr
Host
Tracker
Shortest
Path
Forwarding
Network
Config
OpenStack Service
VTN
Manager
DOVE
Mgr
Controller Platform
Service Abstraction Layer (SAL)
(plug-in mgr., capability abstractions, flow programming, inventory, …)
Southbound Interfaces
& Protocol Plugins
OpenFlow
1.0
1.3
OpenFlow Enabled
Devices
NETCONF
OVSDB
Open vSwitches
Additional Virtual &
Physical Devices
Data Plane Elements
(Virtual Switches,
Physical Device
Interfaces)
Getting Involved
Developer documentation: 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
Getting Involved
Open mailing lists: lists.opendaylight.org
– Discussion groups on specific projects
– Cross-project discussions
– Announcements
Resources
More information and to join:
www.opendaylight.org
IRC: #opendaylight on Freenode
Thanks!
@opendaylightsdn #opendaylight
Download