SDN powers Big Data Network with Analytics and Visualization 用 于 大 数 据 可 视 化 的 SDN 技 术

Transcription

1 SDN powers Big Data Network with Analytics and Visualization 用 于 大 数 据 可 视 化 的 SDN 技 术

2 Agenda SDN Overview Controller Market SDN Application 2

3 SDN Definitions Control Stack Evolution Past IP networks Present IP networks Applications 5 Closed management Tightly integrated stack Open management Tightly integrated stack SDN Networks Business Process/Workflow 4 Network Management Management Plane (CLI, etc) Network Management Management Plane (CLI, etc) Networ k Control Apps Controller Network Mgmt Network and Element Management 3 Control Plane (routing) Control Plane (routing) Open Programming Interfaces 2 Data Plane (packet processing) Data Plane (packet processing) Data Plane (packet processing) Data Plane 1 3

4 SDN Definitions Software Directions Northbound Interface In computer networking and computer architecture, a northbound interface of a component is an interface that conceptualizes the lower level details (e.g., data or functions) used by, or in, the component Examples: SMMP, CORBA, SNMP Southbound Interface Allows a particular network component to communicate with a lower-level component Example: Openflow, Netconf, SNMP East-West Interface Communicate between groups or federations of controllers to synchronize state for high availability 4

5 SDN Definitions Framework SDN Services, Apps Northbound Interface SDN Language App APIs East-west Interface Carriers Infrastructure Information Programmable Control Plane Network OS Southbound Interface Programmable Control Plane Network OS Control and Data Planes Separation Data Plane (Forwarding Hardware) Data Plane (Forwarding Hardware) Data Plane (Forwarding Hardware) Data Plane (Forwarding Hardware) 5

6 Why SDN? Apps vs. Network Applications Network Requirements File Backup App Web App Hadoop Big Data Jobs App Requirements Hard to Express/Enforce Network Admin Help Ticket Phone Call Written docs Or Nothing Yes, No, or Later == No Sufficient bandwidth / ports / devices / uplink? Time to rewrite configs? Impact current apps? Future Apps? Affect provisioning? Network Devices Router Myriad CLI interfaces Emergent behavior Limited control Multitude of Statistics Events Capabilities Host X Switch Firewal l Switch Backup Server Y 6

7 Why SDN? Express/Enforce Requirements via API Applications 1 App s Explicit Requirements File Backup App Network Statistics, Hints, and Events Opportunity to Standardize Network Controller and Network Admin 2 Network Controller Provides network stats up to Apps Translates requirements down to Devices Configures Network Policy Monitors Performance Network Devices 3 Host X Switch Router Firewal l Switch Backup Server Y Standardized API/Protocol Enforced Behavior Low-level Control Capability Discovery Statistics and Faults 7

8 Agenda SDN Overview Controller Market SDN Application 8

9 OpenDaylight SDN Platform Open Source Linux Foundation Collaboration Software Defined Networking Network Function Virtualization Innovation 9

10 SDN, NFV and OpenDaylight New Revenue Service Agility Open, Programmable APIs Orchestration, Automation and MANO SDN NFV Virtualization and Abstraction Layer Lower Cost 10

11 OpenDaylight compared with OpenStack Level of Programmability Python Python REST Scripting CLI OpenDaylight Neutron OpenStack Puppet (Puppet Labs) Chef (Opscode) Network Element Network IT Infrastructure Scope of Domain 11

12 Why Open Source? Flexibility Innovation Choice Control Faster, lower cost and higher quality development through sharing of resources via collaboration Community decisions about new features and roadmaps A common environment for uses and App developers Ability to focus resources on differentiating development 12

13 Controller Market Overview Linux Foundation an open source SDN controller Members: Cisco, IBM, BigSwitch, Brocade, Juniper, Microsoft, Citrix, NEC, HP. Origination, March 2013: Cisco ONE/onePK for the Service Abstraction Layer (SAL) Beacon (OpenFlowJ) API for OpenFlow Applications by NEC, IBM, and others 13

