Bug 1046070

Summary: Configurable External Gateway Modes
Product: Red Hat OpenStack Reporter: Scott Lewis <sclewis>
Component: openstack-neutronAssignee: Assaf Muller <amuller>
Status: CLOSED ERRATA QA Contact: Ofer Blaut <oblaut>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: chrisw, dnavale, lpeer, mlopes, sradvan, twilson, yeylon
Target Milestone: z1Keywords: FutureFeature, Reopened, ZStream
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/neutron/+spec/l3-ext-gw-modes
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Previously, instances connected to tenant networks gained outside connectivity by going through an SNAT by the L3 agent hosting that network's virtual router. With this release, the ability to disable SNAT/PAT on virtual servers is added ensuring that an instance in a tenant network subnet will retain its IP address as it passes through external networks. For example, if 10.0.0.1 is an instance in the 10.0.0.0/8 tenant network, R1, a virtual router that connects the 10.0.0.0/8 subnet to the 20.0.0.0/8 public provider networks, then you can use the 'neutron router-gateway-set --disable-snat R1 public' command and any traffic from 10.0.0.1, which is forwarded out to the provider network will retain its actual source IP address of 10.0.0.1. This can be a flexible and useful method to connect instances directly to a provider network, while retaining it in a tenant network.
Story Points: ---
Clone Of: 989626 Environment:
Last Closed: 2014-01-22 18:32:39 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:
Embargoed:
Bug Depends On: 989626, 1010323    
Bug Blocks: 975499    

Comment 1 Assaf Muller 2013-12-31 09:13:22 UTC
Works in latest RHOS.

Comment 2 Assaf Muller 2013-12-31 11:35:00 UTC
Works in RHOS 4.0.

Comment 5 errata-xmlrpc 2014-01-22 18:32:39 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/RHSA-2014-0091.html