Reviewed: https://review.openstack.org/283134 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c7e972ce4a5d61cfcdff5b2fc4ba62a94905003a Submitter: Jenkins Branch: master
commit c7e972ce4a5d61cfcdff5b2fc4ba62a94905003a Author: Hong Hui Xiao <[email protected]> Date: Wed Mar 2 03:12:38 2016 -0500 Use floating IP to connect different address scopes Currently, floating ip could be used to connect internal subnet and external subnet in different address scopes. But the internal subnets that are in the same address scope of external network are isolated. This is diagramed as follow: +---------------------+ +------------------------+ | address scope 1 | | address scope 2 | | | | | | +----------------+ | | +---+----------+-+ | | |internal network| | | |external network| | | +------------^---+ | | +-------^--------+ | | | | | | | | +-------+--+ | | +-------+----+ | | |fixed ip A+-------------^+floatingip B| | | +----------+ | | +------------+ | +---------------------+ | | | +--------+ +--------+ | | |internal| |internal| | | +-----+--+ +----+---+ | +------------------------+ This patch will make the fixed ip A be able to connect internal networks in address scope2. And internal networks in address scope2 are able to connect fixed ip A by visiting floating ip B. Change-Id: If3b0b49a994e8c604809e524dca6f4afe5b626f3 Closes-Bug: #1543885 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1543885 Title: Support using floating IP to connect internal subnets in different address scopes Status in neutron: Fix Released Bug description: This is a known limitation when discuss address scope with Carl. In the implementation of [1], floating ip could be used to connect internal subnet and external subnet in different address scopes. But the internal subnets that are in the same address scope of external network are isolated. This is diagramed in [2] Because they are in the same address scope, it is fair for fixed IP A to connect internal networks in address scope 2, just as it could connect to the external network in address scope 2. The target of this bug is to build the connection of fixed IP A and internal networks in address scope2. This is diagramed in [3] [1] https://review.openstack.org/#/c/270001/ [2] http://paste.openstack.org/show/486507/ [3] http://paste.openstack.org/show/486508/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1543885/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