14 OpenDayLight Momentum Building OpenDaylight becomes the clear choice for the industry Gigaom Research (April 2014)* 95% of those surveyed want open source in their SDN solution 76% of those surveyed prefer a commercial supplier for their open source-based product Growth in total Membership 18 to 39 members since launch (2 more in September) Developer growth to over 200 developers Growth in number of projects From 14 to 25 Press mentions - over 3000 stories this year and 2.7 million keyword impressions Companies who ve announced ODL based products 10 The platform has over 1.7 million lines of code *Gigaom Research: The report surveyed 600 IT decision makers and technologists in medium to large organizations within enterprise (300) and service provider (300) organizations in North America. 14

15 Continuous Growth to 39 Members 15

16 The OpenDaylight Project THE LINUX FOUNDATION S OPENSOURCE CONTROL PLANE FOR SDN AND NFV OpenDaylight is a widely supported framework for SDN and NFV control Supporting vendors include: Brocade, Cisco, IBM, Arista, Juniper, Ciena, Hewlett Packard, NEC, VMWare, Huawei and many others Important Features of the OpenDaylight Framework: Standardized REST API (northbound) for application developers Standard and vendor-specific plugins (southbound) allow a wide range of switch and router supplier options Service abstraction infrastructure simplifies network complexity and allows SW developers to focus on business logic rather than proprietary vendor interfaces. 1 6

17 Controller Market Overview OpenDaylight framework: 17

18 The Service Abstraction Layer - SAL Exposes device services that are managed by the APP modules at a higher layer Determines how to fulfill the requests from northbound APPs, irrespective of the underlying protocol (southbound interface) Underlying protocols that connect to the devices can be OpenFlow (1.0, 1.3), BGP-LS, Netconf, OVSDB, SNMP, etc. 18

19 The Service Abstraction Layer - SAL Two flavors of SAL: AD-SAL MD-SAL AD-SAL: API Driven SAL Stateless Limited to flow-capable devices and service models only MD-SAL: Model Driven SAL Can store date for models defined by plugins Model agnostic can support any device and/or service model 19

20 Controller Market Overview Players: Open source, established vendors, start-ups Technology Silicon Switches Routers Vendor Broadcom, Ezchip, Intel Arista, Brocade, Cisco, Dell, HP, IBM, Juniper, Mellanox, NEC, Pica8, Cumulus, Big Switch Cisco, Juniper, Huawei, Brocade Vyatta L4-7 6wind, Embrane, F5 Controllers (OpenDaylight) Controllers (Pre- OpenDaylight) Virtualization Orchestration and Automation Cisco APIC-EM, Brocade, Inocybe, Extreme Cisco APIC, XNC, Juniper, HP, Nuage, NEC VMware, Contextream, Midokura Anuta, Lyattis, Plexxi 20

21 Controller Market Overview COMPANY BigSwitch Cisco HP IBM Juniper NEC NTT Data Pica8 Plexxi Inc. SDN CONTROLLER Floodlight-Based APIC (App Policy Infrastructure Controller), APIC-EM, XNC, onepk VAN SDN Controller (Announced moving to ODL) IBM Programmable Network Controller, Dove Contrail Controller, Open Contrail NEC ProgrammableFlow Controller NTT Virtual Network Controller Pica8 Integrated Open OVS Switch & Controller Plexxi Control OpenDaylight OpenDaylight (Hydrogen, Helium (Oct 2014)) Huawei SNC Midokura MidoNet 21

22 Agenda SDN Overview Controller Market SDN Application 22

23 OpenDaylight Controller Use Cases SOFTWARE THAT CONNECTS THE NETWORK TO YOUR BUSINESS PROCESSES Custom Analytics and Compliance Big Data Security QoS and Traffic Management Service Configuratio n and Policy Research and New Protocols Fault and Disaster Recovery WAN Optimization 23

