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
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Summary


As features that extend Neutron's functionality are added to it, most are implemented as extensions to the core API. For more information on how to utilize some of the included extensions, refer to the Neutron API documentation found at http://developer.openstack.org/api-ref-networking-v2-ext.html.

Many third-party extensions require the use of additional software or hardware that are often proprietary and may have associated support and operational costs. A production-grade OpenStack cloud does not require the use of third-party extensions and can simply leverage the open-source compute and networking technologies outlined in this book. Proprietary software and hardware may provide additional features, functionality, and stability that are not yet available with open-source alternatives and should be taken into consideration when developing your OpenStack network architecture.

In Appendix B, Virtualizing the Environment, we will take a look at the use of the virtualization software known as VirtualBox as an alternative to physical hardware when completing the exercises outlined in this book.