OpenFlow & Software Defined Networking

Transcription

1 OpenFlow & Software Defined Networking HPC SEMINAR DELL & INTEL, 24 APRIL 2014 Ronald van der Pol

2 Outline Vision behind Software Defined Networking (SDN) OpenFlow OpenDaylight SDN controller framework Examples of OpenFlow usage Network Function Virtualisation (NFV) Open Hardware SURFnet & SDN/OpenFlow 2/34

3 Vision Behind Software Defined Networking Separation of Data Plane (data forwarding) and Control Plane (policy) Logically centralised policy (control plane) Program (controller) that reads policy configurations, compiles it to forwarding rules and sends those to network elements à Software Defined Networking Dumb switches (data plane) Firmware does packet frame forwarding only Standardised protocol between switches and controllers (e.g. OpenFlow) Competition on hardware, networking intelligence sits in controller 3/34

4 Traditional Networking Routing and Switching Protocols 4/34

5 SDN Architecture APP APP APP APP Open Northbound API(s) Controller Framework (Network Operating System) Open Southbound API(s) /34

6 Advantages of SDN Transition from single all-in-one boxes to separate modules from different vendors Competition between hardware vendors (switches) Competition between software vendors (controller) More choices, more competition, faster innovation SDN applications SDN controllers and Network Operating Systems Switches Faster innovation Much easier to upgrade software running on a server, compared to firmware in switches Network functions not limited by slow embedded processors in switches, software runs on fast servers 6/34

7 (slide by Nick McKeown, Stanford University) App App App App App App App App App App App Specialized Applications Specialized Operating System Specialized Hardware Windows (OS) Open Interface or Linux or Open Interface Microprocessor Mac OS Vertically integrated Closed, proprietary Slow innovation Small industry Horizontal Open interfaces Rapid innovation Huge industry

8 (slide by Nick McKeown, Stanford University) AppAppAppAppAppAppAppAppAppAppApp Specialized Features Specialized Control Plane Specialized Hardware Vertically integrated Closed, proprietary Slow innovation Open Interface Control Plane or Control Plane or Open Interface Merchant Switching Chips Horizontal Open interfaces Rapid innovation Control Plane

9 Computing vs Networking closed open Open Hardware Hypervisor API Closed hardware Portable VMs Workstations + UNIX UNIX System Call API Start of Open Source Software Portable applications Closed Systems Closed Systems Closed hardware OpenFlow API Open Source Applications Portable applications

10 OpenFlow 10/34

11 OpenFlow Protocol OpenFlow Controller OpenFlow Protocol TCP SSL TLS OpenFlow API OpenFlow Switch Flow Table 11/34

12 Swicth Forwarding Flow Table Matching rule #1 Counter Action #1 Matching rule #2 Counter Action #2 Matching rule #3 Counter Action #3 Matching rule #4 Counter Action #4 Matching rule #5 Counter Action #5 Matching rule #6 Counter Action #6 Matching rule #7 Counter Action #7 12/34

13 Header Matching Ingress port Ethernet source/destination address Ethernet type VLAN ID VLAN priority IPv4/IPv6 source/destination address IPv4/IPv6 protocol number IPv4/IPv6 DS field (DSCP/ECN) IP protocol number TCP/UDP/SCTP source/destination port ICMP/ICMPv6 type/code ARP opcode, source/target IPv4 address MPLS label, TC PBB I-SID 13/34

14 Actions Forward 1 port or multiple ports (multicast) Drop Used for e.g. firewalling Set any if the match fields Modify VLAN (VLAN rewrite), IP address (NAT), etc. Add or remove VLAN tag / MPLS label / PBB I-TAG Push or pop labels 14/34

15 OpenFlow Standardisation Open Networking Foundation (ONF) Non-Profit consortium Founded in March 2011 by Deutsche Telecom, Facebook, Google, Microsoft, Verizon and Yahoo! Mission: Open Networking Foundation (ONF) is a user-driven organization dedicated to the promotion and adoption of Software-Defined Networking (SDN) through open standards development. 15/34

