Jump to: navigation, search

Network/Meetings

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

Blueprints

Train-1 blueprints: https://launchpad.net/neutron/+milestone/train-1

Patches up for review:

Community Goals

This slot is to used to track the progress of the community goals. https://governance.openstack.org/tc/goals/index.html#release-cycles

Starter Approved RFEs

This section is for advertising approved RFEs that the Neutron Drivers team have deemed suitable for new contributors:

Bugs and Gate issues

Bug deputy report for week of May 13th: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006410.html and http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006429.html

More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI

Bug deputy

You can find more information about what the role is here: https://docs.openstack.org/neutron/latest/contributor/policies/bugs.html#neutron-bug-deputy

During the Denver PTG we made the decision to institute a fixed rotation for the the bugs deputy role. The current scheduled rotation is the following:

Date who
April-1-2019 Bernard Cafarelli (bcafarel)
April-8-2019 Slawek Kaplonski (slaweq)
April-15-2019 Hongbin Lu (hongbin)
April-22-2019 Boden Russel (boden)
April-29-2019 Nate Johnston (njohnston)
May-6-2019 Lajos Katona (lajoskatona)
May-13-2019 Ryan Tidwell (tidwellr)
May-20-2019 Swaminathan Vasudevan (Swami)
May-27-2019 Akihiro Motoki (amotoki)
June-3-2019 Brian Haley (haleyb)
June-10-2019 Manjeet Bhatia (manjeets)
June-17-2019 YAMAMOTO Takashi (yamamoto)
June-24-2019 Miguel Lavalle (mlavalle)
July-1-2019 Bence Romsics (rubasov)
July-8-2019 Vikram Choudhary (vikram)
July-15-2019 Gabriele Cerami (panda) (tentative)

In preparation for their duty week, deputies are encouraged to review the Neutron bugs policy: https://docs.openstack.org/neutron/latest/contributor/policies/bugs.html

os-ken

Docs

CLI/SDK

SDK migration of neutronclient python bindings https://etherpad.openstack.org/p/neutron-openstacksdk-migration

Status of changes to deliver OSC (this needs to be revisit)

Neutron-lib, planned refactoring and other impacts

HOUSE KEEPING

PATCHES THAT NEED REVIEWS

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):
    • (njohnston): Cleaning old OVO compatibility code.
      • In change 658155, ralonsoh proposed removing old OVO compatibility code for QOS objects. The OVO compatibility code is meant to facilitate rolling upgrades so that a server can communicate with an agent when the version difference is 1-off. Therefore there should not be any need to keep code beyond 2 cycles after the object version change; all of the changes ralonsoh proposed changing were >1 year old. I think this is useful housecleaning and I wanted to suggest to the community that we undertake such cleaning more broadly. See the discussion here.
      • (ralonsoh): what I propose (considering njohnston's recommendations) is (1) document in devref how to implement OVO compatibility methods with examples, (2) document how to test them with examples too, (3) submit per object (or related group, as in QoS) a patch describing the OVOs cleaned, documenting in the commit message when was the last time this object was modified (recommendation: only >1-1,5 year old OVOs).
    • (your nickname): brief description.
      • More details

Previous meeting logs