Book Image

OpenStack Networking Essentials

By : James Denton, Derek Chamorro
Book Image

OpenStack Networking Essentials

By: James Denton, Derek Chamorro

Overview of this book

The OpenStack Networking API offers users the ability to create and manage both basic and complex network architectures that blend the virtual and physical network infrastructure. This book kicks off by describing various components of Openstack Neutron and installing Ubuntu OpenStack based on Canonical's process. Further on, you will use various methods to interface with Neutron to create and manage network resources. You will also get to grips with the relationship between ports, networks, and subnets through diagrams and explanations, and see how the logical components are implemented via plugins and agents. Moving forward, you will learn how virtual switches are implemented and how to build Neutron routers. You will also configure networks, subnets, and routers to provide connectivity to instances using simple examples. At the end, you will configure and manage security groups, and will observe how these rules translate to iptables rules on the host machines. By the end of the book, you will be able to build basic network architectures using Neutron networks and routers in no time.
Table of Contents (15 chapters)
OpenStack Networking Essentials
Credits
About the Author
www.PacktPub.com
Preface
Index

Examining the routers


Virtual routers are implemented as network namespaces on one or more nodes. In our single-node environment, the two routers that have been created so far can both be found on the same node. Using the ip netns command as root or a user with sudo privileges, you can list all network namespaces on a host, like so:

The two qrouter namespaces in the list correspond to the two routers we've created so far:

Using the ip netns exec <namespace> command, you can specify a command to execute within the specified namespace. Useful commands such as ip, netstat, ps, and iptables provide details within the scope of the namespace they're executed in. A quick look at the MySimpleRouter network namespace shows the virtual interface created by Neutron when we attached the router to the MySimpleSubnet subnet earlier in this chapter:

Using the ovs-vsctl show command, we can see the qr-2e525501-5f interface attached to the integration bridge in a local VLAN mapped to MySimpleNetwork:

Additional...