Neutron-neutron interconnection

Bug #1750368 reported by Thomas Morin
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
neutron
Opinion
Wishlist
Unassigned

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.

Tags: rfe
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to neutron-specs (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/545826

Revision history for this message
Thomas Morin (tmmorin-orange) wrote :
description: updated
Changed in neutron:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to neutron-specs (master)

Reviewed: https://review.openstack.org/545826
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=2a34abbd25444a1d643324dafe762131e6c0a18c
Submitter: Zuul
Branch: master

commit 2a34abbd25444a1d643324dafe762131e6c0a18c
Author: Thomas Morin <email address hidden>
Date: Mon Feb 19 14:14:58 2018 +0100

    Neutron-Neutron Interconnections

    Proposed specifications for the Neutron-Neutron Interconnections
    RFE.

    Change-Id: I3860a62420ab4983e2b741dff04498fbb0432d00
    Related-Bug: 1750368

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to neutron-specs (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/598986

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to neutron-specs (master)

Reviewed: https://review.openstack.org/598986
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=c97f096695dbceb68fcdb6b07b33f0651bc34bfd
Submitter: Zuul
Branch: master

commit c97f096695dbceb68fcdb6b07b33f0651bc34bfd
Author: ythomas1 <email address hidden>
Date: Fri Aug 31 16:26:50 2018 +0200

    Update Neutron-Neutron Interconnections

    - Move specification for Neutron-Neutron Interconnections RFE for
      implementation in Stein release,
    - Remove redundant states from lifecycle FSM,
    - Add remote_interconnection_id attribute to interconnection resource,
    - Minor update in API exchange example.

    Signed-off-by: Thomas Morin <email address hidden>
    Submitted on behalf of a third-party: Orange

    Change-Id: I30a886813cdca4ed47507bbff38aff2d4137b434
    Related-Bug: 1750368

Revision history for this message
Slawek Kaplonski (slaweq) wrote :

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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.