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.

Related Content you might be interested in

Current Title:

Small book image
Learning OpenStack Networking (Neutron)
James Denton
Nov, 2015 | 462 pages
No titles found
Table of Contents (21 chapters)
Learning OpenStack Networking (Neutron) Second Edition
Learning OpenStack Networking (Neutron) Second Edition
Credits
Credits
About the Author
About the Author
About the Reviewers
About the Reviewers
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Preparing the Network for OpenStack
Preparing the Network for OpenStack
What is OpenStack Networking?
Preparing the physical infrastructure
Physical server connections
Separating services across nodes
Summary
2
Installing OpenStack
Installing OpenStack
System requirements
Initial network configuration
Initial steps
Installing OpenStack
Summary
3
Installing Neutron
Installing Neutron
Basic networking elements in Neutron
Extending functionality with plugins
Network namespaces
Installing and configuring Neutron services
Configuring Neutron services
Summary
4
Building a Virtual Switching Infrastructure
Building a Virtual Switching Infrastructure
Virtual network devices
Network types supported by Neutron
Choosing a plugin and driver
Visualizing traffic flow when using LinuxBridge
Visualizing the traffic flow when using Open vSwitch
Configuring the ML2 networking plugin
Configuring the LinuxBridge driver and agent
Configuring the Open vSwitch driver and agent
Summary
5
Creating Networks with Neutron
Creating Networks with Neutron
Network management
Neutron ports
Attaching instances to networks
Exploring how instances get their addresses
Exploring how instances retrieve their metadata
Summary
6
Managing Security Groups
Managing Security Groups
Security groups in OpenStack
An introduction to iptables
Working with security groups
Implementing security group rules
Working with security groups in the dashboard
Disabling port security
Summary
7
Creating Standalone Routers with Neutron
Creating Standalone Routers with Neutron
Routing traffic in a cloud
Installing and configuring the Neutron L3 agent
Router management in the CLI
Network address translation
Floating IP management
Demonstrating traffic flow from an instance to the Internet
Router management in the dashboard
Summary
8
Router Redundancy Using VRRP
Router Redundancy Using VRRP
Using keepalived and VRRP to provide redundancy
Networking of highly available routers
Installing and configuring additional L3 agents
Configuring Neutron
Working with highly available routers
Decomposing a highly available router
Summary
9
Distributed Virtual Routers
Distributed Virtual Routers
Distributing routers across the cloud
Installing and configuring Neutron components
Routing east-west traffic between instances
Centralized SNAT
Floating IPs through distributed virtual routers
Summary
10
Load Balancing Traffic to Instances
Load Balancing Traffic to Instances
Fundamentals of load balancing
Integrating load balancers into the network
Installing LBaaS
Load balancer management in the CLI
Building a load balancer
Load balancer management in the dashboard
Summary
11
Firewall as a Service
Firewall as a Service
Enabling FWaaS
Firewall Management in the CLI
Demonstrating traffic flow through a firewall
Summary
12
Virtual Private Network as a Service
Virtual Private Network as a Service
An overview of IPSec
Installing VPNaaS
VPN management in the CLI
VPN management in the dashboard
A tale of two routers
Summary
Additional Neutron Commands
Additional Neutron Commands
Neutron extensions
Neutron agents
Per-tenant quotas
Cisco Nexus 1000V command reference
VMware NSX command reference
Nuage VSP command reference
L3 metering
The LBaaS v2 API
Summary
Virtualizing the Environment
Virtualizing the Environment
Configuring VirtualBox networking
Creating a virtual machine
Configuring a virtual machine
Installing the Ubuntu operating system
Configuring virtual machine networking
Accessing a virtual machine over SSH
Changes to the OpenStack installation
Summary
Index
Index

Initial network configuration

To understand how networking should initially be configured on each host, refer to the following diagram:

Figure 2.1

In the preceding diagram, three interfaces are cabled to each host. The eth0 interface will serve as the management interface for OpenStack services and API access. The eth1 interface will be used for overlay network traffic between hosts. On the controller node, eth2 will be used for external network traffic to instances through Neutron routers. If VLAN tenant networks are used in lieu of overlay networks such as VXLAN and GRE, then eth2 will be configured on the compute nodes to support those networks.

At a minimum, the management interface should be configured with an IP address that has outbound access to the Internet. Internet access is required to download OpenStack packages from the Ubuntu package repository. Inbound access to the management address of the servers from a trusted network via SSH (TCP port 22) is recommended.

Example networks...

Previous Section
End of Section 3
Next Section