Queries for DVR-aware floating IP next-hop lookups

Bug #1555382 reported by OpenStack Infra on 2016-03-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 2e11d85d6b3be3cf3be0dc988e0dfeb004ebce18
Author: Ryan Tidwell <email address hidden>
Date: Tue Mar 1 07:59:14 2016 -0800

    Queries for DVR-aware floating IP next-hop lookups

    Introduce calls to collect host routes for floating IP's in a
    DVR-aware way. When a floating IP is associated through a
    distributed router, the next-hop for the floating IP is announced
    as the floating IP agent gateway port on the corresponding host.

    Change-Id: I654e4d2496e19c011653eedb87c9b6026f801e9f
    Implements: blueprint bgp-dynamic-routing
    DocImpact: Neutron BGP should have docs created for the feature

tags: added: l3-dvr-backlog
removed: neutron
Changed in neutron:
status: New → Confirmed
tags: removed: l3-dvr-backlog
tags: added: l3-ipam-dhcp
Changed in neutron:
importance: Undecided → High
Miguel Lavalle (minsel) wrote :
Changed in neutron:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers