This patch updates our install documentation to account for the fact that linux systems must have net.bridge sysctl knobs. Change-Id: I8b65e2ef22d57cd6c501f25a33af8c1900f20497 Closes-Bug: #1672922
2.0 KiB
Networking Option 1: Provider networks
Configure the Networking components on a compute node.
Configure the Linux bridge 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/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. Seeenvironment-networking-rdo
for more information.In the
[vxlan]
section, disable VXLAN overlay networks:[vxlan] enable_vxlan = false
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
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.
Return to Networking compute node configuration