24 A New Network Architecture Software Defined Networking Centralizes the Control Plane Northbound API Vendor Specific Management Captive Control Plane Vendor A EMS/NMS CLI/API Vendor B EMS/NMS CLI/API Vendor C EMS/NMS CLI/API Open Source SDN Controller Industry Standard Control Protocols Standard Modeling Language Industry Standard Protocols Vendor A Vendor B Vendor C EMS, NMS, CLI and APIs specific to the switch or router vendor Proprietary control plane per device Communication protocols standardized for interoperability Centralized open control plane, non-vendor specific Normalized programming interface Standard control protocols and modeling language 24

25 YANG Model Development and Standardization Open Daylight IETF IETF Working Groups RESTCONF / NETCONF Open Source Community YANG GitHub Channel YANG Models AUTO-Generated API YANG Tools Model-Driven MD-SAL Manually Generated API Abstract-Driven AD-SAL RFC Process Standardized YANG Models Vendor-Proprietary Yang Models 25

26 Netconf and YANG Data Models and Protocols: Example: Protocol SNMP Data model MIBS 26

27 PATHS model Paths modeling depends on the: Modeling of the nodes (hosts and switches) Modeling of the link topology or physical network Modeling of flows on switches. Uses (Layered upon): Hosts Switches Link Topology (as discovered by LLDP) Flows (implemented through the OpenFlow pluggin) Adds: sourceip, destinationip "path" including "waypoints" CRUD of Path model derives CRUD of flows 27

28 Big Data Analytics is comprised of two components: Big Data Data Analytics Defined by: Volume, Velocity, Variety The Process of: Discovery and communication of meaningful patterns in data

29 Why Analytics? Improve network robustness and performance VXLAN Monitoring and Troubleshooting L2-L4 DDOS Mitigation Service and User Accounting Network Anomaly Detection Firewall Bypass 29

30 3 0 Network Requirements for Big Data High Performance with Low Latency Large data transfers and high I/O counts require a high throughput and low latency network and optimized for east/west traffic patterns Scale-out Fabrics Greenplum MPP architecture requires a network with a large number of 10 GbE ports and an architecture that can quickly scale-out to add capacity Operational Simplicity The network must be automated, with self-forming fabric, plug-and-play configuration, and entire fabric managed as a single logical switch Non-stop Networking Downtime must be minimized by adding or modifying links quickly and non-disruptively with rapid convergence time, and with no manual configuration

31 VXLAN and NVGRE Monitoring ( Heat Map ) High performance VXLAN/NVGRE aware DC core and border WAN/ Internet sflow Analyzer Aggregation Transit Monitoring VXLAN and NVGRE sflow extension Path information Troubleshooting Flex Match DC Network Operators are running blind with no VXLAN/NVGRE visibility at physical Core/Interconnect Data Center Tenant A Tenant B 31

32 SDN based Accounting and Management Improve network utilization and reliability; Innovate services sflow Analyzer Per-app Statistics sflow samples OpenFlow port Normal Routing port OpenFlow Hybrid port WAN or Campus network (OSPF, BGP) OpenFlow 1.3 Pipeline Normal Forwarding Pipeline WAN or Campus network WAN (OSPF, or DC BGP) network ISP, DC, Campus Differentiation: Per-flow In-line large scale (128k flows) OpenFlow 1.3: Match, Meter, Drop, Remark Normal Forwarding: L2, L3 and MPLS No impact to original routing or switching Use cases Internet/Mobile traffic analysis: Facebook, Youtube, Netflix, Business/Residential Customer Internet Accounting/Intelligence Campus Visibility, Accounting and Traffic Management Big Data analysis Troubleshooting analysis 32

