SDN 101: Software Defined Networking Course @ ITI - Sameh Zaghloul/IBM - 2014

46 %
54 %
Information about SDN 101: Software Defined Networking Course @ ITI - Sameh Zaghloul/IBM -...
Technology

Published on January 4, 2014

Author: SamehZaghloul

Source: slideshare.net

Description

Sameh Zaghloul
Technology Manager @ IBM
+2 0100 6066012
zaghloul@eg.ibm.com

SDN: Technology that enables data center team to use software to efficiently control network resources

SDN Overview
SDN Standards
NFV – Network Function Virtualization
SDN Scenarios and Use Cases
SDN Sample Research Projects
SDN Technology Survey
SDN Case Study
SDN Online Courses
SDN Lab SW Tools
- OpenStack Framework
- OpenDayLighyt – SDN Controller
- FloodLight – SDN Controller
- Open vSwitch – Virtual Switch
- MiniNet – Virtual Network: OpenFlow Switches, SDN Controllers, and Servers/Hosts
- OMNet++ Network Simulator
- Avior – Sample FloodLight Java Application
- netem - Network Emulation
- NOX/POX - C++/ Python OpenFlow API for building network control applications
- Pyretic = Python + Frenetic - Enables network programmers and operators to write modular network applications by providing powerful abstractions
- Resonance - Event-Driven Control for Software-Defined Networks (written in  Pyretic)

SDN Project

SDN: Software Defined Networking Technology that enables data center team to use software to efficiently control network resources SAMeh Zaghloul Technology Manager @ IBM +2 0100 6066012 zaghloul@eg.ibm.com 3/5/2014 ITI SDN 101 1

• • • • • • • • • SDN Overview SDN Standards NFV – Network Function Virtualization SDN Scenarios and Use Cases SDN Sample Research Projects SDN Technology Survey SDN Case Study SDN Online Courses SDN Lab SW Tools 1. OpenStack Framework 2. OpenDayLighyt – SDN Controller 3. FloodLight – SDN Controller 4. Open vSwitch – Virtual Switch 5. MiniNet – Virtual Network: OpenFlow Switches, SDN Controllers, and Servers/Hosts 6. OMNet++ Network Simulator 7. Avior – Sample FloodLight Java Application 8. NOX/POX - C++/ Python OpenFlow API for building network control applications 9. Pyretic = Python + Frenetic - Enables network programmers and operators to write modular network applications by providing powerful abstractions 10. Resonance - Event-Driven Control for Software-Defined Networks (written in Pyretic) 11. Trema - Full-Stack OpenFlow Framework in Ruby and C 12. FlowScale - Project to divide and distribute traffic over multiple physical switch ports. 13. SNAC - Open source OpenFlow controller for LANs with a graphical user interface. • SDN Project Note: slides contain HyperlinksSDN external resources – run in “Presentation” mode 3/5/2014 ITI to 101 2

SDN Overview 3/5/2014 ITI SDN 101 3

What is Cloud Computing and Software Defined Environments (SDE) Cloud Computing was once defined by the National Institute of Standards and Technology (NIST) as “Convenient, on-demand network access to a shared pool of configurable resources which include: • Networks (SDN), • Servers (SDC), • Storage (SDS), • Applications/Services/Orch estration (SDO) 3/5/2014 ITI SDN 101 4

Open Networking Foundation Pursues New SDN Standards The members of the Open Networking Foundation will include: Broadcom, Brocade, Ciena, Cisco, Citrix, D ell, Deutsche Telekom, Ericsson, Fa cebook, Force10, Goo gle, HewlettPackard, I.B.M., Junip er, Marvell, Microsoft , NEC, Netgear, NTT, R iverbed Technology, Verizon, VMWare and Yahoo. 3/5/2014 ITI SDN 101 5

SDN Context within Software Defined Environments (SDE) 3/5/2014 ITI SDN 101 6

