Description of problem: My answer file includes the following: CONFIG_NEUTRON_OVS_TENANT_NETWORK_TYPE=gre CONFIG_NEUTRON_OVS_VLAN_RANGES=physnet1 CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=physnet1:br-eth1 CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-eth1:eth1 CONFIG_NEUTRON_OVS_TUNNEL_RANGES=1:1000 My intent is to use GRE tunnels for tenant networks, but use a VLAN on eth1 for my external network. The installation completed, and configuration for the tenant GRE tunnels looks correct, but the configuration for the physical network was ignored. Version-Release number of selected component (if applicable): openstack-packstack.noarch 2013.2.1-0.9.dev756.el6 @openstack-havana How reproducible: every time Steps to Reproduce: 1. Run packstack with options above 2. Examine configuration for server and agents 3. Try to create a provider network using physnet1 Actual results: On the server node, /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini does not contain network_vlan_ranges. On the nodes where neutron-openvswitch-agent runs, /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini does not contain bridge_mappings, and br-eth1 has not been created. Provider external network cannot be created because physnet1 is not known. Expected results: On the server node, /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini should contain: "network_vlan_ranges = physnet1". On the nodes where neutron-openvswitch-agent runs, /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini should contain "bridge_mappings=physnet1:br-eth1", and the br-eth1 OVS bridge should be created with eth1 added as a port. Additional info: N/A
CONFIG_NEUTRON_OVS_VLAN_RANGES, CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS and CONFIG_NEUTRON_OVS_BRIDGE_IFACES parameters are filled only if CONFIG_NEUTRON_OVS_TENANT_NETWORK_TYPE=vlan so actually this is a feature.
This is a bug, not a feature. All network types can be used for provider networks (including provider external networks), regardless of which network type is selected for tenant networks. Using vlan or flat provider networks still requires network_vlan_ranges and bridge_mappings to be set. So these packstack config items need to work normally even when CONFIG_NEUTRON_OVS_TENANT_NETWORK_TYPE is not 'vlan'. Also, this bug looks like a copy/clone of https://bugzilla.redhat.com/show_bug.cgi?id=1006534, which I filed originally against RDO, and is currently being worked on. -Bob
AFAIK, Terry is already working on the RDO's version of the bug.
A patch for this was already merged ~10 days ago.
tested, seems working fine openstack-packstack-2013.2.1-0.13.dev876.el6ost.noarch [OVS] network_vlan_ranges=inter-vlan:195:203 local_ip=55.55.55.19 enable_tunneling=True integration_bridge=br-int tunnel_id_ranges=1:1000 tunnel_bridge=br-tun tenant_network_type=gre bridge_mappings=inter-vlan:br-eth3
Slight clarification to the doc text.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1859.html