yahoo-eng-team team mailing list archive

[Hong Hui Xiao <xiaohhui@xxxxxxxxxx>]

Public bug reported:

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/

** Affects: neutron
     Importance: Undecided
     Assignee: Hong Hui Xiao (xiaohhui)
         Status: New


** Tags: address-scopes

** Tags added: address-scopes

** Changed in: neutron
     Assignee: (unassigned) => Hong Hui Xiao (xiaohhui)

-- 
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:
  New

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