Book Image

Learning OpenStack Networking (Neutron)

By : James Denton
Book Image

Learning OpenStack Networking (Neutron)

By: James Denton

Overview of this book

OpenStack Neutron is an OpenStack component that provides networking as a service for other OpenStack services to architect networks and create virtual machines through its API. This API lets you define network connectivity in order to leverage network capabilities to cloud deployments. Through this practical book, you will build a strong foundational knowledge of Neutron, and will architect and build an OpenStack cloud using advanced networking features. We start with an introduction to OpenStack Neutron and its various components, including virtual switching, routing, FWaaS, VPNaaS, and LBaaS. You’ll also get hands-on by installing OpenStack and Neutron and its components, and use agents and plugins to orchestrate network connectivity and build a virtual switching infrastructure. Moving on, you’ll get to grips with the HA routing capabilities utilizing VRRP and distributed virtual routers in Neutron. You’ll also discover load balancing fundamentals, including the difference between nodes, pools, pool members, and virtual IPs. You’ll discover the purpose of security groups and learn how to apply the security concept to your cloud/tenant/instance. Finally, you' ll configure virtual private networks that will allow you to avoid the use of SNAT and floating IPs when connecting to remote networks.
Table of Contents (21 chapters)
Learning OpenStack Networking (Neutron) Second Edition
About the Author
About the Reviewers


Highly available routers can be created and managed using the same router command set that was discussed in the previous chapter. The L3 agents are responsible for configuring the routers in a VRRP group, and the routers are left to elect the master router and implement their respective keepalived configuration.

While HA routers provide a level of redundancy over their standalone counterparts, they are not without their drawbacks. A single node hosting a master router is still a bottleneck for traffic traversing this router. In addition, if the network used for dedicated VRRP traffic between routers experiences a loss of connectivity, the routers can become split-brained, causing two or more routers to become master routers and potentially causing ARP and MAC flapping issues in the network. Connection tracking between routers has not been implemented as of the Kilo release, which means that connections to and from instances may be severed during a failover event. In addition to the...