Book Image

Software-Defined Networking (SDN) with OpenStack

By : Sreenivas Voruganti, Sriram Subramanian
Book Image

Software-Defined Networking (SDN) with OpenStack

By: Sreenivas Voruganti, Sriram Subramanian

Overview of this book

Networking is one the pillars of OpenStack and OpenStack Networking are designed to support programmability and Software-Defined Networks. OpenStack Networking has been evolving from simple APIs and functionality in Quantum to more complex capabilities in Neutron. Armed with the basic knowledge, this book will help the readers to explore popular SDN technologies, namely, OpenDaylight (ODL), OpenContrail, Open Network Operating System (ONOS) and Open Virtual Network (OVN). The first couple of chapters will provide an overview of OpenStack Networking and SDN in general. Thereafter a set of chapters are devoted to OpenDaylight (ODL), OpenContrail and their integration with OpenStack Networking. The book then introduces you to Open Network Operating System (ONOS) which is fast becoming a carrier grade SDN platform. We will conclude the book with overview of upcoming SDN projects within OpenStack namely OVN and Dragonflow. By the end of the book, the readers will be familiar with SDN technologies and know how they can be leveraged in an OpenStack based cloud.
Table of Contents (16 chapters)
Software-Defined Networking (SDN) with OpenStack
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface

Using ONOS to manage Open vSwitch


Having installed and configured ONOS with the preceding features, let's put the setup to use by managing Open vSwitch instances using ONOS. Open vSwitch, or OVS as it is popularly called, is a virtual switch that supports OpenFlow protocols:

  1. In Chapter 4, SDN Networking with Open vSwitch, we introduced Mininet as a tool to simulate an Open vSwitch-based network topology. We will continue to use Mininet to discuss how ONOS can manage OVS. The first step is to create a network topology using Mininet:

  2. Let us check the ONOS GUI to verify the preliminary state by pointing the web browser to http://<ONOS_Controller_IP>:8181/index.html:

  3. Simulate network traffic using a ping command on the Mininet shell:

  4. Check the node, links, and device status using the ONOS CLI command as shown in the following screenshot:

  5. We will use OVS commands to verify if the OpenFlow tables have been programmed or not:

  6. We can also check the status on the ONOS GUI. It shows a summary...