Description of problem: Packstack should be more descriptive about it's inputs: # A comma separated list of VLAN ranges for the Quantum linuxbridge # plugin CONFIG_QUANTUM_LB_VLAN_RANGES= what is the VLAN range format? 10-50 or 10:50 ? # A comma separated list of interface mappings for the Quantum # linuxbridge plugin CONFIG_QUANTUM_LB_INTERFACE_MAPPINGS= physnet1:eth1 or host1:physnet1:eth1, host2:physnet1:eth1 # Type of network to allocate for tenant networks CONFIG_QUANTUM_LB_TENANT_NETWORK_TYPE=local I would at least showed vlan, local Same should be done for OVS Version-Release number of selected component (if applicable): openstack-packstack-2013.1.1-0.10.dev605.el6ost.noarch How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** Bug 977955 has been marked as a duplicate of this bug. ***
Merged. Moving to MODIFIED.
Auto adding >= MODIFIED bugs to beta
Tested NVR: openstack-packstack-2013.2.1-0.20.dev936.el6ost.noarch generated a packstack answer file. (In reply to Jaroslav Henner from comment #0) > Description of problem: > Packstack should be more descriptive about it's inputs: > > # A comma separated list of VLAN ranges for the Quantum linuxbridge > # plugin > CONFIG_QUANTUM_LB_VLAN_RANGES= > > what is the VLAN range format? 10-50 or 10:50 ? > snipped from the newly generated packstack answer file: # A comma separated list of VLAN ranges for the Neutron linuxbridge # plugin (eg. physnet1:1:4094,physnet2,physnet3:3000:3999) CONFIG_NEUTRON_LB_VLAN_RANGES= > > # A comma separated list of interface mappings for the Quantum > # linuxbridge plugin > CONFIG_QUANTUM_LB_INTERFACE_MAPPINGS= > > physnet1:eth1 or host1:physnet1:eth1, host2:physnet1:eth1 > snipped from the newly generated packstack answer file: # A comma separated list of interface mappings for the Neutron # linuxbridge plugin (eg. physnet1:br-eth1,physnet2:br-eth2,physnet3 # :br-eth3) CONFIG_NEUTRON_LB_INTERFACE_MAPPINGS= > > # Type of network to allocate for tenant networks > CONFIG_QUANTUM_LB_TENANT_NETWORK_TYPE=local > > I would at least showed vlan, local > snipped from the newly generated packstack answer file: # The type of network to allocate for tenant networks (eg. vlan, # local, gre) CONFIG_NEUTRON_LB_TENANT_NETWORK_TYPE=local > > Same should be done for OVS > snipped from the newly generated packstack answer file: # Type of network to allocate for tenant networks (eg. vlan, local, # gre) CONFIG_NEUTRON_OVS_TENANT_NETWORK_TYPE=local # A comma separated list of VLAN ranges for the Neutron openvswitch # plugin (eg. physnet1:1:4094,physnet2,physnet3:3000:3999) CONFIG_NEUTRON_OVS_VLAN_RANGES= # A comma separated list of bridge mappings for the Neutron # openvswitch plugin (eg. physnet1:br-eth1,physnet2:br-eth2,physnet3 # :br-eth3) CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS= # A comma separated list of colon-separated OVS bridge:interface # pairs. The interface will be added to the associated bridge. CONFIG_NEUTRON_OVS_BRIDGE_IFACES= The following parameters should be more descriptive about their inputs as well: # A comma separated list of tunnel ranges for the Neutron openvswitch # plugin CONFIG_NEUTRON_OVS_TUNNEL_RANGES= # Override the IP used for GRE tunnels on this hypervisor to the IP # found on the specified interface (defaults to the HOST IP) CONFIG_NEUTRON_OVS_TUNNEL_IF=
Fixed on this review: https://review.openstack.org/#/c/62974/
Patch reviewed and merged.
Verified NVR: openstack-packstack-2013.2.1-0.22.dev956.el6ost.noarch Following to Comment #8, Verified the descriptions of CONFIG_NEUTRON_OVS_TUNNEL_RANGES and CONFIG_NEUTRON_OVS_TUNNEL_IF Result: ======= # A comma separated list of tunnel ranges for the Neutron openvswitch # plugin (eg. 1:1000) CONFIG_NEUTRON_OVS_TUNNEL_RANGES= # The interface for the OVS tunnel. Packstack will override the IP # address used for GRE tunnels on this hypervisor to the IP found on # the specified interface. (eg. eth1) CONFIG_NEUTRON_OVS_TUNNEL_IF=
doc text set to "-"
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. https://rhn.redhat.com/errata/RHBA-2014-0046.html