Introduction to OpenDaylight: Current Events and OpenStack Neutron Integration David Meyer Chief Scientist and SP CTO @Brocade Research Scientist @University of Oregon Chair of the OpenDaylight Board of Directors dmm@{brocade.com , uoregon.edu, 1-4-5.net, ….} Note: This deck contains slides courtesy Colin Dixon and a cast of 1000s
34
Embed
Introduction to OpenDaylight: Current Events and OpenStack Neutron ...dmm/talks/2015/openstack_austin.pdf · Introduction to OpenDaylight: Current Events and OpenStack Neutron Integration
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Introduction to OpenDaylight: Current Events and OpenStack Neutron Integration David Meyer Chief Scientist and SP CTO @Brocade Research Scientist @University of Oregon Chair of the OpenDaylight Board of Directors dmm@{brocade.com, uoregon.edu, 1-4-5.net, ….} Note: This deck contains slides courtesy Colin Dixon and a cast of 1000s
Agenda • What is OpenDaylight? • History: Helium • What’s in store for Lithium • Some Personal Learnings • Neutron Integra>on? • Q&A
What is OpenDaylight OpenDaylight is an Open Source So+ware project under the Linux Founda3on with the goal of furthering the adop>on and innova>on of So+ware Defined Networking (SDN) through the crea>on of a common industry supported plaGorm
Code Acceptance Community
To create a robust, extensible, open source code base that covers the major common components required to build an SDN solu>on
To get broad industry acceptance amongst vendors and users
• Using OpenDaylight code directly or through vendor products
• Vendors using OpenDaylight code as part of commercial products
To have a thriving and growing technical community contribu>ng to the code base, using the code in commercial products, and adding value above, below and around.
Who is OpenDaylight?
Who is OpenDaylight? (Really)
• Like any Open Source Project, OpenDaylight primarily consists of those who show up to do the work.
• Running around 150–200 commits per week • 30 Days: ~400 commits, ~55 contributors
• During releases this is >= 1000 commits and >= 100 commi\ers • 12 Months: ~10,000 commits, ~260 contributors
• Strong integra>on and tes>ng community • This stuff really ma\ers • Staffing I&T is well, challenging
5
Source: https://www.openhub.net/p/opendaylight
Why Open Source?
• Short version: this is how modern infrastructure is built • Modern way to build “undifferen>ated” plumbing
• Long version: • Build more, be\er code faster via collabora>on • Make be\er decisions with devs and users at the table • Spend more >me on the code that ma\ers
• 80/20 rule: 80% of code is non-‐differen>a>ng 6
Aside: Release Naming
7
Brief Note on Project Lifecycles
8
Agenda • What is OpenDaylight? • History: Helium • What’s in store for Lithium • Some Personal Learnings • Neutron Integra>on? • Q&A
AAA: Authen>ca>on, Authoriza>on & Accoun>ng AuthN: Authen>ca>on BGP: Border Gateway Protocol COPS: Common Open Policy Service DLUX: OpenDaylight User Experience DDoS: Distributed Denial Of Service DOCSIS: Data Over Cable Service Interface Specifica>on FRM: Forwarding Rules Manager GBP: Group Based Policy LISP: Locator/Iden>fier Separa>on Protocol
OVSDB: Open vSwitch DataBase Protocol PCEP: Path Computa>on Element Communica>on Protocol PCMM: Packet Cable Mul>Media Plugin2OC: Plugin To OpenContrail SDNI: SDN Interface (Cross-‐Controller Federa>on) SFC: Service Func>on Chaining SNBI: Secure Network Bootstrapping Infrastructure SNMP: Simple Network Management Protocol TTP: Table Type Pa\erns VTN: Virtual Tenant Network
Legend “HELIUM”
AAA AuthN Filter
MD-‐SAL RESTCONF (REST) APIs
OpenFlow Enabled Devices
DLUX VTN Coordinator
OpenStack (via Neutron)
SDNI Wrapper
DDoS Protec3on
Network Applica3ons Orchestra3ons & Services
Open vSwitches Addi3onal Virtual & Physical Devices
Now your controller is ready to connect to switches and handle incoming flows.
ODL Helium: Karaf
ODL Helium: Clustering
• The MD-‐SAL data store, no>fica>ons and RPCs now work in a cluster • Built using the RAFT consensus algorithm on top of Akka messaging • Tolerates f controller failures if you have 2f+1 controllers • Uses sharding for scale-‐out performance
• Lithium work items • Finer-‐grained, configurable sharding • Migra>ng plugins to take advantage of clustering and support failover • Provide clearer models for building clustered applica>ons
• Based on modern frameworks: node.js, AngularJS
• Completely decoupled from the core controller
• Run it from any loca>on • Modular, easy to extend
ODL Helium: DLUX
ODL Helium: Policy
• Policy is everywhere at them moment • Group-‐based Policy, Congress, Intent, ACI, …
• At least three policy-‐oriented projects in ODL • Service Func>on Chaining • Group-‐based Policy • Network Intent Composi>on
• ODL is ac>ng as a proving ground for policy approaches where engineers and users can play with different approaches
• OpenDaylight exposes a single common OpenStack Service Northbound
• Matches Neutron API precisely • Mul)ple implementa)ons of Neutron in OpenDaylight
• New features in Helium • Distributed L3 forwarding • OpenStack Security Groups • LBaaS implementa>on OpenDaylight
OpenContrail Provider VTN Provider
Neutron Service
OpenStack Neutron
OVSDB Provider
Neutron ML2 MechanismDriver
OpenDaylight APIs (REST)
ODL Helium: OpenStack Integration
Growth from Hydrogen to Helium
23
13 154
291
10,411 total
1.9M lines of code since projects launch
Adoption
Agenda • What is OpenDaylight? • History: Helium • What’s in store for Lithium • Some Personal Learnings • Neutron Integra>on? • Q&A
AAA: Authen>ca>on, Authoriza>on & Accoun>ng ALTO: Applica>on Layer Traffic Op>miza>on AuthN: Authen>ca>on BGP: Border Gateway Protocol CAPWAP: Control and Provisioning of Wireless Access Points COPS: Common Open Policy Service DIDM: Device Iden>fica>on and Driver management DLUX: OpenDaylight User Experience DDoS: Distributed Denial Of Service
DOCSIS: Data Over Cable Service Interface Specifica>on FRM: Forwarding Rules Manager GBP: Group Based Policy IoTDM: Internet of Things Data Broker LACP: Link Aggrega>on Control Protocol LISP: Locator/Iden>fier Separa>on Protocol MAPLE: Maple Programming NIC: Network Intent Proposal OVSDB: Open vSwitch DataBase Protocol OPFLEX: Extensible Policy Protocol
Open vSwitches Addi3onal Virtual & Physical Devices
Topology Processing
DIDM
MD-‐SAL / Yangtools
GBP Service SFC
DOCSIS Abstrac3on
VTN Manager
Plugin20C LISP Service
BGP PCEP OVSDB
OVSDB NETCONF PCMM/COPS SNBI LISP BGP
PCEP SNMP Plugin20C OpenFlow
Neutron Service
SDNI Aggregator
Persistence
L2 Switch
TCP-‐MD5
SXP USC
Discovery IoTDM
IoT
LACP
MAPLE
ALTO
CAPWAP
Reserva3on
TSDR
VPN Service NIC
USC Manager
OPFLEX
Topology Inventory FRM
Network Applica3ons Orchestra3ons and Services
NB APIs
Applica3ons
Plugin Services
Controller plaZorm
SB interfaces & protocols plugins
PCEP: Path Computa>on Element Protocol PCMM: Packet Cable Mul>Media Plugin2OC: Plugin To OpenContrail SDNI: SDN Interface (Cross-‐Controller Federa>on) SFC: Service Func>on Chaining SNBI: Secure Network Bootstrapping Infrastructure SNMP: Simple Network Management Protocol SXP: Source-‐Group Tag eXchange Protocol TSDR: Time Series Data Repository TTP: Table Type Pa\erns USC: Unified Secure Channel VTN: Virtual Tenant Network
Lithium Dependency Graph
Agenda • What is OpenDaylight? • History: Helium • What’s in store for Lithium • Some Personal Learnings • Neutron Integra>on? • Q&A
Key Personal Learning: Open Source is the Modern Way to Develop Non-Differentiated “Plumbing”
• Community building is a core Open Source objective • Both intra and inter project
• Code is the coin of the realm • But don’t forget the importance of testing and integration, documentation, …
Putting this all together à 23
• Engineering systems are as important as artifacts
Implica6on: Engineering ar6facts are no longer the source of sustainable advantage and/or innova6on
• Engineering Systems • Culture • People/Process
Perhaps surprisingly, the “hyper-‐scale” and open source communi>es have taught me that actual ar>facts (in our case network applica>ons as well as HW/SW) are ephemeral en>>es and that the only source of sustainable advantage/innova>on consists of
Bio-‐techno Convergence and The Hidden Nature of Complexity
David Meyer CTO and Chief Scien>st, Brocade
Director, Advanced Technology Center, University of Oregon Network Complexity Research Group
IETF 88 Vancouver, BC
dmm@{brocade.com,uoregon.edu,1-‐4-‐5.net,…}
hcp://www.1-‐4-‐5.net/~dmm/talks/ncrg88.pdf 25
Transformation à
Said Another Way: Open Source has Transformed the Good-Cheap-Fast Development Cycle
26
Fast Fast
Fast
Why? Because you can build Good or Cheap from Fast by using OS Development methodologies and leveraging the OS communities (this is a form of leveraged Investment)
• Transparency ma\ers
• When there are disagreements in the community • Transparency makes everyone feel heard • Transparency makes sure the community does not fracture
• OpenDaylight is transparent to the extreme • Calls, mailing lists, wikis… are open to anyone • Even the technical steering commi\ee calls
Transparency
27
Agenda • What is OpenDaylight? • History: Helium • What’s in store for Lithium • Some Personal Learnings • Neutron Integra>on? • Q&A
Neutron Update • 5+ projects wan>ng to do Neutron integra>on