DECODING SOFTWARE DEFINED NETWORKS

Transcription

1 DECODING SOFTWARE DEFINED NETWORKS Emil Gągała 10th PLNOG,

2 AGENDA What s it? Architecture Use Cases Transition Summary 3 Copyright 2012 Juniper Networks, Inc.

3 SOFTWARE DEFINED NETWORKING / SDN SDN is an emerging network architecture where network control is decoupled from forwarding and is directly programmable. 4 Copyright 2012 Juniper Networks, Inc.

4 GARTNER HYPE CYCLE Visibility? SDN? IP tracking and docketing systems Time Technology Trigger Peak of Inflated Expectations Trough of Disillusionment Slope of Enlightenment Plateau of Productivity 5 Copyright 2012 Juniper Networks, Inc.

5 THE 7 MYTHS OF SDN Myth: Myth: Myth: Myth: Myth: Myth: Myth: It s only about datacenter networking It s only about reducing CAPEX It s only about software It s only about centralization It s only about OpenFlow It s going to happen immediately It s going to take forever 6 Copyright 2012 Juniper Networks, Inc.

6 CUSTOMER MOTIVATIONS Surveyed IT Professionals: 9% believe they have SDN in production or testing 42% believe SDN will boost network utilization and efficiency 35% believe SDN will automate more provisioning and management 32% believe SDN will improve security Service provider history of application integration Enterprise track record for controllers WLC NAC Can the new technologies address both problems? 7 Copyright 2012 Juniper Networks, Inc.

7 WHY DO WE NEED OPEN PROGRAMMABLE NETWORKS 2010 Juniper Networks, Inc.

8 WHAT IS THE REAL PROBLEM? THE DEVELOPER THE NETWORK Application World Network World Divide has existed forever Impacts everyone Applications guess and probe Networks derive and spy How to change the situation? Need interfaces to influence network behavior and get information Reality: too few, requiring too much integration Do we understand each other - What language are we using? Network terminology: Bandwidth, latency, jitter, quality of service Reality: application developers don t (want to) know which of these is important or impacting their application 10 Copyright 2012 Juniper Networks, Inc.

9 CURRENT APPROXIMATION TECHNIQUES ARE BARELY SUFFICIENT APPLICATION WORLD: GUESSING NETWORK WORLD: DERIVING Applications blindly probe the network to understand what it can deliver Networks spy on traffic to try to understand applications? Network Aware Applications?? Application Aware Networking? Game ping-stats, doppler, geolocation, whois Proprietary codecs Approximate topology/location Deep Packet Inspection Stateful flow analysis Application fingerprinting Service specific overlay topologies 11 Copyright 2012 Juniper Networks, Inc.

10 WHAT DOES THE IDEAL WORLD LOOK LIKE? End-user Application Network Content Application World Network World Where we are going Bringing together the important players to enable interaction and influence the experience of the end user 12 Copyright 2012 Juniper Networks, Inc.

11 BRIDGE APPLICATION NETWORK DIVIDE START WITH UNDERSTANDING DEMAND Bi-directional Communications Intent == value Trend == better planning Network 1 - Uncongested Network 2 - Congested Efficient? Σ(supply) Σ(demand) 13 Copyright 2012 Juniper Networks, Inc. Inefficient or efficient? Σ(supply) = Σ(demand)? Demand is unknown ahead of time Intent can help us learn actual demand Modeling of applications Dynamic analysis of elephant flows Abstract API / UNI to inform of intent

12 NETWORK NEEDS TO ADJUST MUCH FASTER Inform network of desired behavior Bi-Directional Communications Inform application of data intrinsically in the network Network edge has highest rate-of-change Intent == value THE APPLICATION WORLD Network Programmability THE NETWORK WORLD Trend == better planning Some examples User service profile Register intent Hypervisor stack mobility Capture usage pattern End-user Network Flexible creation/modification of sessions What periodic behavior is expected Assurance of service Application Content 14 Copyright 2012 Juniper Networks, Inc.

13 NETWORKING BUSINESS CHALLENGES Configuration Features Software Packaging Reliability Overly complex, manual, operationally expensive. Slow to respond to business requests Too hard to deploy Inflexible, difficult to scale Below expectations 15 Copyright 2012 Juniper Networks, Inc.

14 SDN ARCHITECTURE 2010 Juniper Networks, Inc.

15 WHY DO WE NEED SDN? Static Networks Must respond dynamically based on Business Policy Manual Policies Must be automated to reduce personnel cost Monolithic Network Services Must dynamically scale independent of network devices Essential Applications Must be developed within the network to deliver business results 20 Copyright 2012 Juniper Networks, Inc.

