OpenFlow Ronald van der Pol

Transcription

1 OpenFlow Ronald van der Pol

2 Outline! Goal of this project! Why OpenFlow?! Basics of OpenFlow! Short Demo

3 OpenFlow Overview! Initiative of Stanford University! Run network research experiments and production network on the same infrastructure! Slice your network and give control to various groups! Each slice has independent separated forwarding! Network virtualization! Simple and cheap forwarding hardware! No dependence on closed hardware! Standardized functionality (must haves + optionals)! External control plane (distributed or centralised)! Standard API between hardware and control plane! Currently supported by HP and NEC (special firmware)! Widely used in Future Internet Testbeds in the USA (GENI) and Asia

4 A bright idea I have a great idea! The original Internet architecture was designed to connect one computer to another but a better architecture would be fundamentally based on PEOPLE and CONTENT! That will never work! It won t scale! What about security? It s impossible to implement or operate! Show me! (slide by Chip Elliott GENI Program Office)

5 Network Slices slice A slice B slice C

6 Federation GENI grows by GENI-enabling heterogeneous infrastructure (slide by Chip Elliott GENI Program Office) My experiment runs across the evolving GENI federation. Campus #3 Commercial Clouds Backbone #1 Campus My GENI Slice Access #1 Research Testbed Backbone #2 NSF parts of GENI Other-Nation Projects Corporate GENI suites This approach looks remarkably familiar... Campus #2 Goals: avoid technology lock in, add new technologies as they mature, and potentially grow quickly by incorporating existing infrastructure into the overall GENI ecosystem

7 OpenFlow Basics! API to manipulate forwarding tables in (Ethernet) switches! One or more flow tables with flow entries! Flow entry = match + action! Match on:! Ingress Port! Metadata! Ethernet Address (src and dst)! Ether Type! VLAN ID and Priority! MPLS Label and Class! IPv4 Address (src and dst)! IPv4 Proto! IPv4 ToS! TCP/UDP/SCTP Port (src and dst)! ICMP Code and Type

8 OpenFlow Switch Architecture OpenFlow Controller OpenFlow Protocol OpenFlow Switch Secure Channel Group Table Packet in Flow Table 0 action set Flow Table 1 action set Flow Table 2 action set Flow Table n action set Execute Action Set Packet Out

9 Required Actions! Required Output actions! ALL: send packet on all standard ports, but not ingress port! CONTROLLER: encapsulate and send to controller! TABLE: send packet (from controller) to first flow table! IN_PORT: send packet to ingress port! Required Group action! Process packet through specified group

10 Optional Actions! Optional Output actions! LOCAL: send to local networking stack! NORMAL: process via traditional non-of piperline! FLOOD: flood via normal pipeline, VLAN ID may get used! Optional Set-Queue action! Set queue id for a packet! Optional Push-Tag / Pop-Tag action! Push or pop VLAN tag! Push or pop MPLS header! Optional Set-Field action! Modify fields in the header, e.g. Set Ethernet src/dst MAC address Set VLAN ID or priority Set MPLS label, class, TTL Set IPv4 src/dst address, ToS, ECN, TTL Set transport src/dst port

11 Flow Action Pipeline! Possible instructions after packet match:! Apply-Actions action(s) Apply action(s) immediately without Action Set change! Clear-Actions Clear Action Set! Write-Actions action(s) Merge action(s) into Action Set! Write-Metadata metadata / mask Write masked metadata value into metadata field! Goto-Table next-table-id Next flow table in the processing pipeline

12 DEMO

13 Thank you Ronald van der Pol