What is SDN? • Recent trends in communications networking have made it possible to control the behavior of entire networks from a single, high-level software program. • This trend, called software-defined networking (SDN), is reshaping the way networks are designed, managed, and secured. • This new field of networking is still evolving for OpenFlow Switches/Controllers (NOX, FloodLight, and OpenDayLight). • Cloud (OpenStack) and SDN (OpenFlow) integration is: “Network Connectivity as a Service – NaaS” (Quantum/Neutron) 3/5/2014 ITI SDN 101 7

What is OpenStack? 3/5/2014 ITI SDN 101 8

OpenStack - Cloud Computing and SDN Integration 3/5/2014 ITI SDN 101 9

Current Network Closed to Innovations in the Infrastructure Closed App App App Operating System App Specialized Packet Forwarding Hardware App App App App Operating System Specialized Packet Forwarding Hardware App Operating System App Specialized Packet Forwarding Hardware App App Operating System App App App Specialized Packet Forwarding Hardware Operating System 3/5/2014 Specialized Packet Forwarding Hardware ITI SDN 101 10

“Software Defined Networking” approach to open it App App App Network Operating System App App App Operating System App Specialized Packet Forwarding Hardware App App App App Operating System Specialized Packet Forwarding Hardware App Operating System App Specialized Packet Forwarding Hardware App App Operating System App App App Specialized Packet Forwarding Hardware Operating System 3/5/2014 Specialized Packet Forwarding Hardware ITI SDN 101 11

The “Software-defined Network” 2. At least one good operating system Extensible, possibly open-source 3. Well-defined open API App App App Network Operating System 1. Open interface to hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware 3/5/2014 Simple Packet Forwarding ITI Hardware SDN 101 12

Network Not Keeping Pace with Server Virtualization 3/5/2014 ITI SDN 101 13

Isolated “slices” App App Network Operating System 1 Many operating systems, or Many versions App App Network Operating System 2 App App App Network Operating System 3 App Network Operating System 4 Open interface to hardware Virtualization or “Slicing” Layer Open interface to hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware 3/5/2014 Simple Packet Forwarding Hardware ITI SDN 101 14

SDN: Network Layers 3/5/2014 ITI SDN 101 15

SDN in Action 3/5/2014 ITI SDN 101 16