16 TENETS OF SOFTWARE DEFINED NETWORKING (SDN) 1 Network Programmability At multiple levels of abstraction 2 Centralized Control Some control plane functions should remain distributed. 3 Separation of the Planes Forwarding plane, control plane, management plane, and services plane. 21 Copyright 2012 Juniper Networks, Inc.

17 SDN ARCHITECTURE 22 Copyright 2012 Juniper Networks, Inc.

18 SDN IS A PARADIGM AND ARCHITECTURE SDN Overlays SDN SW + Network integrations SDN SDN s definition encompasses 3 elements: 1 Abstract North-Bound Interfaces Network Programming Model 2 Centralized Control Plane Logically Centralized 3 Control, Data, Management and Service Plane Separation With Standards OpenFlow one such example 23 Copyright 2012 Juniper Networks, Inc.

19 SEPARATION OF THE PLANES Centralized Management Plane Centralized Control Plane Peering via Widely Deployed Standard Protocols (BGP) Benefits Independent scaling of planes Ability to use COTS hardware Router / Switch Management Plane Service Plane Hybrid Control Plane Resource pooling Control Plane Different rates of innovation Forwarding Plane Service Plane DistributedControl Plane CAPEX and OPEX savings Forwarding Plane Leverage ASICs for forwarding 24 Copyright 2012 Juniper Networks, Inc.

20 SDN - CENTRALIZED NODE BY NODE CONTROL Physical View Logical View SDN Controller Characteristics End point memberships and virtualized network resources are programmed node by node Network isolation Centralized e2e view Granular control Many control points (every node) 25 Copyright 2012 Juniper Networks, Inc.

21 WHO OWNS SDN? IS IT ABOUT ANY ONE PROTOCOL? Since the original push to define SDN by the ONF, a number of protocol solutions to the programmability problem have emerged. HOW the information between application (operations, workflow, end-user) and network is exchanged is less important than the abstraction. Use Case VXLAN OpenFlow PCE BGP- TE EVPN ALTO Ephemeral DB DC Virtualization x x x DC Interconnect x x x x x x Bandwidth Calendaring x x x x x Virtual Patch Panel, Tap, Steering x x x Network Access Control x x Dynamic Threat Mitigation x x 26 Copyright 2012 Juniper Networks, Inc.

22 THE SDN ECOSYSTEM INCLUDES ORCHESTRATION, CONTROLLERS, NETWORK INFRASTRUCTURE & VIRTUALIZED NETWORK FUNCTIONS Orchestration Orchestration systems Domain driven; DC, Edge, Core, WAN, Campus Commercial; Vmware, IBM, Microsoft, NEC Open Source; OpenStack, CloudStack; OESS Custom - Home grown SDN Controller Controllers Domain & market driven technology; BGP- TE ALTO PCE Open Flow Other DC: BGP L3VPN, Overlay Control Plane/OVSDB+, DOVE Edge/Core/WAN: BGP, PCE R&E: Openflow Network Infrastructure SDN APIs on network platforms; BGP + extensions, OpenFlow, PCE Overlay Networking; MPLS, VXLAN, NVGRE Routing Switching Services L2 & L3 GW functions Virtualized Network Functions vswitches & vrouter (L3 End Points) SDN APIs; XMPP, OVSDB+ vswitch or vrouter vservices Overlay support; MPLS, VXLAN, NVGRE Virtualized Services 27 Copyright 2012 Juniper Networks, Inc.

23 SDN USE CASES 2010 Juniper Networks, Inc.

24 SDN - NETWORK PROGRAMABILITY Network-wide orchestration requires an understanding of: Locality & Affinity Compute/Storage/External Resources Topology & Path LAN/WAN/Data Center Connectivity Communications What the Application Wants Bi-Directional APIs: Bridge the Application and Network Worlds DC EDGE High Rate of Change Externally Controlled Policy Enforcement TRANSPORT Publish Topology and Instrumentation Programmed Topology/Path Guarantee Reliable Communications 29 Copyright 2012 Juniper Networks, Inc.

25 SDN-BASED NETWORK APPLICATIONS Network support for cloud computing Content / Service Routing Inter-Data Center workload mobility Software Defined Networking Content prepositioning to caches Cloudburst Security - DDoS attack prevention 30 Copyright 2012 Juniper Networks, Inc.

