Jump to: navigation, search


'Meeting time: The OpenStack Networking Team (Neutron) holds public meetings alternating between Mondays at 2100 UTC (#openstack-meeting) and Tuesdays at 1400 UTC (#openstack-meeting). Everyone is encouraged to attend.

Announcements / Reminders

  • No meeting Jan 4th, 2016


Current milestone: https://launchpad.net/neutron/+milestone/mitaka-2 (ends Jan 16 2016)


Approximate stats for the current cycle:

  • From Mitaka beginning (Sep-23-2015) (last recurrence in parenthesis):
    • Total reports: 538 (503)
      • Fix released: 232 (222)
      • Unassigned: 79 (79)
        • New: 17 (18)
        • Incomplete: 19 (24)
        • Confirmed: 28 (22)
        • Triaged: 6 (8)
  • For last week:
    • Total reports: 44 (55)
      • Fix released: 6 (8)
      • Unassigned: 14 (15)
        • New: 5 (10)
        • Incomplete: 2 (0)
        • Confirmed: 6 (1)
        • Triaged: 0 (0)

Bug deputy

Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.

Date ihrachys regXboi markmcclain armax mestery mangelajo garyk rossella_s dougwig HenryG carl_baldwin amotoki kevinbenton amuller
Oct-05-2015 x
Oct-12-2015 x
Oct-19-2015 x
Oct-24-2015 x
Nov-02-2015 x
Nov-09-2015 x
Nov-16-2015 x
Nov-23-2015 x
Nov-30-2015 x
Dec-07-2015 x
Dec-14-2015 x
Dec-21-2015 x
Dec-28-2015 x
Jan-04-2016 x


  • Discuss proofing devref and spec patches. (Sam-I-Am)

Open Items for Liberty: (reviews needed)

Networking Guide

On Demand Agenda

We can only pick one or two topics we can talk in the time left of the meeting. People should add ideas to the topics section. We will select one or two topics we can chew during the next meeting. Please follow the template below:

  • Topic for the meeting:
    • Pagination support in the agents, Brian Haley, Dec 17th
      • There are currently two reviews adding "pagination" to the RPC calls to sync networks and routers on the DHCP and L3 agents (respectively). One has chosen a config variable, the other has chosen a large number, with backoff logic on failure. We need to discuss a common way these can move forward so we don't have two different solutions for the same problem. Brian (haleyb) might not be available Monday, but Zhi Chang and Oleg Bondarev are the respective authors.
        • https://review.openstack.org/#/c/234067/
        • https://review.openstack.org/#/c/257100/
          • <armax> IMO, consistency is paramount; besides the config variable approach has been shot down a few times before and the patch is blocked since it's a duplicate. To prevent these from happening, I think we should wrap this into some sort of utility method, but it's probably best to have fixes to the related issues merged separately, and reconcile them later (in whichever shape they end up being)

    • Live Migration Notifiers for Nova/Neutron, Swaminathan Vasudevan, Jan 4th 2016
      • Nova VM instances can migrate from one compute host to another compute host. When Nova VM migrates,

there is no notification messages sent to neutron and also nova migration task manager does not verify if the destination host has all L3 networking setup in place. Because of this issue, we are seeing issues with VM migration having L3 connectivity, especially with DVR routers, since DVR routers create routers on demand in a reactive manner. We have been discussing this issue with respect to a launchpad bug and also have a couple of patches up for review.

This work requires a joint effort from Nova and Neutron team to fix this problem. I would like to get the Neutron teams feedback on this and to assign a core team to work on this feature.

Previous meeting logs