[RFE] Floating IP Subnets on Routed Provider Networks

Bug #1667329 reported by John Davidge
42
This bug affects 5 people
Affects Status Importance Assigned to Milestone
neutron
In Progress
Wishlist
Thomas Goirand

Bug Description

This RFE proposes an enhancement to the Routed Provider Networks[1][2] feature to allow the creation of Floating IP subnets. The planned implementation will leverage the BGP Dynamic Routing[3] and Service Subnets[4] features to achieve this.

Problem Description
===================

Currently, all subnets on a Routed Network are required to belong to a segment, which typically corresponds to the physical rack on which all VMs for the subnet will be provisioned. This doesn't make sense for a Floating IP subnet, which will not be associated with a neutron segment as its address range will span more than a single rack. Additionally, no mechanism currently exists to provide routing from a floating IP to a specific Routed Network Segment.

Proposed Solution
=================

To solve the first part of the problem, Service Subnets[4] will be used to allow a Floating IP subnet to be created on a Routed Network without the need for subnet/segment association. Specifically, a subnet with service_type "network:floating_ip" will not be subject to the segment association check.

To solve the second part, BGP Dynamic Routing[3] will be used to advertise the ToR for the relevant segment as the next-hop for assigned Floating IPs. This will require enhancing the BGP Agent to be segment-aware, rather than just network-aware.

[1] https://specs.openstack.org/openstack/neutron-specs/specs/newton/routed-networks.html
[2] https://docs.openstack.org/newton/networking-guide/config-routed-networks.html
[3] https://docs.openstack.org/newton/networking-guide/config-bgp-dynamic-routing.html
[4] https://docs.openstack.org/newton/networking-guide/config-service-subnets.html

Changed in neutron:
status: New → Triaged
Changed in neutron:
importance: Undecided → Wishlist
tags: added: rfe-approved
removed: rfe
Revision history for this message
Miguel Lavalle (minsel) wrote :

As discussed today in the drivers meeting, next step is a spec and a blue print (e.g. https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch)

Changed in neutron:
assignee: nobody → John Davidge (john-davidge)
Miguel Lavalle (minsel)
Changed in neutron:
assignee: John Davidge (john-davidge) → Miguel Lavalle (minsel)
Changed in neutron:
status: Triaged → In Progress
Changed in neutron:
assignee: Miguel Lavalle (minsel) → Ryan Tidwell (ryan-tidwell)
Revision history for this message
Javier Diaz Jr (javierdiazcharles) wrote :

Any progress or ETAs on this RFE?

Revision history for this message
Ryan Tidwell (ryan-tidwell) wrote :

See https://review.opendev.org/#/c/486450/ for design details that are being hashed out. I'm in the process of proposing an initial patch for this, look for it shortly. This initial patch will demonstrate what I'm proposing in the design spec. Reviews on https://review.opendev.org/#/c/486450/ would be greatly appreciated.

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

Fix proposed to branch: master
Review: https://review.opendev.org/669395

Revision history for this message
Takashi Sogabe (sogabe) wrote :

Are there any blockers around the RFE?
I evaluated the configuration by using devstack with PoC code. It seems work well and should be a little impact for upstream code.

Takashi Sogabe (sogabe)
information type: Public → Public Security
information type: Public Security → Private Security
information type: Private Security → Public
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.opendev.org/741429

Changed in neutron:
assignee: Ryan Tidwell (ryan-tidwell) → Thomas Goirand (thomas-goirand)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by Thomas Goirand (<email address hidden>) on branch: master
Review: https://review.opendev.org/741429

Changed in neutron:
assignee: Thomas Goirand (thomas-goirand) → Rodolfo Alonso (rodolfo-alonso-hernandez)
Changed in neutron:
assignee: Rodolfo Alonso (rodolfo-alonso-hernandez) → Thomas Goirand (thomas-goirand)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to neutron-lib (master)

Reviewed: https://review.opendev.org/741607
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=b64d4e2423da8b1664ec632a849b4d8c0892e20e
Submitter: Zuul
Branch: master

commit b64d4e2423da8b1664ec632a849b4d8c0892e20e
Author: Thomas Goirand <email address hidden>
Date: Fri Jul 17 11:38:37 2020 +0200

    Add DEVICE_OWNER_ROUTED constant

    This patch adds the DEVICE_OWNER_ROUTED constant.

    Related-Bug: #1667329
    Change-Id: Ibde33bdacba6bd1e9c41cc69d0054bf55e1e6454

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

Reviewed: https://review.opendev.org/486450
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=3f584dc9b72fb883d82296dad7c413e51fd45b15
Submitter: Zuul
Branch: master

commit 3f584dc9b72fb883d82296dad7c413e51fd45b15
Author: Miguel Lavalle <email address hidden>
Date: Sun Jul 23 19:38:13 2017 -0500

    Floating IP's for routed networks

    This specification proposes to add functionality that allows users to
    associate floating IPs to ports of routed networks

    Partial-Bug #1667329

    Change-Id: Id07f52da9fff321827aff8be11614a347030bb04

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers