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

Distributed ONOS


Let's now see how an ONOS cluster comprising of one or more ONOS nodes, with a mechanism for syncing the network state, is a key element of the distributed ONOS core. The network switches connect with one or more ONOS nodes via the network control channel. Nodes within the same cluster communicate via the control Network. Switches in the network connect to multiple nodes to achieve resiliency and high availability:

  1. Use the onos-form-cluster tool to create a cluster specifying a list of nodes' IP addresses.

  2. Start Mininet with a set of switches, hosts, and interlinks between them:

  3. Check the ONOS status summary:

  4. Check the node status:

  5. Each device has one primary master and zero or more standby controller nodes that can take over in case the primary master fails:

  6. Check the ONOS Summary in the GUI:

  7. Rebalance the primary for optimal load distribution:

  8. Confirm OVS connects to multiple nodes: