Jump to: navigation, search


Revision as of 03:26, 5 November 2016 by Armax (talk | contribs) (Announcements / Reminders)

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

  • neutron-lib 1.0.0 is released
  • check out for design summit recaps on the ML


Current milestone: https://launchpad.net/neutron/+milestone/ocata-1

OVO/no API downtime

List here patches/topics that need core reviewer attention.

Bugs and Gate failures

Approximate stats for the current cycle:

  • From the beginning of Ocata (Sept-16-2016):
    • Total reports: 155
      • Fix released: 43
      • Unassigned: 60
        • New: 11
        • Incomplete: 14
        • Confirmed: 13
        • Triaged: 7

Bug deputy

Use this section to keep track of who volunteers for the 'bug deputy' role. Instructions and pointers available at:


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, kevinbenton, mangelajo, dasm, john-davidge, rossella_s, johndperkins, blogan, mlavalle, jlibosva

Next weeks:

Date who
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
Sep-26-2016 ihrachys
Oct-3-2016 dougwig
Oct-10-2016 john-davidge
Oct-17-2016 dasanind_
Oct-24-2016 dasm
Oct-31-2016 dougwig


Transition to OSC

Status of changes to deliver OSC

Neutron-lib and planned neutron refactoring

List here any planned potential disruption that may be caused by a new neutron-lib release.

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 (keep this template, please):
    • (your nickname): brief description.
      • More details
  • Deprecation policy
    • dasm: Tests for deprecated code
      • There are two types of deprecation: when implementation will be removed and when implementation of function was moved to other library: oslo-lib, neutron-lib. What should happen with tests for that? In the first case, code should be still tested. In the second case, should we leave test to verify presence of deprecated code, or should we remove it, because code is tested in external library?

Previous meeting logs