33 Science DMZ For Research Institutions and Universities Customer Challenge The Solution Solution Benefits Firewall is a choke point for elephant flows Overall performance degradation Requiring manual input for configuration changes can t scale, especially under peak demand Selectively bypass FW automatically for trusted users Internet2 Science DMZ application Sunshine controller Openflow switch and Router Automation for scaling existing processes Big performance gain for trusted users; eases constraints on FWs, up to 100GE Uses existing security and NW infrastructure Uses standards-based API and protocols 33

34 SDN Science-DMZ Demo Firewall Bypass Example Traffic Analytics App (TAA) White-List Flow parameters Traffic Management App (TMA) OpenFlow port Normal Routing port OpenFlow Hybrid port DMZ Router/Switch Processed data sflow sampled packets 100G WAN Link Raw data HPC/Science High Volume Flows Firewalled Traffic HPC/Science LAN Campus network Improves 100G performance by 2x for legitimate flows 250ms - double throughput of firewall path 1.5sec - same throughput as NO firewall 34

35 Volumetric Attack Mitigation Value proposition: Less expensive, Easy out-of-the-box install Customer Portal TS App sflow Analyzer 1. Data Center Devices Send sflow samples to the collector sflow Analyzer Open Daylight Controller 4 Analyze and report Volumetric Flow trigger 3. Traffic steering application with policy based UI and REST APIs Instruct controller to redirect volumetric flows 4. OpenDayLight Controller S-Flow Samples Ethernet VLAN, VXLAN IPv4/v6, NVGRE MPLS Network 1 Program OpenFlow 1.3 rules in openflow router and switch 35

36 Controller Cluster Load Balancing (LB) Target: Telco Provider, Cloud Service Provider Customer Challenge The Solution Solution Benefits Even traffic distribution Processing computationally intense operation like SSL Operational overhead for configuring multiple controllers IP addresses towards end points and applications OpenFlow LB from network to controller domain REST (Northbound API) connection LB from applications to controller domain Content based LB (ex: PUT request directed to lead of shard) Request validation (ex: HTTP methods/browser filtering) TLS offload for OpenFlow and REST connections Enables controller clustering for fault tolerance and scalability Ensures even load distribution across controllers Increases network and controller scale by offloading encryption processing Simplifies controller operation 36

37 Drag and Drop Flow Modification For Any Customer Using ANY OF 1.0 and 1.3 compliant switch Customer Challenge The Solution Solution Benefits Understanding and visualizing network traffic flows Difficulty in modifying traffic flows Manual insertion of new network services Dynamic flow interaction through an intuitive GUI OpenDaylight controller Any OpenFlow compliant switch Easy to view topology and traffic flows Intuitive traffic flow modification Easy to understand system response Rapid service insertion 37

38 Drag and Drop Flow Modification The pendaylight Controller includes a topology display and GUI objects for network flows. For any device controlled by ODL using OpenFlow 1.3, the GUI includes an end-point on the flow that can be dragged and snapped to any network element. Data Center VDX OpenDaylight Controller - Drag and Drop Flows GUI penflow switch Openflow switch Openflow switch 38

39 Controller Cluster Load Balancing (LB) Applications by Controll er Instance Controll er Instance Controll er Instance The OpenDaylight Controller is designed in a cluster for increased performance and reliability Controll er Instance HA vadx enhances SDN operations: OpenFlow load balancing Northbound API load balancing TLS offload for encrypted traffic NETWORK SWITCHES 39

40 SDN-Based Adaptive and Automated QoS Application detects voice/video delays, dynamically requests prioritization Lync Server ICX ICX ICX ICX OpenFlow 1.3 ICX ICX ICX ICX ICX ICX ICX ICX Lync Plug-in Controller Solution Fully automated and adaptive call admission and control Single trusted source of QoS management Eliminates the need to QoS tag at the switch port level Dynamic replacement of manual switch-by-switch provisioning of static QoS policies Lync Client Lync Client 12/19/

41 Thanks