Jump to: navigation, search


Revision as of 14:23, 13 September 2016 by Hirofumi Ichihara (talk | contribs)

The OpenStack Networking Team (Neutron) holds public meetings as advertised on OpenStack IRC Meetings Calendar. If you are unable to attend, please check the most recent logs.

Announcements / Reminders


Current milestone: https://launchpad.net/neutron/+milestone/newton-rc1

Bugs and Gate failures

Approximate stats for the current cycle:

  • From Newton beginning (Mar-16-2016):
    • Total reports: 789
      • Fix released: 308
      • Unassigned: 104
        • New: 39
        • Incomplete: 30
        • Confirmed: 26
        • Triaged: 10

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.

Previous deputies in order per week: iharchys, regXboi, markmcclain, armax, mestery, mangelajo, garyk, rosella_s, dougwig, HenryG, carl_baldwin, amotoki, kevinbenton, amuller, Zzelle, mlavalle, njohnston, mhickey, rosella_s, dasm, scheuran, HenryG, Amotoki, reedip, blogan, dougwig, armax, regXboi, haleyb, hichihara, carl_baldwin

Next weeks:

Date who
May-30-2016 kevinbenton
Jun-6-2016 mangelajo
Jun-13-2016 dasm
Jun-20-2016 john-davidge
Jun-27-2016 rossella_s
Jul-4-2016 johndperkins
Jul-11-2016 blogan
Jul-18-2016 mlavalle
Jul-25-2016 jlibosva
Aug-01-2016 electrocucaracha
Aug-08-2016 njohnston
Aug-15-2016 armax
Aug-30-2016 haleyb
Sep-04-2016 jschwarz
Sep-12-2016 hichihara
Sep-19-2016 ihrachys


Transition to OSC

Status of changes to deliver OSC

Moving to Keystone v3 API in Neutron


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:

  • Feature Classification Framework/Matrix
  • Let operator update subnet.cidr:
    • yottatsa: as an operator I want to expand or shrink Public network without re-allocating all Floating IPs.
  • Transaction guards on *_port methods, and l3 service plugins.
    • oanson: create_port, update_port, and delete_port have a transaction guard which breaks existing l3 service plugins. There is a workaround (GUARD_TRANSACTION=false), but what is the long-term solution?
      • I understand that GUARD_TRANSACTION=false is a workaround. What would be the correct solution to continue using port modification functions on the core plugin in case of transactions in the service plugin code, or how to correct the client code? I ran into this in Dragonflow, but I have seen it in Midonet as well. Neutron change: https://review.openstack.org/#/c/275110/ , Dragonflow change: https://review.openstack.org/#/c/355736/ .
  • Distributed gateway for optimized local SNAT
  • Topic for the meeting (keep this template, please):
    • (your nickname): brief description.
      • More details

Previous meeting logs