yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1750368@xxxxxxxxxxxxxxxxxx>]

Due to lack of activity neutron-interconnection project was some time ago moved from Neutron stadium to the x/ namespace.
So I think that we can close this RFE as "abandoned" now.

** Changed in: neutron
       Status: Confirmed => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1750368

Title:
  Neutron-neutron interconnection

Status in neutron:
  Opinion

Bug description:
  Today, to realize connectivity between two OpenStack clouds (e.g. two
  distinct OpenStack deployments, or two OpenStack regions, for
  instance) some  options are available, such as floating IPs, VPNaaS
  (IPSec-based), and BGPVPNs.

  However, none of these options are appropriate to address use cases where all
  the following properties are desired:

  * interconnection consumable on-demand, without admin intervention
  (possible with floating IPs, VPNaaS, but not with the BGP VPN
  interconnections API extension)

  * have network isolation and allow the use of private IP addressing
  end-to-end (possible with VPNaaS, and BGP VPN interconnections, but
  not with floating IPs)

  * avoid the overhead of packet encryption (possible with floating IPs,
  and BGP VPN interconnections, but by construction not with VPNaaS)

  The goal of this RFE is to propose a solution to provide network connectivity
  between two or more OpenStack deployments or regions, respecting these
  constraints.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1750368/+subscriptions