Bug 1003120

Summary: Add support for GRE networks
Product: Red Hat OpenStack Reporter: Terry Wilson <twilson>
Component: openstack-packstackAssignee: Terry Wilson <twilson>
Status: CLOSED ERRATA QA Contact: Nir Magnezi <nmagnezi>
Severity: high Docs Contact:
Priority: high    
Version: 3.0CC: aortega, derekh, hateya, mmagr, sclewis, sradvan, yeylon
Target Milestone: beta   
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-packstack-2013.2.1-0.5.dev740.el6ost Doc Type: Enhancement
Doc Text:
Feature: Add support for GRE networks.
Story Points: ---
Clone Of:
: 1004397 (view as bug list) Environment:
Last Closed: 2013-12-20 00:22:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1004397    

Description Terry Wilson 2013-08-30 21:47:10 UTC
Packstack currently doesn't support setting up GRE networks. Since OVS GRE-supported kernels are now available, support for them should be added to packstack.

Comment 2 Terry Wilson 2013-09-04 14:13:03 UTC
To test,

packstack --allinone --quantum-ovs-tunnel-ranges=1:1000 --quantum-ovs-tenant-network-type=gre

or, make sure that the answer file contains
CONFIG_QUANTUM_OVS_TUNNEL_RANGES=1:1000
CONFIG_QUANTUM_OVS_TENANT_NETWORK_TYPE=gre

s/quantum/neutron/ for havana.

Comment 3 Nir Magnezi 2013-10-21 09:28:50 UTC
Verified NVR: openstack-packstack-2013.2.1-0.6.dev763.el6ost.noarch

Installed OpenStack via packstack as follows:
# packstack --allinone --neutron-ovs-tunnel-ranges=1:1000 --neutron-ovs-tenant-network-type=gre -d

Result:
=======
1. snipped from /etc/neutron/plugin.ini

[OVS]
local_ip=<IP>
tunnel_id_ranges=1:1000
tunnel_bridge=br-tun
integration_bridge=br-int
enable_tunneling=True
tenant_network_type=gre

2. Networking team tested and confirmed that GRE tunneling works properly.

Comment 5 errata-xmlrpc 2013-12-20 00:22:40 UTC
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