Provider router with private networks

This section describes how to install the OpenStack Networking service and its components for a single router use case: a provider router with private networks.

This figure shows the set up:

[Note]Note

Because you run the DHCP agent and L3 agent on one node, you must set use_namespaces to True (which is the default) in the configuration files for both agents.

The configuration includes these nodes:

Table 9.1. Nodes for use case
Node Description

Controller

Runs the Networking service, Identity Service, and all Compute services that are required to deploy a VM.

The service must have at least two network interfaces. The first should be connected to the Management Network to communicate with the compute and network nodes. The second interface should be connected to the API/public network.

Compute

Runs Compute and the Networking L2 agent.

This node does not have access the public network.

The node must have a network interface that communicates with the controller node through the management network. The VM receives its IP address from the DHCP agent on this network.

Network

Runs Networking L2 agent, DHCP agent, and L3 agent.

This node has access to the public network. The DHCP agent allocates IP addresses to the VMs on the network. The L3 agent performs NAT and enables the VMs to access the public network.

The node must have:

  • A network interface that communicates with the controller node through the management network

  • A network interface on the data network that manages VM traffic

  • A network interface that connects to the external gateway on the network

Log a bug against this page


loading table of contents...