Chapter 6. Walking through a Networking deployment
This chapter covers
- Network node prerequisites
- Deploying OpenStack Networking core
- Setting up OpenStack Networking ML2 plug-in
- Configuring OpenStack Networking DHCP, Metadata, L3, and OVS agents
In chapter 5 you walked through the deployment of an OpenStack controller node, which provides the server-side management of OpenStack services. During the controller deployment, you made controller-side configurations for several OpenStack core services, including Networking, Compute, and Storage. We discussed the configurations for each core service in relation to the controller, but the services themselves weren’t covered in detail.
Chapters 6 through 8 will walk you through the deployment of core OpenStack services on resource nodes. Resource nodes are nodes that provide a specific resource in relation to an OpenStack service. For instance, a server running OpenStack Compute (Nova) services (and all prerequisite requirements) would be considered a compute resource node. As you learned in chapter 2, it’s possible for a specific node to provide multiple services, including Compute (Nova), Network (Neutron), and Block Storage (Cinder). But just like an exclusive node was used for the controller in chapter 5, exclusive resource nodes will be used for demonstration in chapters 6 (Networking), 7 (Block Storage), and 8 (Compute).
Take another look at the multi-node architecture introduced in chapter 5, shown in figure 6.1.