Install and configure the Networking components on the controller node.
# apt-get install neutron-server neutron-plugin-linuxbridge-agent \
neutron-dhcp-agent neutron-metadata-agent
For networking option 2, also install the neutron-l3-agent
package.
Respond to prompts for database management, Identity service credentials, service endpoint registration, and message queue credentials.
Select the ML2 plug-in:
Note
Selecting the ML2 plug-in also populates the service_plugins
and
allow_overlapping_ips
options in the
/etc/neutron/neutron.conf
file with the appropriate values.
The ML2 plug-in uses the Linux bridge mechanism to build layer-2 (bridging and switching) virtual networking infrastructure for instances.
Edit the /etc/neutron/plugins/ml2/ml2_conf.ini
file and complete the
following actions:
In the [ml2]
section, enable flat, VLAN, and VXLAN networks:
[ml2]
...
type_drivers = flat,vlan,vxlan
In the [ml2]
section, enable VXLAN self-service networks:
[ml2]
...
tenant_network_types = vxlan
In the [ml2]
section, enable the Linux bridge and layer-2 population
mechanisms:
[ml2]
...
mechanism_drivers = linuxbridge,l2population
Warning
After you configure the ML2 plug-in, removing values in the
type_drivers
option can lead to database inconsistency.
Note
The Linux bridge agent only supports VXLAN overlay networks.
In the [ml2]
section, enable the port security extension driver:
[ml2]
...
extension_drivers = port_security
In the [ml2_type_flat]
section, configure the provider virtual
network as a flat network:
[ml2_type_flat]
...
flat_networks = provider
In the [ml2_type_vxlan]
section, configure the VXLAN network identifier
range for self-service networks:
[ml2_type_vxlan]
...
vni_ranges = 1:1000
In the [securitygroup]
section, enable ipset to increase
efficiency of security group rules:
[securitygroup]
...
enable_ipset = True
The Linux bridge agent builds layer-2 (bridging and switching) virtual networking infrastructure for instances and handles security groups.
Edit the /etc/neutron/plugins/ml2/linuxbridge_agent.ini
file and
complete the following actions:
In the [linux_bridge]
section, map the provider virtual network to the
provider physical network interface:
[linux_bridge]
physical_interface_mappings = provider:PROVIDER_INTERFACE_NAME
Replace PROVIDER_INTERFACE_NAME
with the name of the underlying
provider physical network interface. See Host networking
for more information.
In the [vxlan]
section, enable VXLAN overlay networks, configure the
IP address of the physical network interface that handles overlay
networks, and enable layer-2 population:
[vxlan]
enable_vxlan = True
local_ip = OVERLAY_INTERFACE_IP_ADDRESS
l2_population = True
Replace OVERLAY_INTERFACE_IP_ADDRESS
with the IP address of the
underlying physical network interface that handles overlay networks. The
example architecture uses the management interface to tunnel traffic to
the other nodes. Therefore, replace OVERLAY_INTERFACE_IP_ADDRESS
with
the management IP address of the controller node. See
Host networking for more information.
In the [securitygroup]
section, enable security groups and
configure the Linux bridge iptables firewall driver:
[securitygroup]
...
enable_security_group = True
firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver
The Layer-3 (L3) agent provides routing and NAT services for self-service virtual networks.
Edit the /etc/neutron/l3_agent.ini
file and complete the following
actions:
In the [DEFAULT]
section, configure the Linux bridge interface driver
and external network bridge:
[DEFAULT]
...
interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver
external_network_bridge =
Note
The external_network_bridge
option intentionally lacks a value
to enable multiple external networks on a single agent.
The DHCP agent provides DHCP services for virtual networks.
Edit the /etc/neutron/dhcp_agent.ini
file and complete the following
actions:
In the [DEFAULT]
section, configure the Linux bridge interface driver,
Dnsmasq DHCP driver, and enable isolated metadata so instances on provider
networks can access metadata over the network:
[DEFAULT]
...
interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver
dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq
enable_isolated_metadata = True
Return to Networking controller node configuration.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.