tripleo-image-elements/elements/neutron-openvswitch-agent
Derek Higgins 1fde418207 Use os-apply-config everywhere
os-config-applier is being deprecated.

Change-Id: Iaaa5e77dcb16f1019e7bace0d6743d51bb61fd1a
2013-11-20 09:12:15 +00:00
..
install.d Quantum -> Neutron rename 2013-07-10 12:45:49 +01:00
neutron-ovs-agent-bin Use os-apply-config everywhere 2013-11-20 09:12:15 +00:00
os-refresh-config Move the metadata NAT rule to nova-baremetal. 2013-08-13 09:12:22 +12:00
README.md Support working with neutron host-routes. 2013-10-14 23:17:13 +13:00
element-deps Quantum -> Neutron rename 2013-07-10 12:45:49 +01:00

README.md

Install and configure OpenStack Networking Openvswitch agent.

Configuration

The physical interface and bridges to use to bridge traffic onto can be configured via Heat Metadata. For example:

neutron:
  ovs:
    public_interface: vlan25
    public_interface_raw_device: eth2
    public_interface_route: 12.34.56.78
    physical_bridge: br-ctlplane
    physical_network: ctlplane
    network_vlan_ranges: ctlplane
    bridge_mappings: ctlplane:br-ctlplane

If public_interface and physical_bridge are not set, no bridges will be connected directly. This is normal for neutron hosting virtual machines when using an overlay network (e.g. GRE tunnelling). Some of the other fields will be ignored in this case. Most of them map 1:1 with their counterparts in the OVS section of ovs_neutron_plugin.ini If public_interface_raw_device is set, public_interface must be a vlan device, and the vlan device will be created using the raw device during os-collect-config configuration.

Once the public interface is configured, public_interface_route (if set) will replace the default route's next hop. The hop this replaces will be added as the next hop for 169.254.169.254/32 (unless one already exists). This permits routing default traffic out through a hardware router without breaking the ability to contact a bare metal metadata server.