Previously in all our install guides there were info that name of the physical interface should be put in the bridge_mappings config option in ths OVS agent's config. This wasn't correct as bridge_mappings expects there bridge name instead. Change-Id: I0698aa4621a15c1927ad2c352501cea02e6ee70c
2.2 KiB
Networking Option 1: Provider networks
Configure the Networking components on a compute node.
Configure the Open vSwitch agent
The Open vSwitch agent builds layer-2 (bridging and switching) virtual networking infrastructure for instances and handles security groups.
- Edit the
/etc/neutron/plugins/ml2/openvswitch_agent.inifile and complete the following actions:In the
[ovs]section, map the provider virtual network to the provider physical bridge:[ovs] bridge_mappings = provider:PROVIDER_BRIDGE_NAMEReplace
PROVIDER_BRIDGE_NAMEwith the name of the bridge connected to the underlying provider physical network. Seeenvironment-networking-ubuntuand../admin/deploy-ovs-providerfor more information.Ensure
PROVIDER_BRIDGE_NAMEexternal bridge is created andPROVIDER_INTERFACE_NAMEis added to that bridge# ovs-vsctl add-br $PROVIDER_BRIDGE_NAME # ovs-vsctl add-port $PROVIDER_BRIDGE_NAME $PROVIDER_INTERFACE_NAMEIn 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_hybridIn the case of using the hybrid iptables firewall driver, ensure 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