Comment 4 for bug 1543885

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 address hidden>
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