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.6 KiB
Networking Option 2: Self-service 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.inifile 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_NAMEReplace
PROVIDER_INTERFACE_NAMEwith the name of the underlying provider physical network interface. Seeenvironment-networking-obsfor 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 = trueReplace
OVERLAY_INTERFACE_IP_ADDRESSwith 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, replaceOVERLAY_INTERFACE_IP_ADDRESSwith the management IP address of the compute node. Seeenvironment-networking-obsfor 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.IptablesFirewallDriverEnsure your Linux operating system kernel supports network bridge filters by verifying all the following
sysctlvalues are set to1:net.bridge.bridge-nf-call-iptables net.bridge.bridge-nf-call-ip6tablesTo enable networking bridge support, typically the
br_netfilterkernel module needs to be loaded. Check your operating system's documentation for additional details on enabling this module.
Return to Networking compute node configuration.