Introduction to OpenDaylight: Current Events and OpenStack Neutron Integration

Transcription

1 Introduction to OpenDaylight: Current Events and OpenStack Neutron Integration David Meyer Chief Scientist and SP Research of Oregon Chair of the OpenDaylight Board of Directors uoregon.edu, net,.} Note: This deck contains slides courtesy Colin Dixon and a cast of 1000s

2 Agenda What is OpenDaylight? History: Helium What s in store for Lithium Some Personal Learnings Neutron Integra>on? Q&A

3 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.

4 Who is OpenDaylight?

5 Who is OpenDaylight? (Really) Like any Open Source Project, OpenDaylight primarily consists of those who show up to do the work. Running around 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 Source: 5

6 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

7 Aside: Release Naming 7

8 8 Brief Note on Project Lifecycles

9 Agenda What is OpenDaylight? History: Helium What s in store for Lithium Some Personal Learnings Neutron Integra>on? Q&A

10 HELIUM Legend 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 VTN Coordinator DDoS Protec3on SDNI Wrapper DLUX OpenStack (via Neutron) Network Applica3ons Orchestra3ons & Services Custom Basic AuthN Filter AD- SAL REST APIs AAA AuthN Filter MD- SAL RESTCONF (REST) APIs Neutron AuthN Neutron APIs Base Network Service Func3ons OpenStack Neutron Service Topology Manager Stats Manager Switch Manager Fwding Rules Mgr Host Tracker DOCSIS Service LISP Service SDNI Aggregato r Service Flow Chaining GBP Service L2 Switch OVSD B VTN Plugin20C Controller PlaZorm API- Driven Service Abstrac3on Layer (AD- SAL) Clustering Model- Driven Service Abstrac3on Layer (MD- SAL) Service Abstrac3on Layer (Common models, APIs, etc.) OpenFlow PCMM/ SNBI OVSDB SNMP LISP BGP PCEP 1.0 COPS NETCONF OpenFlow TTP Plugin20C Southbound Interfaces & Protocol Plugins OpenFlow Enabled Devices Open vswitches Addi3onal Virtual & Physical Devices Data Plane Elements (Virtual Switches, Physical Device Interfaces)

11 ODL Helium: Karaf Java chosen as an enterprise- grade, cross- plagorm compa>ble language Java Interfaces are used for event listening, specifica>ons and forming pa\erns Maven build system for Java OSGi: Allows dynamically loading bundles Allows registering dependencies and services exported For exchanging informa>on across bundles Karaf: Light- weight Run>me for loading modules/bundles OSGi based. Primary distribu>on mechanism for Helium FeatureA FeatureB SAL Karaf OSGi Framework (Equinox) 11

12 ODL Helium: Karaf $ wget integration/distribution-karaf/0.2.0-helium/distribution-karaf Helium.zip $ unzip distribution-karaf helium.zip $ cd distribution-karaf helium $./bin/karaf opendaylight-user@root> feature:list (get all apps available) opendaylight-user@root> feature:install odl-dlux-core opendaylight-user@root> feature:install odl-openflowplugin-all opendaylight-user@root> feature:install odl-l2switch-all opendaylight-user@root> bundle:list grep Active Now your controller is ready to connect to switches and handle incoming flows.

13 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

14 ODL Helium: DLUX Based on modern frameworks: node.js, AngularJS Completely decoupled from the core controller Run it from any loca>on Modular, easy to extend

15 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

16 ODL Helium: OpenStack Integration OpenStack Neutron Neutron ML2 MechanismDriver OpenDaylight APIs (REST) OpenDaylight exposes a single common OpenStack Service Northbound Matches Neutron API precisely Mul)ple implementa)ons of Neutron in OpenDaylight Neutron Service VTN Provider OpenDaylight OpenContrail Provider OVSDB Provider New features in Helium Distributed L3 forwarding OpenStack Security Groups LBaaS implementa>on

17 Growth from Hydrogen to Helium M lines of code since projects launch ,411 total

18 Adoption

19 Agenda What is OpenDaylight? History: Helium What s in store for Lithium Some Personal Learnings Neutron Integra>on? Q&A

20 LITHIUM DLUX DDoS Protec3on OpenStack Neutron Legend 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 SDNI Wrapper 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 VTN Coordinator 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 Network Applica3ons Orchestra3ons and Services Topology Inventory FRM AAA- AuthN Filter OpenDaylight APIs (REST) NB APIs ALTO DIDM GBP Service SFC SDNI Aggregator L2 Switch VTN Manager Neutron Service NIC Reserva3on VPN Service Applica3ons MAPLE Topology Processing Discovery DOCSIS Abstrac3on BGP PCEP Plugin20C TCP- MD5 OVSDB LISP Service IoTDM USC Manager LACP Plugin Services MD- SAL / Yangtools Persistence TSDR Controller plazorm OpenFlow NETCONF SNBI PCMM/ COPS BGP PCEP Plugin20C SNMP OVSDB LISP IoT USC CAPWAP SXP OPFLEX SB interfaces & protocols plugins OpenFlow Enabled Devices Open vswitches Addi3onal Virtual & Physical Devices

21 Lithium Dependency Graph

22 Agenda What is OpenDaylight? History: Helium What s in store for Lithium Some Personal Learnings Neutron Integra>on? Q&A

23 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, Engineering systems are as important as artifacts Putting this all together à 23

24 Implica6on: Engineering ar6facts are no longer the source of sustainable advantage and/or innova6on 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 Engineering Systems Culture People/Process 24

25 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 5.net, } hcp:// 5.net/~dmm/talks/ncrg88.pdf 25

26 Said Another Way: Open Source has Transformed the Good- Cheap-Fast Development Cycle 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) Fast Transformation à Fast Fast 26

27 Transparency 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 27

28 Agenda What is OpenDaylight? History: Helium What s in store for Lithium Some Personal Learnings Neutron Integra>on? Q&A

29 Neutron Update 5+ projects wan>ng to do Neutron integra>on Includes VTN, Dove, GBP, OVSDB, LISP Flow Mapping, VPN Service, What s missing? Clearly need an abstrac>on for projects wan>ng to use Neutron

30 Neutron-ODL Stack Evolution -- Proposal Current World Near Future Lithium Release? Long-Term Strategy Possible Future API Layers OpenStack Neutron (REST) Major needed work: 1.) Factor apart two halves of the OVSDB project network virt. layer and OVSDB library. 2.) Migrate network virt. layer to use the MD-SAL. 3.) Turn OVSDB protocol library into a plugin not just a library. OpenStack Neutron (REST) REST/YANG Adapter OpenStack Neutron (REST) REST/YANG Adapter OpenStack Neutron (REST) REST/YANG Adapter OpenStack Neutron (REST) REST/YANG Adapter 4.) Migrate OVSDB protocol plugin to use the MD-SAL. Neutron (YANG) Neutron (YANG) Neutron (YANG) Neutron (YANG) OVSDB This project is a monolithic combination of: (1) a network virtualization layer that is hard-wired to Neutron above and OVS below as well as (2) an OVSDB protocol library. 5.) Close feature gap between network virt. layer and OVS OS plugin, e.g., FWaaS, VPNaaS. 6.) Test/improve scale, stability, and performance of the stack. 7.) Migrate network virt. layer s NB API from Neutron (REST) to Neutron (YANG) to Policy/Intent. 8.) Migrate network virt. layer s SB APIs from OVS-specific to tunnel management and traffic direction (into tunnels). $(NEW NAME FOR OVSDB NETVIRT) Network virtualization layer that is still hard-wired to Neutron above, but now uses more general APIs below. Tunnel Mgmt Traffic Direction Neutron ODL Policy Adapter App Higher-Level Network Virtualization API App $(NEW NAME FOR OVSDB NETVIRT) Network virtualization layer that now uses the more general APIs above and below. Tunnel Mgmt Traffic Direction Neutron ODL Policy Adapter App Higher-Level Network Virtualization API Tunnel Mgmt, Traffic Dir, Flow Prgmming, etc App Various new drivers/providers and layering over time as we learn what makes sense Neutron ODL Policy Adapter App Higher-Level Network Virtualization API Generic Overlay Network??? Tnnl Mgmt?????? Tunnel Mgmt, Traffic Dir, Flow Prgmming, etc App OVSDB Plugin NETCONF If developers show up to help OpenFlow +Nicira Extns? OVSDB Plugin NETCONF OpenFlow +Nicira Extns? OVSDB NETCONF SNMP OpenFlow +Nicira Extns? OVSDB NETCONF SNMP OpenFlow +Nicira Extns? OpenFlow + OVSDB + Nicira Extensions Relevant Southbound Protocol Relevant Southbound Protocol Relevant Southbound Protocol Relevant Southbound Protocol OVS Many h/w- and v-switches Many h/w- and v-switches Many h/w- and v-switches Many h/w- and v-switches Slide courtesy Chris Wright and Colin Dixon

31 Quasi-technical things we re working on (necessarily incomplete list) Con>nue to build/refine our community Including increasing commi\er diversity within and across the projects Code Quality and Coverage Stability, Security, Performance, Bug fixes ($Major.$Minor) Distributed Systems Issues S3P Stability, Scalability, Security, and Performance Staffing Release engineering Tes>ng and Integra>on Documenta>on Con>nue to refine our engineering systems Thanks Linux Founda>on! 31 We need more code that writes code MD- SAL is an example Fewer humans in the loop More automa>on more be\er

32 Agenda What is OpenDaylight? History: Helium What s in store for Lithium Some Personal Learnings Neutron Integra>on? Q&A

33 Get Involved! Pull code and try it out TSC weekly calls open to everyone Keep informed and join the conversation IRC: #opendaylight on irc.freenode.net lists.opendaylight.org Twitter: #OpenDaylight 33

34 Q&A Thanks!