Open Data Center Interoperable Network (ODIN) • Traditional networks are designed for North-South traffic flows (which traverse multiple network tiers (i.e. latency and degrading performance) • ODIN promotes a flat, 2 tier network optimized for East-West traffic (layer-2) between servers. • ODIN promotes scaling the network to thousands of physical ports at 10/40/100 GbE each, and tens of thousands of virtual machines. • ODIN promotes software defined networking and virtualized network overlays (wire-once). • ODIN describes equal cost multipath spine-leaf architectures. 3/5/2014 ITI SDN 101 17

Network Subscription Level Network Subscription Level is the difference between: 1. 2. The input bandwidth (north) for each layer of switching in the network (or, number of downlinks) The output bandwidth (south) for each layer of switching in the network (or, number of uplinks) Fully-subscribed North-South network: downlinks = uplinks Oversubscribed switch: downlink > uplink Undersubscribed: uplink > downlink New 40GbE and 100GbE Interfaces/Ports for Switches and Servers 3/5/2014 ITI SDN 101 18

3/5/2014 ITI SDN 101 19

3/5/2014 ITI SDN 101 20

Comparison Network topology Scaling Up & Down Capex & Opex Network Management Network Subscription Level Virtualization environment 3/5/2014 Classical Networks SDN -Network consists of many tiers, where each layer duplicates many of the IP/Ethernet packets, this adds cumulative end-toend latency and requires significant amounts of processing and memory - data traffic between racks of servers and storage needs to travel up and down a logical tree structure which will add latency and potentially creates congestion on inter-switch links (ISLs) -Network loops are prevented by using Spanning Tree Protocol (STP) which allows only one active path between any two switches. This means that ISL bandwidth is limited to a single logical connection, which may lead to ISL bottlenecks. Do not scale in a cost effective or performance effective manner. Scaling requires adding more tiers to the network, more physical switches, and more physical service appliances Installation and maintenance of this physical compute model requires both high capital expense and high operating expense. The high capital expense is due to the large number of underutilized servers and multiple interconnect networks. High operational expense is driven by high maintenance and energy consumption of poorly utilized servers, high levels of manual network and systems administration conventional data centers use several tools to manage their server, storage, network and hypervisor elements removing tiers from a traditional hierarchical data center network and collapses into a two tier network (access switches, also known as top of rack (TOR) switches, and core switches),connected devices can communicate with each other without using an intermediate router -Flatter networks also include elimination of STP. Replacing the STP protocol allows the network to support a fabric topology (tree, ring, mesh, or core/edge) while avoiding ISL bottlenecks Fabrics use multiple least cost paths for high performance and reliability, and are more elastic (scaling up or down as required) Flattening the network reduces capital expense through the elimination of dedicated storage, cluster and management adapters and their associated switches, and the elimination of traditional networking tiers. Operating expense is also reduced through management simplification by enabling a single console to manage the resulting converged fabric Converging and flattening the network leads to simplified physical network management Network was over-provisioned most of the time. This To be able to provide a network which is “ any-to-any” approach provided an acceptable user experience, but it does connectivity,” fairness”, and “non-blocking”, which will help in not scale in a cost effective manner. subscription levels Conventional data centers have consisted of lightly utilized servers running a bare metal operating system or a hypervisor with a small number of virtual machines (VMs) ITI SDN 101 High virtualized, which will leads to high availability and better performance. 21

SDN: Architecture 3/5/2014 ITI SDN 101 22

SDN: Software Defined Networking Technology that enables data center team to use software to efficiently control network resources Traditional switch design OpenFlow design Comparison of different controller architectures 3/5/2014 ITI SDN 101 23

Why SDN is important for Virtual Environments and VM Mobility (1/5) 3/5/2014 ITI SDN 101 24

Why SDN is important for Virtual Environments and VM Mobility (2/5) 3/5/2014 ITI SDN 101 25

Why SDN is important for Virtual Environments and VM Mobility (3/5) 3/5/2014 ITI SDN 101 26

Why SDN is important for Virtual Environments and VM Mobility (4/5) Software Defined Network for Virtual Environments Software Defined Networking (SDN) offers a next-generation alternative to networking in the data center using network virtualization and separation of control plane and data plane techniques. Software Defined Network for Virtual Environments (SDN VE) creates a virtual network for virtual machines (VMs). This virtual network is decoupled and isolated from the physical network, much like VMs are separated from the host server hardware. This approach enables virtual networks to be created without any changes to the existing network –meaning it can be wired once. Provisioning and administration are simplified and automated, and IP and MAC addresses can be reused, permitting logical separation of networks for multi-tenancy. OpenFlow-enabled switches and a programmable network controller provide centralized control. SDN VE incorporates open source components to enable an ecosystem of network services.

Why SDN is important for Virtual Environments and VM Mobility (5/5) 3/5/2014 ITI SDN 101 28

SDN Market Potential Domains Products • • • • • • • • Switches, routers: About 15 vendors • Software: 8-10 vendors and startups Data centers Public clouds Enterprise/campus Cellular Enterprise WiFi WANs Home networks New startups. Lots of hiring in networking. 3/5/2014 ITI SDN 101 29

SDN Standards 3/5/2014 ITI SDN 101 30

3/5/2014 ITI SDN 101 31

3/5/2014 ITI SDN 101 32

3/5/2014 ITI SDN 101 33

3/5/2014 ITI SDN 101 34

3/5/2014 ITI SDN 101 35

3/5/2014 ITI SDN 101 36

3/5/2014 ITI SDN 101 37

3/5/2014 ITI SDN 101 38

OpenFlow Forwarding Abstraction Control Program A Control Program B Network OS “If header = p, send to port 4” Packet Forwarding Packet Forwarding 3/5/2014 “If header = q, overwrite header with r, add header s, and send to ports 5,6” “If header = ?, send to me” Flow Table(s) Packet Forwarding ITI SDN 101 39

Communication in OpenFlow Network Controller MAC table: MAC address Ingress port 08-00-20-3A-00-4F 1 Packet-in: unmatched frame with MAC 08-00-2A-0B-FE-FD Packet-out: flood on all ports except ingress port Src: 08-00-20-3A-00-4F Dst: 08-00-2A-0B-FE-FD 1 2 OpenFlow Switch Host 1 MAC address 08-00-20-3A-00-4F Host 2 MAC address 08-00-2A-0B-FE-FD Flow Table: Match Field empty 3/5/2014 Action empty ITI SDN 101 40

Communication in OpenFlow Network Controller Flow-mod messages: Match Src: 08-00-2A-0B-FE-FD Dst: 08-00-20-3A-00-4F Match Src: 08-00-20-3A-00-4F Dst: 08-00-2A-0B-FE-FD MAC table: MAC address 1 08-00-2A-0B-FE-FD Forward on port 1 Ingress port 08-00-20-3A-00-4F Action 2 Packet-in: unmatched frame with MAC 08-00-20-3A-00-4F Action Forward on port 2 Src: 08-00-2A-0B-FE-FD Packet-out: forward on port 1 Dst: 08-00-20-3A-00-4F 1 2 OpenFlow Switch Host 1 MAC address 08-00-20-3A-00-4F Flow Table: Match Field Action Src: 08-00-2A-0B-FE-FD Dst: 08-00-20-3A-00-4F Forward on port 1 Src: 08-00-20-3A-00-4F Dst: 08-00-2A-0B-FE-FD 3/5/2014 Host 2 MAC address 08-00-2A-0B-FE-FD Forward on port 2 ITI SDN 101 41

Network virtualization in Data Center 3/5/2014 ITI SDN 101 42

(Option 1) Classical VLAN 3/5/2014 ITI SDN 101 43

(Option 2) OpenFlow with Overlay type 3/5/2014 ITI SDN 101 44

(Option 3) OpenFlow with Hop-by-Hop type 3/5/2014 ITI SDN 101 45

NFV – Network Function Virtualization 3/5/2014 ITI SDN 101 46

3/5/2014 ITI SDN 101 47

3/5/2014 ITI SDN 101 48

3/5/2014 ITI SDN 101 49

3/5/2014 ITI SDN 101 50

SDN Scenarios and Use Cases 3/5/2014 ITI SDN 101 51

Use Case – What Location Why SDN Needed Benefits Achieved Network Virtualization– MultiTenant Networks Datacenter To dynamically create segregated topologically-equivalent networks across a datacenter, scaling beyond typical limits of VLANs today at 4K Better utilization of datacenter resources, claimed 20-30% better use of resources. Faster turnaround times in creating segregated network, from weeks to minutes via automation APIs. Network Virtualization – Stretched Networks Datacenter To create location-agnostic networks, across racks or across datacenters, with VM mobility and dynamic reallocation of resources Simplified applications that can be made more resilient without complicated coding, better use of resources as VMs are transparently moved to consolidate workloads. Improved recovery times in disasters. Service Insertion (or Service Chaining) Datacenter/ Service Provider DMZ/WAN To create dynamic chains of L4-7 services on a per tenant basis to accommodate self-service L4-7 service selection or policy-based L47 (e.g. turning on DDoS protection in response to attacks, self-service firewall, IPS services in hosting environments, DPI in mobile WAN environments) Provisioning times reduced from weeks to minutes, improved agility and self-service allows for new revenue and service opportunities with substantially lower costs to service Tap Aggregation Datacenter/campus access networks Provide visibility and troubleshooting capabilities on any port in a multiswitch deployment without use of numerous expensive network packet brokers (NPB). Dramatic savings and cost reduction, savings of $50-100K per 24 to 48 switches in the infrastructure. Less overhead in initial deployment, reducing need to run extra cables from NPBs to every switch. 3/5/2014 ITI SDN 101 52

Use Case – What Location Why SDN Needed Benefits Achieved Dynamic WAN reroute –move large amounts of trusted data bypassing expensive inspection devices Service Provider/ Enterprise Edge Provide dynamic yet authenticated programmable access to flow-level bypass using APIs to network switches and routers Savings of hundreds of thousands of dollars unnecessary investment in 10Gbps or 100Gbps L4-7 firewalls, loadbalancers, IPS/IDS that process unnecessary traffic. Dynamic WAN interconnects Service Provider To create dynamic interconnects at Internet interchanges between enterprise links or between service providers using cost-effective highperformance switches. Ability to instantly connect Reduces the operational expense in creating crossorganization interconnects, providing ability to enable self-service. Bandwidth on Demand Service Provider Enable programmatic controls on carrier links to request extra bandwidth when needed (e.g. DR, backups) Reduced operational expense allowing self-service by customers and increased agility saving weeks of manual provisioning. Virtual Edge – Residential and Business Service Provider Access Networks In combination with NFV initiatives, replace existing Customer Premises Equipment (CPE) at residences and businesses with lightweight versions, moving common functions and complex traffic handling into POP (points-of-presence) or SP datacenter. Increased usable lifespan of on-premises equipment, improved troubleshooting, less truck rolls, flexibility to sell new services to business and residential customers. 3/5/2014 ITI SDN 101 53

SDN Sample Research Projects 3/5/2014 ITI SDN 101 54

3/5/2014 ITI SDN 101 55

3/5/2014 ITI SDN 101 56

Operator Network Monetization Through OpenFlow™-Enabled SDN 3/5/2014 ITI SDN 101 57

OpenFlow Research 3/5/2014 ITI SDN 101 58

OpenFlow-as-a-Service (OpenStack Quantum) 3/5/2014 ITI SDN 101 59

SDN Technology Survey 3/5/2014 ITI SDN 101 60

SDN and NFV Product and Services Directory 3/5/2014 ITI SDN 101 61

eBay 3/5/2014 ITI SDN 101 62

Google 3/5/2014 ITI SDN 101 63

BigSwitch 3/5/2014 ITI SDN 101 64

Cisco 3/5/2014 ITI SDN 101 65

HP 3/5/2014 ITI SDN 101 66

Intel 3/5/2014 ITI SDN 101 67

VMWare (NSX/Nicira) 3/5/2014 ITI SDN 101 68

VMWare (NSX/Nicira) 3/5/2014 ITI SDN 101 69

VMWare (NSX/Nicira) 3/5/2014 ITI SDN 101 70

Juniper 3/5/2014 ITI SDN 101 71

Juniper 3/5/2014 ITI SDN 101 72

IBM Controller Platforms Network Virtualization z OpenFlow Physical Switches 3/5/2014 GA 10/2012 IBM PNC (OF Ctrl) SDN DVS 5000V Controller SDN IBM SDN-VE NFV DOVE: NFV standards-compliant layer-2 virtual switch multi-tenant network virtualization • Advanced Connectivity Service with Application chaining • Additional Hypervisor vSwitches • Additional OpenFlow enabled OpenFlow OF 1.0 10GE switch ITI SDN 101 IBM Switches • OpenFlowSpec Currency Release OF 1.3.1 73

IBM SDN-VE: A hypervisor for the network • • • SDN for Virtual Environments (SDN-VE) is based on IBM’s Distributed Overlay Virtual Ethernet (DOVE) networking technology SDE-VE uses existing IP infrastructure: No change to existing network Provides server-based connectivity for virtual workloads 3/5/2014 ITI SDN 101 74

IBM Software Defined Networking OpenStack based SDE framework for storage, compute & networking Load Balancer Firewall Firewall IBM SmartCloud Stack Multi-tier workload patterns Monitoring & service assurance Intrusion Prevention Web Servers Application Server Database Cluster SmartCloud Orchestration Cinder Storage APIs NOVA Compute APIs Quantum Storage OpenStack Quantum API NOVA SDN-VE (Open Daylight based) Driver Driver PowerVM OpenFlow 1.0, 1.3.1 DOVE / vSwitch other std I/F zHyp VMware KVM Hyper-V OpenStack Quantum Enhancements Service & middleware configuration Service connectivity Service templates Service connectivity patterns 3/5/2014 ITI SDN 101 75

IBM SmartCloud Foundations & OpenStack Supporting both Vertically Integrated and Horizontal solutions • • • • Open, common, standards based architecture Simple 3 tier structure, with increased Client Value at each tier Clean upgrade paths Significant customer benefits above and beyond base OpenStack Related Standards & Organizations TOSCA OSLC CCRA CIMI & OVF SmartCloud Orchestration – Orchestrate Services across multiple environments and domains SmartCloud Provisioning SmartCloud Provisioning Automate Optimized Workloads Automate Optimized Workloads Automate Optimized Workloads Key: SmartCloud Entry Automate IT Delivery Common Cloud Stack SmartCloud Entry Automate IT Delivery Customer integrated hardware 3/5/2014 PureApplication System PureFlex System ITI SDN 101 Factory Integrated Bundle Option 76

Checklist of Key SDN Controller Functionality OpenFlow Support IT organizations need to understand the OpenFlow functionality that the controller currently supports, including support for optional features and extensions to the protocol. IT organizations also need to understand the vendor’s roadmap to implement new versions of OpenFlow. Network Virtualization It must be possible to dynamically create policy-based virtual networks to meet a range of requirements. These virtual networks must abstract and pool network resources in a manner similar to how server virtualization abstracts and pools compute resources. Network Functionality This includes the ability to discover multiple paths from origin to destination and to split the traffic across multiple links. It also includes the ability to utilize a rich set of constructs that enable the creation of L2 and L3 networks within a tenant-specific virtual network. Scalability An SDN controller should be able to support a minimum of 100 switches. It must also be able to mitigate the impact of network broadcast overhead and the proliferation of flow table entries. Performance An SDN controller must be able to pre-populate the flow tables to the degree possible and it must have processing and I/O capabilities that ensure that the controller is not a bottleneck in the creation of flow entries. 3/5/2014 ITI SDN 101 77

Checklist of Key SDN Controller Functionality Network Programmability It must be possible to apply sophisticated filters to packets. The SDN controller should provide templates that enable the creation of scriptable CLIs that allow for the dynamic programming of the network. Reliability It must be possible to have multiple network paths from origin to destination. The SDN controller should also be built using both hardware and software redundancy features and it must be possible to cluster the controllers. Security of the Network It must be possible to apply enterprise class authentication and authorization and to completely isolate each virtual network. The SDN controller must be able to rate limit the control communications. Centralized Management and Visualization An SDN controller should enable the IT organization to choose the classes of traffic that it monitors and it should present to the IT organization a visualization of both the physical network and the multiple virtual networks that run on top of it. The SDN Controller Vendor The vendor must demonstrate that it has the financial and technical resources to support the ongoing development that will be associated with SDN. The vendor must also demonstrate its long-term position and momentum in the SDN marketplace. 3/5/2014 ITI SDN 101 78

SDN Case Study 3/5/2014 ITI SDN 101 79

Case Study Marist College (a member of Internet2), which currently includes several academic partners (Columbia University, City University of New York, and State University of New York), as well as corporate partners (IBM, ADVA, NEC, and BigSwitch). 3/5/2014 ITI SDN 101 80

• SDN/NFV test bed constructed as part of the New York State Center for Cloud Computing and Analytics SDN Innovation Lab. Established in 2013. • This center is a consortium based at Marist College (a member of Internet2), which currently includes several academic partners (Columbia University, City University of New York, and State University of New York) • as well as corporate partners (IBM, ADVA, NEC, and BigSwitch). • The goals of this test bed include demonstrating practical use cases for SDN/NFV network abstractions, promoting standardsbased, open source development communities, and developing new academic curricula for networking professionals. 3/5/2014 ITI SDN 101 81

3/5/2014 ITI SDN 101 82

3/5/2014 ITI SDN 101 83

3/5/2014 ITI SDN 101 84

SDN Online Courses 3/5/2014 ITI SDN 101 85

A Review of Recent SDN MOOC (Massive Open Online Course) 3/5/2014 ITI SDN 101 86

Software Defined Networking @ coursera 3/5/2014 ITI SDN 101 87

SDN Lab SW Tools 3/5/2014 ITI SDN 101 88

OpenStack – How to get Images 3/5/2014 ITI SDN 101 89

OpenStack – Documentation 3/5/2014 ITI SDN 101 90

OpenStack – Network Plug-ins 3/5/2014 ITI SDN 101 91

OpenStack – Network Configuration Scenarios 3/5/2014 ITI SDN 101 92

OpenDayLighyt – SDN Controller 3/5/2014 ITI SDN 101 93

OpenDayLighyt Pre-built Opendaylight VM Images 3/5/2014 ITI SDN 101 94

OpenDayLighyt – Neutron Plugin 3/5/2014 ITI SDN 101 95

OpenDaylight Virtual Tenant Network (VTN) 3/5/2014 ITI SDN 101 96

FloodLight – SDN Controller 3/5/2014 ITI SDN 101 97

FloodLight configuration with OpenStack 3/5/2014 ITI SDN 101 98

FloodLight configuration with DevStack 3/5/2014 ITI SDN 101 99

MiniNet – Virtual Network: OpenFlow Switches, SDN Controllers, and Servers/Hosts 3/5/2014 ITI SDN 101 100

MiniNet – Virtual Network: OpenFlow Switches, SDN Controllers, and Servers/Hosts 3/5/2014 ITI SDN 101 101

MiniNet GUI Automatic Creation of Mininet Scripts 3/5/2014 ITI SDN 101 102

Open vSwitch – Virtual Switch 3/5/2014 ITI SDN 101 103

Open vSwitch – Configuration with OpenStack 3/5/2014 ITI SDN 101 104

OMNet++ Network Simulator 3/5/2014 ITI SDN 101 105

OMNet++ Network Simulator 3/5/2014 ITI SDN 101 106

Avior – Sample FloodLight Java Application 3/5/2014 ITI SDN 101 107

Avior – Sample FloodLight Java Application 3/5/2014 ITI SDN 101 108

Avior – Sample FloodLight Java Application 3/5/2014 ITI SDN 101 109

NOX - C++ OpenFlow API for building network control applications POX - Python OpenFlow API for building network control applications 3/5/2014 ITI SDN 101 110

Pyretic = Python + Frenetic Enables network programmers and operators to write modular network applications by providing powerful abstractions 3/5/2014 ITI SDN 101 111

Resonance Event-Driven Control for Software-Defined Networks (written in 3/5/2014 ITI SDN 101 Pyretic) 112

Trema Full-Stack OpenFlow Framework in Ruby and C 3/5/2014 ITI SDN 101 113

FlowScale Project to divide and distribute traffic over multiple physical switch ports. 3/5/2014 ITI SDN 101 114

SNAC Open source OpenFlow controller for LANs with a graphical user interface and a policy definition language. 3/5/2014 ITI SDN 101 115

SDN Project 3/5/2014 ITI SDN 101 116

1st Project Network Virtualization– Multi-Tenant Networks To dynamically create segregated topologicallyequivalent networks across a datacenter, scaling beyond typical limits of VLANs today at 4K Better utilization of datacenter resources, claimed 20-30% better use of resources. Faster turnaround times in creating segregated network, from weeks to minutes via automation APIs. 3/5/2014 ITI SDN 101 117

2nd Project SDN Integration with Multiple Hypervisors Integrate VMWare SDN Solution (NSX) with multiple Hypervisors: • VMWare • Hyper-V • Cetrix Xen • KVM Automating VM-to-VLAN association/provisioning. Test SDN capabilities in VM Fault-Tolerant Solutions, with VM/VLAN Fail-Over and/or Fall-Back. 3/5/2014 ITI SDN 101 118

Simulated SDN Project Network 3/5/2014 ITI SDN 101 119

Add a comment

Related presentations

Presentación que realice en el Evento Nacional de Gobierno Abierto, realizado los ...

In this presentation we will describe our experience developing with a highly dyna...

Presentation to the LITA Forum 7th November 2014 Albuquerque, NM

Un recorrido por los cambios que nos generará el wearabletech en el futuro

Um paralelo entre as novidades & mercado em Wearable Computing e Tecnologias Assis...

Microsoft finally joins the smartwatch and fitness tracker game by introducing the...