How To Understand The Power Of A Network In A Microsoft Computer System (For A Micronetworking)

Transcription

1 Digitaalne andmeülekanne IRT0150 OpenFlow /nädal 6/ Avo Ots 12. märts

2 Various Services Virtual Networks LINP1 LINP3 LINP2 LINP1 Manager LINP2 Manager LINP3 Manager Virtual Resources Physical Resources (Router, Switch, Hosts, etc.) Physical NW 1 Physical NW 2 Physical NW 3 Physical NW 4 Virtual Resources Manager Physical NW 1 Manager Physical NW 2 Manager Physical NW 3 Manager Physical NW 4 Manager

3 OPEX: 60-70% CAPEX: 30-40%

4 Firewall Router IPSec OSPF-TE RSVP-TE HELLO Software Control HELLO Hardware Datapath HELLO

5 5 Tänane mudel Applications built on Reliable (or unreliable) transport built on Best-effort global packet delivery built on Best-effort local packet delivery built on Local physical transfer of bits

6 Multi-Services Module (MS-PIC) Multi-Services Module (MS-PIC) Juniper router Control plane Routing Engine (RE) Switch Control Board (SCB) Packet Forwarding Engine (PFE) Forwarding plane RE x86 PC running JUNOS PFE ASIC hardware and microcode MS-PIC MIPS64-based XLR network processor Each runs separate JUNOS JUNOS FreeBSD-based OS for all Juniper routers

7 Tänane interneti protokollid Routing, management, mobility management, access control, VPNs, App App App Operating System Million of lines of source code 7488 RFCs Barrier to entry Specialized Packet Forwarding Hardware 500M gates 10Gbytes RAM Power Hungry

8 Vajadus S D N järele (1) Networks are hard to manage Computation and storage have been virtualized Creating a more flexible and manageable infrastructure Networks are still notoriously hard to manage Network administrators large share of sysadmin staff

9 Vajadus S D N järele (2) Networks are hard to evolve Ongoing innovation in systems software New languages, operating systems, etc. Networks are stuck in the past Routing algorithms change very slowly Network management extremely primitive

10 Vajadus S D N järele (3) Networks design not based on formal principles OS courses teach fundamental principles Mutual exclusion and other synchronization primitives Files, file systems, threads, and other building blocks Networking courses teach a big bag of protocols No formal principles, just general design guidelines

11 Data plane: Packet streaming Digitaalne andmeedastus Forward, filter, buffer, mark, rate-limit, and measure packets

12 Control plane: Distributed algorithms Track topology changes, compute routes, install forwarding rules

13 Management plane: Human time scale Collect measurements and configure the equipment

14 Control plane Control plane must compute forwarding state. To accomplish its task, the control plane must: Figure out what network looks like (topology) Figure out how to accomplish goal on given topology Tell the swtiches what to do (configure forwarding state) And we require each new protocol to solve all three

15 Areng App App App App App App Windows Windows Windows (OS) (OS) (OS) Linux Linux Linux Mac Mac Mac OS OS OS NOX Controller Controller 1 1 (Network OS) Controller Controller Network 22 OS Virtualization layer x86 (Computer) Virtualization or Slicing OpenFlow Computer Industry Network Industry

16 App App App Network Operating System Ap p Ap p Ap p Operating System Specialized Packet Forwarding Hardware Ap p Ap p Operating System Ap p Ap p Ap p Operating System Ap p Specialized Packet Forwarding Hardware Ap p Ap p Operating System Ap p Specialized Packet Forwarding Hardware Ap p Ap p Ap p Specialized Packet Forwarding Hardware Operating System Specialized Packet Forwarding Hardware

17 17 Software Defined Network (SDN) Consistent, up-to-date global network view Control Program 1 Control Program 2 At least one Network OS probably many. Open- and closed-source Network OS 1. Open interface to packet forwarding Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding

18 18 OpenFlow Basics Control Program A Control Program B Network OS OpenFlow Protocol Ethernet Control Switch Path OpenFlow Data Path (Hardware)

19 Logically-centralized control Smart, slow API to the data plane (e.g., OpenFlow) Switches Dumb, fast

20 OpenFlow Controller OpenFlow Protocol (SSL/TCP) Control Path OpenFlow Data Path (Hardware)

21 OpenFlow Usage Dedicated OpenFlow Network OpenFlow Switch Rule Action Statistics Controller PC OpenFlow Protocol OpenFlow Switch OpenFlow Switch Rule Action Statistics Rule Action Statistics OpenFlowSwitch.org

22 OpenFlow Voo juhtimine Rule Action Stats Packet + byte counters 1. Forward packet to port(s) 2. Encapsulate and forward to controller 3. Drop packet 4. Send to normal processing pipeline 5. Modify Fields Switch Port VLAN ID MAC src MAC dst Eth type IP Src IP Dst IP Prot TCP sport TCP dport + mask what fields to match

23 OpenFlow voo tabel Controller Software Layer OpenFlow Firmware PC Hardware Layer MAC src MAC dst Flow Table IP Src IP Dst TCP sport TCP dport Action * * * * * port 1 port 1 port 2 port 3 port

24 FlowSpace: Maps Packets to Slices (liistak)

25 Dynamic Access Control Inspect first packet of a connection Consult the access control policy Install rules to block or route traffic

26 Seamless Mobility/Migration See host send traffic at new location Modify rules to reroute the traffic

27 27 Server Load Balancing Pre-install load-balancing policy Split traffic based on source IP src=0* src=1*

28 28 Controller Delay and Overhead Controller is much slower the the switch Processing packets leads to delay and overhead Need to keep most packets in the fast path packets

29 A Short History of SDN ~2004: Research on new management paradigms RCP, 4D [Princeton, CMU,.] SANE, Ethane [Stanford/Berkeley] 2008: Software-Defined Networking (SDN) NOX Network Operating System [Nicira] OpenFlow switch interface [Stanford/Nicira] 2011: Open Networking Foundation (~69 members) Board: Google, Yahoo, Verizon, DT, Microsoft, Facebook, NTT Members: Cisco, Juniper, HP, Dell, Broadcom, IBM, : Open Networking Summit 1600 attendees, Google: SDN used for their WAN

30 Lingid e-tue-openflow.pdf article=1000&context=tlen_gradetds