16 OpenDaylight SDN controller framework Developed by an open consortium as a Linux Foundation Collaborative Project Many large vendors as members Most active members: Cisco, IBM, NEC, Ericsson, VMware, Red Hat First release: February 2014 (hydrogen) Base edition (controller + OpenFlow) Virtualisation edition (base + affinity + OpenDOVE + OVSDB + VTN + Defense4All) Service Provider edition (base + affinity + BGP/PCEP + LISP FlowMapping) 16/34

17 OpenDaylight Architecture 17/34

18 Example of OpenFlow Usage Data Centre WAN network 18/34

19 Open vswitch Software switch that implements the OpenFlow protocol Open Source project Included in the Linux kernel, OpenStack, OpenNebula, Developed by Nicira (startup founded in 2007) Martin Casado (Stanford University) Nick McKeown (Stanford University) Scott Shenker (UC Berkeley) Nicira was acquired by VMware in 2012 for USD 1.26 billion 19/34

20 Open vswitch in a Cloud Environment 20/34

21 Google Data Network Google has two networks: I-Scale: User facing services (search, YouTube, Gmail, etc), high SLA G-Scale: Data centre traffic (intra and inter), lower SLA, perfect for OpenFlow testing OpenFlow introduced in G-Scale network since mid 2010 Experience/benefits of introducing OpenFlow: Better Traffic Engineering (global view of network) Centralised Traffic Engineering much faster on a 32 core server (25-50 times as fast) than on slow CPUs inside switches Software development for a high performance server with modern software tools (debuggers, etc) much easier and faster and produces higher quality software than development for an embedded system (router/switch) with slow CPU and little memory 21/34

22 Google Data Network 22/34

23 Google OpenFlow Switch (source Google) 23/34

24 Google s OpenFlow Deployment 24/34

25 Almost 100% Link Utilization 25/34

26 NFV (Network Functions Virtualisation) 26/34

27 Network Functions Virtualisation ETSI Industry Specification Group Goal: Provide Network Functions through virtualisation techniques using general purpose servers and storage devices How: Replace proprietary hardware network appliances by consolidating the network functions as applications running on virtual machines 27/34

28 Open Hardware 28/34

29 Open Compute Project Started by Facebook in April 2011 Build servers and data centres following the Open Source model Open Networking Project announced in May 2013 Build an open network switch Current Projects: Intel: switch specification Mellanox: switch specification Cumulus Networks: ONIE (Open Network Install Environment) Broadcom: switch specification 29/34

30 SDN and SURFnet 30/34

31 SURFnet OpenFlow Activities RoN 2011: OpenFlow technology assessment RoN 2011: OpenFlow Ethernet OAM demo (SC11) RoN 2012: MPTCP multipath OpenFlow demo (GLIF, SC12, TNC2013) RoN 2012: Testbed with Pica8 OpenFlow switches March 2013: OpenFlow workshop by Steve Wallace 2013: Partner in GN3plus JRA2 T1 SDN 2013: Partner in EU-JP FELIX interdomain OpenFlow testbeds 2013: OpenFlow testbed connected to i2, GÉANT3, StarLight, UvA 31/34

32 SURFnet OpenFlow Testbed All switches in testbed Amsterdam (Science Park) 4x Pica (48x 1GE UTP ports & 4x 10GE SFP+ ports) 1x Pica (48x 10GE SFP+ ports & 4x 40GE QSFP+ ports) 3x Supermicro servers (one used for OpenStack & Neutron netwerk module testing) External connections: StarLight Internet2 GN3plus OpenFlow Facility UvA 32/34

33 2014 Activities Extend OpenFlow testbed to Groningen, Enschede, Utrecht, Delft Evaluate OpenFlow controller frameworks (DONE: OpenDaylight) GN3plus CoCo Open Call (TNO & SURFnet) Build an international on-demand L2 virtual network service Research on Networks Project with UTwente, RUG and UvA Continue work in GN3plus JRA2 T1 SDN and EU-JP FELIX 33/34

34 Ronal van der Pol