Networking Option 1: Provider networks¶
Install and configure the Networking components on the controller node.
Install the components¶
# apt install neutron-server neutron-plugin-ml2 \
neutron-openvswitch-agent neutron-dhcp-agent \
neutron-metadata-agent
Configure the server component¶
The Networking server component configuration includes the database, authentication mechanism, message queue, topology change notifications, and plug-in.
Note
Default configuration files vary by distribution. You might need
to add these sections and options rather than modifying existing
sections and options. Also, an ellipsis (...
) in the configuration
snippets indicates potential default configuration options that you
should retain.
Edit the
/etc/neutron/neutron.conf
file and complete the following actions:In the
[database]
section, configure database access:[database] # ... connection = mysql+pymysql://neutron:NEUTRON_DBPASS@controller/neutron
Replace
NEUTRON_DBPASS
with the password you chose for the database.Note
Comment out or remove any other
connection
options in the[database]
section.In the
[DEFAULT]
section, enable the Modular Layer 2 (ML2) plug-in and disable additional plug-ins:[DEFAULT] # ... core_plugin = ml2 service_plugins =
In the
[DEFAULT]
section, configureRabbitMQ
message queue access:[DEFAULT] # ... transport_url = rabbit://openstack:RABBIT_PASS@controller
Replace
RABBIT_PASS
with the password you chose for theopenstack
account in RabbitMQ.In the
[DEFAULT]
and[keystone_authtoken]
sections, configure Identity service access:[DEFAULT] # ... auth_strategy = keystone [keystone_authtoken] # ... www_authenticate_uri = http://controller:5000 auth_url = http://controller:5000 memcached_servers = controller:11211 auth_type = password project_domain_name = Default user_domain_name = Default project_name = service username = neutron password = NEUTRON_PASS
Replace
NEUTRON_PASS
with the password you chose for theneutron
user in the Identity service.Note
Comment out or remove any other options in the
[keystone_authtoken]
section.In the
[DEFAULT]
and[nova]
sections, configure Networking to notify Compute of network topology changes:[DEFAULT] # ... notify_nova_on_port_status_changes = true notify_nova_on_port_data_changes = true [nova] # ... auth_url = http://controller:5000 auth_type = password project_domain_name = Default user_domain_name = Default region_name = RegionOne project_name = service username = nova password = NOVA_PASS
Replace
NOVA_PASS
with the password you chose for thenova
user in the Identity service.
In the
[oslo_concurrency]
section, configure the lock path:[oslo_concurrency] # ... lock_path = /var/lib/neutron/tmp
Configure the Modular Layer 2 (ML2) plug-in¶
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 and VLAN networks:[ml2] # ... type_drivers = flat,vlan
In the
[ml2]
section, disable self-service networks:[ml2] # ... tenant_network_types =
In the
[ml2]
section, enable the Linux bridge mechanism:[ml2] # ... mechanism_drivers = openvswitch
Warning
After you configure the ML2 plug-in, removing values in the
type_drivers
option can lead to database inconsistency.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
Configure the Open vSwitch agent¶
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/openvswitch_agent.ini
file and complete the following actions:In the
[ovs]
section, map the provider virtual network to the provider physical network interface:[ovs] bridge_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
[securitygroup]
section, enable security groups and configure the Open vSwitch native or the hybrid iptables firewall driver:[securitygroup] # ... enable_security_group = true firewall_driver = openvswitch #firewall_driver = iptables_hybrid
In the case of using the hybrid iptables firewall driver, ensure your Linux operating system kernel supports network bridge filters by verifying all the following
sysctl
values are set to1
:net.bridge.bridge-nf-call-iptables net.bridge.bridge-nf-call-ip6tables
To enable networking bridge support, typically the
br_netfilter
kernel module needs to be loaded. Check your operating system’s documentation for additional details on enabling this module.
Configure the DHCP 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 = openvswitch dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq enable_isolated_metadata = true
Create the provider network¶
Follow this provider network document from the General Installation Guide.
Return to Networking controller node configuration.