Some init_router_port steps are unnecessary for new devices

Bug #2043558 reported by Adam Oswick
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
In Progress
Medium
Adam Oswick

Bug Description

Summary
-------
When doing the init for new router ports, some of the steps are not needed and just add extra overhead.

Description
-----------
These unnecessary steps slow down the router setup. If the entire network is being setup from scratch, this can increase the time it takes for VMs to become reachable.

Pre-conditions
--------------
The Neutron L3 agent is attempting to setup a router for the first time or from scratch (e.g. following a complete removal of the qrouter & fip namespaces). For replication purposes, this should be a router with a large number of subnets attached (~100).

Step by step reproduction steps
-------------------------------
On a compute node with DVR:

ip netns delete $QROUTER_NETNS && ip netns delete $FIP_NETNS && docker restart neutron_l3_agent

Note: How the agent is restarted will of course depend on how OpenStack is being deployed.

Expected output
---------------
Unnecessary steps for new interfaces are skipped.

Actual output
-------------
Unnecessary steps for new interfaces are carried out but result in no changes and delay the router setup being completed.

Version
-------
OpenStack Antelope

Adam Oswick (adamoswick)
Changed in neutron:
assignee: nobody → Adam Oswick (adamoswick)
Changed in neutron:
status: New → In Progress
Revision history for this message
Jakub Libosvar (libosvar) wrote :
tags: added: l3-dvr-backlog
Changed in neutron:
importance: Undecided → Medium
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.