1 / 172

Okinawa open laboratory First hand on seminar OpenDaylight edition

Okinawa open laboratory First hand on seminar OpenDaylight edition. Satoshi Hieda Takahiro Oshima. July 29 , 2014. Agenda. Part 1: OpenDaylight Introduction to OpenDaylight project Introduction to OpenDaylight Hydrogen OpenDaylight hands on Break

macon
Télécharger la présentation

Okinawa open laboratory First hand on seminar OpenDaylight edition

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Okinawa open laboratoryFirst hand on seminarOpenDaylight edition Satoshi Hieda Takahiro Oshima July 29, 2014

  2. Agenda Part 1: OpenDaylight • Introduction to OpenDaylight project • Introduction to OpenDaylight Hydrogen • OpenDaylight hands on • Break Part 2: VTN (Virtual Tenant Network) • Introduction to VTN • VTN hands on • Practice problems

  3. Part 1: OpenDaylight

  4. Introduction to OpenDaylight project

  5. SDN (Software Defined Networking) • Separate network control and data forwarding • Make network control programmable SDN Current network application API control control control Control/Data planeInterface forwarding forwarding forwarding control control forwarding forwarding

  6. OpenDaylight project • Part of Linux Foundation Collaborative Project • Main activities • SDN controller development • Develop SDN controller for commercial use from the development resources committed by participating vendors. • Make it Open source • Offer SDN controller as OSS to a wide range of users and vendors • Promote SDN market • Accelerate the rise of SDN market and promote its commercial use with the above activities.

  7. Multi-vendor • Participation of both network vendors and IT vendors. • 39 vendors at present. The participants are increasing. (from http://www.opendaylight.org/project/members, as of 7/19)

  8. Multi-project • Project proposal by many participants/vendors • There are 25 projects at present. • OpFlex Implementation Project • OVSDB Open vSwitch Database Integration Project • OSCP Project • PacketCable PCMM Project • Secure Network Bootstrapping Infrastructure (SNBI) project • Service Function Chaining • SNMP4SDN • Table Type Patterns (TTPs)/Negotiable Datapath Models (NDMs) • Toolkit Project • Virtual Tenant Network (VTN) • YANG Tools • AAA Service • Affinity Metadata Service • BGP-LS/PCEP • Controller • dlux - openDayLight User eXperience • Documentation Project • Defense4All • Dynamic Resource Reservation • Group Policy Plugin Project • Integration Group • LISP Flow Mapping • Open DOVE • OpenFlowPlugin • OpenFlow Protocol Library (from https://wiki.opendaylight.org/view/Main_Page, as of 7/19)

  9. Open community • Vendor neutral • Only vendor neutral projects can be proposed • Check by TSC in creation review of project • Governance • Board: Collegiate system with focus on Platinum member. • TSC: Committer elected by Core project representative (focus is on Platinum member for now because it is just after the inauguration) • Contents of discussion have been published on Internet • TSC: Technical Steering Committee. Organization controlling • the overall design/development of OpenDaylight

  10. Introduction to OpenDaylight Hydrogen

  11. OpenDaylight Hydrogen • SDN controller released in February, 2014 • First OpenDaylight release • License: Eclipse Public License • Three release edition • Base Edition • Basic features only • For SDN, OpenFlow investigation • Virtualization Edition • Base Edition + virtualization • For data centers • Service Provider Edition • Base Edition + multiple protocol support • For providers, carriers Eclipse Public License(EPL) The receiver of EPL-licensed programs can use, modify, copy and distribute the work and modified versions. However, certain obligations are attributed to the distribution of the modified version, like revealing the method to acquire the source code. (from http://ja.wikipedia.org/wiki/Eclipse_Public_License)

  12. Code volume • Rapid increase in short period of time after OpenDaylight inauguration(May, 2013) • Many contribution of existing code as well Hydrogen release (total: 1.5ML, code: 1.0ML) OpenDaylight 発足 (from http://www.ohloh.net/p/opendaylight)

  13. Adoption • Announcement of products with OpenDaylight base • Cisco: XNC (Extensible Network Controller) • One PK, OpenFlow 1.0 support • IBM: SDN VE (Software Defined Network for Virtual Environment) • Adopt same technology as OpenDOVE • PoC of OpenDaylight starts in Deutsche Telekom, Italtel etc. • Ericsson launches laboratory for validation

  14. Community • Many vendor-led projects • Depending on the project, committers are limited to one company • Non vendor-led projects are also increasing • University of Kentucky, ITRI, ... • Community is diversifying • Projects with multiple vendor participation • Integration between projects

  15. Community • Contributors: 154(as of February,2014) (Reference: OpenStack 1974, Floodlight 52) Commit count Line count (from http://events.linuxfoundation.org/sites/events/files/slides/OpenDaylight-Year1%20v4-ext.pdf )

  16. Projects in the Hydrogen Release (From https://wiki.opendaylight.org/images/2/24/ODL_2013.11-IETF-final.pptx)

  17. (From OpenDaylight_Briefing_Deck_06.30.14.ppt http://bit.ly/ZPgDut)

  18. OpenDaylight Hydrogen Base Edition

  19. (From http://www.opendaylight.org/software/base-edition )

  20. OpenDaylightController • Framework of SDN controller • Constitutes of OSGi Framework + bundle • Major features • Base Network Service Function • Bundle the basic controller features and offer it as REST API • Topology Manager, Stats Manager, Switch Manager, ... • SAL (Service Abstraction Layer) • HA, Clustering • Northbound API • GUI

  21. SAL • Abstraction layer between Controller Platformand Protocol Plugin • Control data sharing, request calls etc. • Two types of SAL are defined • AD-SAL (API-Driven SAL) • MD-SAL (Model-Driven SAL) • Supported SAL differs based on Plugin

  22. AD-SAL • SAL defines the service APIs offered to upper layers • Higher applications use SB Plugin via service API • Degree of support provided for service APIs differ based on SB Plugin, and it is necessary to be aware of the return code AD-SAL (From https://wiki.opendaylight.org/view/OpenDaylight_Controller:AD-SAL )

  23. MD-SAL • Java bindings(API/Plugin) are created via YANG Tools, based on the data model defined in YANG (From https://wiki.opendaylight.org/images/7/78/ONF_NBI_Leadership_Roundtable_Presentation_-_ODL.pptx )

  24. MD-SAL • Application and SB plugin operate model data, and execute request (RPC) and notification via the generatedJava bindings (From https://wiki.opendaylight.org/images/e/e3/Os2014-md-sal-tutorial.pdf )

  25. OpenFlow Plugin & Protocol Library • OpenFlowPlugin • Protocol plugin that controls OpenFlow switch • Supports OF 1.0, 1.3.x • OpenFlow Protocol Library • Library for transmitting and receiving OpenFlow protocol data (From https://wiki.opendaylight.org/view/File:Openflow_Protocol_Library.pdf )

  26. YANG Tools • Tools and libraries to configure network devices by using NETCONFand YANG • Generates Java binding from model described in YANG • Service module of MD-SAL can be easily created from YANG model

  27. OpenDaylight Hydrogen Virtualization Edition

  28. (From http://www.opendaylight.org/software/virtualization-edition )

  29. VTN • Virtualization technology that realizes a multi tenant that spans across multiple SDN controllers • Offers VTN APIfor higher applications to control the virtual network • Refer details in Part 2VTN!

  30. OVSDB • OVS(Open vSwitch) configuration and management features via OVSDB • Offers features for OVS like creation of bridge, port etc., modification of settings, deletion, information retrieval and tunnel control • Possible to integrate with OpenStack (From http://www.1-4-5.net/~dmm/talks/OpenDaylight_SDN_Workshop_AZ.pdf )

  31. OpenDOVE • Virtualization technology with overlay technology (VxLAN) • Tenants can connect with each other on L2 and L3(ACL control) • Has a gateway feature with the existing physical network • Integrates with OpenStack (From https://wiki.opendaylight.org/view/Open_DOVE:Proposal )

  32. Affinity Metadata Service • Metadata to realize network model • This service does not look into how metadata is expressed as config and flow entry (From https://wiki.opendaylight.org/view/Project_Proposals:Affinity_Metadata_Service )

  33. Defence4All • Feature to control detection and defense for DDoS attacks • When a DDoS attack is detected, it mitigates the attack by directing target flows to mitigation systems (From https://wiki.opendaylight.org/view/Project_Proposals:Defense4All )

  34. OpenStack Service • Supported projects • VTN,OVSDB,OpenDOVE • Resources • Resources used differs for different projects • Offers one northbound for the controller • Plugin individual implementations of each project under it VTN Provider VTN Provider DOVE Provider DOVE Provider OVSDB Provider overlay hop by hop overlay (From http://www.1-4-5.net/~dmm/talks/OpenDaylight_SDN_Workshop_AZ.pdf )

  35. OpenDaylight Hydrogen Service Provider Edition

  36. (From http://www.opendaylight.org/software/service-provider-edition )

  37. LISP, BGP, PCEP, SNMP • LISP Mapping Service • Controls network devices that support LISP • Offers mapping feature between EID/Locator of LISP • BGP-LS/PCEP • Controls network devices that support BGP-LSand PCEP • Allows topology detection via BGP-LS and path programming via PCEP • SNMP4SDN • Controls network devices via SNMP

  38. Conclusion

  39. Future of OpenDaylight • OpenDaylight Helium (incoming SDNcontroller) • Under development, release planned for September 29 • Projects that plan to participate (25 projects) • AAA Service • BGPCEP • Controller • dLux • Defense4All • Docs • Group Based Policy • Integration Group • L2 Switch • Lisp Flow Mapping Service • ODL-SDNi App • OpenFlow Plugin • Openflow Protocol Library • OpFlex protocol Agent • OVSDB • PacketCablePCMM • Secure Network Bootstrapping Infrastructure • Service Function Chaining • Southbound plugin to the OpenContrail platform • Reservation • SNMP4SDN • Table Type Patterns • Toolkit • VTN Project • YANG Tools

  40. Conclusion • We now have an overview of OpenDaylight project and OpenDaylight Hydrogen • For those who are interested in the projects, please refer this page! https://wiki.opendaylight.org/view/Main_Page

  41. OpenFlowoverview

  42. Status of OpenFlow OpenDaylight Controller Architecture One of the protocols supported by OpenDaylight (Southbound Interface)

  43. OF1.0 Basic overview of OpenFlow (version 1.0) • Controller enters the rules for packet processing into the switch tables.Switch will process the packets based on this table information.=Separating control and forwarding features • OpenFlow specification defines - message format between controller and switch - necessary switch capabilities

  44. OpenFlow utilization (Overlay or Hop-by-hop) • Overlay technology • Hop-by-hop technology OF OF OF OF Legacy OF OF OF OF OF OF • OpenFlowin its entirety • Replacesexisting network devices • Central management of core NW is possible→ Visualize physical path→ Traffic path control is easy • OpenFlow in edge only • Maintains existing network devices • Central management of core NW is not possible→ Cannot visualize physical path→ Traffic path control is difficult

  45. Traffic path controlspecifically, such things are possible ■ Sophistication of traffic path control with Open flow Effective use of network bandwidth by path control of each flow (multi-path) ② Improvement in network device maintainability by moving flows to one side ③ Place network appliances like Firewall, Load balancer etc. between thepath and allow passage of specific flows (WayPoint feature) OpenFlow controller ① OpenFlow switch Flow 1 Flow 2 App 1 App 1 App 2 App 2 Server ①

  46. Traffic path controlspecifically, such things are possible ■ Sophistication of traffic path control with Open flow Effective use of network bandwidth by path control of each flow (multi-path) ② Improvement in network device maintainability by moving flows to one side ③ Place network appliances like Firewall, Load balancer etc. between thepath and allow passage of specific flows (WayPoint feature) OpenFlow controller OpenFlow switch Flow 1 Flow 2 App 1 App 1 ②Move flows to one side App 2 App 2 Server ②Maintenance possible

  47. LB FW • Traffic path controlspecifically, such things are possible ■ Sophistication of traffic path control with Open flow Effective use of network bandwidth by path control of each flow (multi-path) ② Improvement in network device maintainability by moving flows to one side ③ Place network appliances like Firewall, Load balancer etc. between thepath and allow passage of specific flows (WayPoint feature) OpenFlow controller OpenFlow switch Flow 1 Flow 2 App 1 App 1 App 2 App 2 Server Firewall Load balancer ③

  48. OF1.0 Packet header fields used inMatch conditions Uses total of twelve header fields as Match conditions from L1 toL4 [Conventional network devices] Controls forwarding to individual network devices according to destination address of L2/L3 layers L2 (MAC) switching L3 (IP) routing (Firewall etc.) Ingress Port Dst MAC Src MAC Ether Type VLAN id VLAN Priority Dst IP Src IP IP Proto IP ToS TCP/UDP SrcPort TCP/UDP Dst Port Data Ｌ１ Ｌ２ Ｌ３ Ｌ４ [What happens in OpenFlow?] Distinguish communication traffic withany combination ofaddress/ identifier in each of the L1(physical port etc.）, L2(MAC), L3(IP) and L4(port number) layers and define actions accordingly for more flexible control.

  49. OF1.0 Action for each flow(Action) • As Action, it is possible to update packet header (Modify-Field), output to specified port (OUTPUT) or add to specified queue(ENQUEUE). • Drop action is performed if action is not specified

  50. OpenDaylight hands on

More Related