26 EXAMPLE WAN EFFICIENCY/OPTIMIZATION SINGLE LEVEL TE OPTIMIZATION USING PCE/PCEP Network Primitives 1. Understand real-time topology 2. Establish a path through the network(s) 3. Select what traffic may (not) use this path Topology Provision Analyze 1: BGP-TE One-way, One session per network Extract topology and reachability information(external reachability, internal links, internal nodes, traffic engineering reservation info) BGP-TE OpenFlow 3: OpenFlow Two-way, session with each head-end node Instruct router to filter specific traffic into one of the established paths OF controller PCE-P Path Computation Element Optimize Optimization criteria: Exit (peering) information (IRS, BPM) Immediate demand Future demand (reservation/calendaring) Historical demand 2: PCE-P Two-way, session with each head-end node Phase-1: Instruct router to modify existing RSVP LSP reservation (path to take, class, bandwidth,..) Phase-2: Instruct router to initiate/delete RSVP LSP reservation 33 Copyright 2012 Juniper Networks, Inc.

27 EXAMPLE CONTENT REQUEST ROUTING APPLICATION NETWORK NETWORK APPLICATION From where the user is connected to where the content is best served Based on: Network Application Network proximity Network availability Network congestion Content availability Content load Content capacity Open standard: ALTO Application Layer Traffic Optimization Content Content Content This is new because: Uses information of the network infrastructure Runs across multiple service providers Mobile & broadband subscribers Chicago ALTO cost ALTO directs traffic to best POP based on network conditions London ALTO cost - 50 Amsterdam ALTO cost Copyright 2012 Juniper Networks, Inc.

28 EXAMPLE BANDWIDTH CALENDARING Schedule a reserved path for your session Web Services API with complete control and predictability Technology used: Real-time topology understanding (ALTO, BGP-TE) Steering traffic through optimal paths (PCE) Selecting specific traffic (OpenFlow) Orchestration What would I use this for? Location 1 Location 2 Network Scheduled application/session specific path in the network Scheduled data center backups Managed content distribution Cloud orchestration 36 Copyright 2012 Juniper Networks, Inc.

29 SDN-ENABLED OPENSTACK CLOUD IaaS (i.e. compute and object storage services) OpenStack Cloud Controller (Orchestration) Plug-in NaaS Interface/API Quantum Protocols Monitoring Network Virtualization Compute OF/SDN Controller(s) Interface/API Storage 43 Copyright 2012 Juniper Networks, Inc.

30 TRAFFIC STEERING DYNAMIC THREAT MITIGATION OpenFlow auto protection OF solution cooperates with IDS and a flow is controlled automatically. Interoperability of OF Switches and OF Controllers normal analysis Block Normal Traffic Suspicious Traffic Attack Traffic copy 48 Copyright 2012 Juniper Networks, Inc.

31 TRANSITION TO SDN 2010 Juniper Networks, Inc.

32 4-STEP APPROACH TO TRANSITION TO SDN Centralize Management Extract Services Centralize Controller Optimize The Hardware 51 Copyright 2012 Juniper Networks, Inc.

33 NETWORK FUNCTION VIRTUALIZATION Data Plane Traffic 1 Steer flows 2 Tunnel flows with meta-data Directly tethered L2 network L3 network 3 Process flows Service in a VM VSE appliance Generic cloud compute 52 Copyright 2012 Juniper Networks, Inc.

34 VIRTUALIZED SERVICES On-Router Tethered Appliance (VSE) Cloud Service Network Address Translation (NAT) Firewall Deep Packet Inspection (DPI) Intrusion Detection / Prevention (IDP) Load Balancer WAN optimization HTTP header rewriting Compression Copyright 2012 Juniper Networks, Inc.

35 SERVICE CHAINING Visit multiple VM-hosted services VMs may be on same or different compute node Visit both VM-hosted and PIC-hosted services 55 Copyright 2012 Juniper Networks, Inc.

36 SUMMARY 2010 Juniper Networks, Inc.

37 SDN PRINCIPLES Separate networking software into 4 layers Forwarding, Control, Services and Mgmt Centralize Mgmt, Services and Control layers Use the cloud for elastic scale and flexible deployment enabling usagebased pricing Common Platform for network and Security applications and management integration Standard protocols for interoperability across vendors Broadly apply to Network & Network Security Enterprise & Service Providers Mobile and Wireline Optimize each network element Simplifies network design and lowers OPEX Reduce time to service and correlate cost based on value Enables new business solutions Provides choice and lowers cost Flexibility and new business opportunities 57 Copyright 2012 Juniper Networks, Inc.

38 THE 7 MYTHS OF SDN Myth: Myth: Myth: Myth: Myth: Myth: Myth: It s only about datacenter networking It s only about reducing CAPEX It s only about software It s only about centralization It s only about OpenFlow It s going to happen immediately It s going to take forever Truth: Truth: Truth: Truth: Truth: Truth: Truth: It applies to all networking and networking services Opex reduction is more significant It will fuel hardware innovation Considerable intelligence stays decentralized OpenFlow is just a protocol and probably not the most important one for SDN It will happen step-by-step We will begin to see the impact in Copyright 2012 Juniper Networks, Inc.

39