SDN Test Suite – Methodology | SDN Hub SDN Test Suite – Methodology Typical SDN-based Network Virtualization The architecture rolled out can be one of the following: Pure-overlay: Programmable virtual dataplane elements (vDP) are inserted into edge servers and controlled by the controller cluster. Pure-underlay: SDN-enabled top-of-rack or leaf physical switches are deployed and controlled by the controller cluster. Testing these solutions irrespective of the architectural choice makes it essential to adopt a black-box testing methodology that integrates leverages components from the computing world and the networking world. Classes of Tests For testing Network Virtualization, we divided our tests into four main categories: Functionality tests: Essentially these test the claimed (and unclaimed) features of the network-virtualization solution, including the following. Setup for functionality and data plane tests using bare-metal servers Setup for control plane tests Test Suite Design and Architecture Challenges Resources
Lab 3 - OpenvSwitch and OpenFlow Controller - ELET 4421 Open vSwitch is a production quality open source software switch designed to be used as a vswitch in virtualized server environments. A vswitch forwards traffic between different VMs on the same physical host and also forwards traffic between VMs and the physical network. Open vSwitch supports standard management interfaces (e.g. sFlow, NetFlow, RSPAN, CLI), and is open to programmatic extension and control using OpenFlow and the OVSDB management protocol. Open vSwitch as designed to be compatible with modern switching chipsets. How to Install OpenvSwitch in Ubuntu 12.04 1. $/etc/init.d network-manager stop 2. $ apt-getupdate $ apt-get install python-simplejson python-qt4 python-twisted-conch automake autoconf gcc uml-utilities libtool build-essential$ apt-get install build-essential autoconf automake pkg-config 2. $wget $ cd openvswitch-1.7.0.tar.gz $ . $ . $ make $ make install $rmmod bridge 3. 4. 1. 2. $ant
Software Defined Networking course GA Tech About the Course This course introduces software defined networking, an emerging paradigm in computer networking that allows a logically centralized software program to control the behavior of an entire network. Separating a network's control logic from the underlying physical routers and switches that forward traffic allows network operators to write high-level control programs that specify the behavior of an entire network, in contrast to conventional networks, whereby network operators must codify functionality in terms of low-level device configuration. Logically centralized network control makes it possible for operators to specify more complex tasks that involve integrating many disjoint network functions (e.g., security, resource control, prioritization) into a single control framework, allowing network operators to create more sophisticated policies, and making network configurations easier to configure, manage, troubleshoot, and debug. Course Syllabus Module 3: Control Plane Prof.
Introduction to Open vSwitch If you're new here, you may want to subscribe to my RSS feed, or follow me on Twitter! That way you can stay up to date with all Keeping It Classless posts! In the early days of my quest to cut through the jungle of hype regarding SDN, it was difficult to go a single day without hearing about Open vSwitch, or OVS. I’ve been tinkering with Open vSwitch in my lab for a few months now, and realized that I haven’t yet written an introductory post about it for those that haven’t tried it out. If you’re involved with data center like I am, you’re probably familiar with the concept of a vSwitch. The main reason one would use OVS is to greatly improve the capabilities of each hypervisor switch beyond simple bridging capability. The configuration of OVS is controlled by a database schema organized into several tables, all held in userspace (the kernel module is used strictly for forwarding). There are two tools used to configure an OVS instance: OpenFlow and OVSDB. OpenFlow Configuration Conclusion
Spanning Tree and OpenFlow Questions I often get asked include: Can you run Spanning Tree and OpenFlow together?What happens when Spanning Tree blocks a port? Firstly, it is possible to run an OpenFlow network connected to the HP VAN SDN Controller with Spanning Tree turned off. In this blog entry I will show you a simple network with a look and demonstrate what happens with Spanning Tree turned off as well as on using HP Comware switches. VLAN 1 = Management VLAN (Used for communication with the Controller. In this topology I am using two 5900AF-48G-4XG-2QSFP+ switches with the following details: [5900-1]dis version HP Comware Software, Version 7.1.045, Release 2307 Copyright (c) 2010-2013 Hewlett-Packard Development Company, L.P. [5900-2]dis version HP Comware Software, Version 7.1.045, Release 2307 Copyright (c) 2010-2013 Hewlett-Packard Development Company, L.P. In the output below, you can see that Spanning Tree is disabled on VLAN 10: VLAN 192 is the link to the HP VAN SDN Controller: And the result:
Software defined networking, Openvswitch, and Ubuntu 12.04 Recently I’ve been testing over committing on KVM. Once I started running hundreds of virtual machines (vms) on a single node, I realized that in order to get them to do anything I have to access them over the network to run something like Ansible playbooks designed to test load. In order to provide networking resources to the vms, I decided to take a look at Openvswitch and what it takes to get it up and running with KVM and Ubuntu 12.04/Precise. Software defined networking Like cloud and big-data, software defined networking (SDN) is a loaded term. “A good working definition of SDN is the separation of the data and control functions of today’s routers and other layer two networking infrastructure with a well-defined programming interface between the two.” — Via Arstechnica SDN is a big part of OpenStack as well. Openflow is also an important technology in SDN that requires some research time. Building on other’s work I’m not really doing anything new here—though I hope to at some point… :)
OpenFlow, OpenvSwitch and KVM SDN Lab Installation App This OpenFlow, Open vSwitch and KVM SDN Lab Installation App is a python app that will install a few different options at an SDN lab. There are some really nice SDN applications that are coming along that have been open sourced from vendors or the community. Lots of people are really getting interested in understanding what SDN and getting to know new technologies but can quickly hit a wall wether its time to figure out the often tricky installs, lack of experience in Unix and for all of us just time to dedicate to getting a lab framework built.I tried to keep the Python program very linear to make it as readable and reusable as I could. I think I wrote about five pages worth of comments in it. It can be difficult either remembering how to install some of this stuff after a while so I have gotten to the point just to automate everything if possible. There is a screencast below in case anyone gets stuck and needs a reference. There are four installation builds to choose from. Figure 1.
OpenDaylight OpenStack Integration with DevStack on Fedora 20 The following is a walk through of the OVSDB project within OpenDaylight for OpenStack integration. There are a couple of bugs so it is not for the faint of heart. It is intended for those looking to get their development environment up and running. We will have videos and what not walking through the installation and code reviews of the implementation. It was developed by folks from various vendors and users in the community. The following are some late night / early morning recordings from Madhu and me. OpenStack/OpenDaylight/OVSDB Installation Part 1 – Configuring VirtualBox and VM FusionOpenStack/OpenDaylight/OVSDB Installation Part 2 – Stacking and Spinning up Multi-Node OpenStack w/the OpenDaylight ControllerFor more OpenDaylight / OVSDB videos and weekly Hangouts please see our YouTube channel: OpenDaylight OVSDB Channel → No standards were hurt in the making of this recording. There are two options for images. Fedora 19 based all-in-one VM: VirtualBox NIC Network Caveats Oops .