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

 * Next milestone is Rocky-2, June 4 - 8
 * Rocky release schedule: https://releases.openstack.org/rocky/schedule.html
 * Last week we released neutron-lib 1.14.0: https://review.openstack.org/#/c/564571/
 * Looking for a volunteer to be Neutron liaison with the QA team: https://wiki.openstack.org/wiki/CrossProjectLiaisons#QA
 * These are the Neutron related sessions proposed for the Vancouver Forum:
 * Neutron project handling of its RYU dependency: http://forumtopics.openstack.org/cfp/details/136
 * nova/neutron + ops cross-project session: http://forumtopics.openstack.org/cfp/details/124
 * [neutron] extend-logging-api: http://forumtopics.openstack.org/cfp/details/143
 * [neutron-fwaas] firewall l7 fitlering: http://forumtopics.openstack.org/cfp/details/144
 * Etherpad to track Neutron team members attending Vancouver Summit / Forum: https://etherpad.openstack.org/p/YVR-neutron-atendees
 * Social event Tuesday 22nd evening
 * Rocky PTG summary: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128183.html

Blueprints
Rocky-2 blueprints: https://launchpad.net/neutron/+milestone/rocky-2

OVO/no downtime API

 * OVO backlog control spreadsheet: https://docs.google.com/spreadsheets/d/1Mz7V40GSdcUH_aBoNWjsFaNRp4wf-duz1GFWligiNXc/edit#gid=1051788848
 * Weekly meeting on Thursday at 1400UTC: http://eavesdrop.openstack.org/#Neutron_Upgrades_Meeting

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


 * policy-in-code (Queens) -- amotoki
 * wsgi support (Pike) -- annp
 * Enable mutable configuration (Rocky) https://governance.openstack.org/tc/goals/rocky/enable-mutable-configuration.html -- slaweq
 * mox3 removal (Rocky) https://bugs.launchpad.net/python-neutronclient/+bug/1753504 -- hongbin (neutronclient), amotoki (fwaas/vpnaas-dashboard), (perhaps) yamamoto (networking-midonet)
 * python3.5 fully support https://etherpad.openstack.org/p/py3-neutron-pike
 * Thread on overall community plan to move to a Python 3 only world: http://lists.openstack.org/pipermail/openstack-dev/2018-April/129866.html

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


 * Create a vlan transparent network in mixed driver environment: https://bugs.launchpad.net/neutron/+bug/1745192

Bugs and Gate issues
Bug deputy report for week of April 23rd: http://lists.openstack.org/pipermail/openstack-dev/2018-April/129988.html

A full hour is dedicated to this topic, and more during the following meeting:


 * https://wiki.openstack.org/wiki/Meetings/NeutronCI
 * Confirmed gate failures
 * Bugs that need attention
 * All bug reports associated to deprecation issues
 * Bugs Sheet
 * Grafana dashboards

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:

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

Docs

 * The future of OpenStack documentation - http://lists.openstack.org/pipermail/openstack-dev/2016-July/099012.html
 * Documentation bugs - https://bugs.launchpad.net/neutron/+bugs?field.tag=doc

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)
 * https://etherpad.openstack.org/p/osc-transition-priorities
 * http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html

Neutron-lib, planned refactoring and other impacts
List here any planned potential disruption that may be caused by a new neutron-lib release and adoption of its latest features.

DO NOT TOP POST - ADD PATCHES TO THE BOTTOM OF THE LIST


 * Open issues: https://review.openstack.org/#/q/status:open+message:%22NeutronLibImpact%22
 * In most cases all consumers using neutron/neutron-lib stable branches are updated as part of consumption. For those who "pin" neutron/neutron-lib, they will have to address the consumption as they move their "pin" up.
 * To see all consumption patches for a lib impact change, view the topic branch of the corresponding lib impact change (or search using the same subject).
 * Patches that need high-level input from neutron cores: https://review.openstack.org/#/q/message:%22NeutronCoreInputNeeded%22
 * Past issues: https://review.openstack.org/#/q/status:merged+message:%22NeutronLibImpact%22
 * UpgradeImpact changes: https://review.openstack.org/#/q/status:open+message:%22UpgradeImpact%22+project:openstack/neutron
 * Periodic neutron-lib check: http://grafana.openstack.org/dashboard/db/neutron-lib-failure-rate?panelId=4&fullscreen


 * 

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
 * How often should we tag stable branches?
 * (mlavalle): one idea might be to tag stable branches once the week after every milestone, so we regularly release the fixes added to those branches

Previous meeting logs

 * Previous meetings, with their notes and logs, can be found here.
 * networking-2018
 * networking-2017
 * networking-2016
 * networking-2015
 * networking-2014
 * networking-2013
 * quantum-2013
 * quantum-2012