Bug 1255112
| Summary: | [RFE][Neutron] Backport add onlink route when multiple external subnets | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Jon Schlueter <jschluet> |
| Component: | openstack-neutron | Assignee: | lpeer <lpeer> |
| Status: | CLOSED ERRATA | QA Contact: | Itzik Brown <itbrown> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.0 | CC: | amuller, chrisw, dcadzow, ebarrera, ihrachys, jschluet, lpeer, lyarwood, mkolesni, mlopes, nyechiel, oblaut, sputhenp, tfreger, yeylon |
| Target Milestone: | z5 | Keywords: | FeatureBackport, FutureFeature, Triaged, ZStream |
| Target Release: | 5.0 (RHEL 6) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-neutron-2014.1.4-3.el6ost | Doc Type: | Enhancement |
| Doc Text: |
Previously, when using multiple subnets on an external network, traffic from one subnet to the other would be forwarded through the upstream router first.
This resulted in massive inefficiency, to the point that adoption of the concept of multiple subnets on an external network was hindered.
This update addresses this issue by adding an on-link route to each subnet.
As a result, a router connected to an external network is attached to one subnet, thus having one IP address (even if that network has multiple subnets). With this fix, the router will still consume an IP address from only subnet, but also has an on-link route to all subnets on the network.
|
Story Points: | --- |
| Clone Of: | 1185200 | Environment: | |
| Last Closed: | 2015-09-10 11:51:54 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: | 1185200 | ||
| Bug Blocks: | 1188003 | ||
|
Comment 3
Itzik Brown
2015-09-01 09:35:07 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. https://rhn.redhat.com/errata/RHBA-2015-1755.html |