Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Bug deputy)
(483 intermediate revisions by 34 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Release countdown for week R-0 - http://lists.openstack.org/pipermail/openstack-dev/2016-September/104809.html
+
* Shanghai PTG
 +
** Summit and PTG is next week
 +
** planning etherpad https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
 +
** schedule: https://usercontent.irccloud-cdn.com/file/z9iLyv8e/pvg-ptg-sched-2
 +
** forum session: https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24412/neutron-stadium-projects-the-path-forward
 +
* Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html
  
 
=== Blueprints ===
 
=== Blueprints ===
  
Current milestone: https://launchpad.net/neutron/+milestone/ocata-1
 
  
=== Bugs and Gate failures ===
+
Blueprints which we should include in Ussuri milestones:
 +
* Blueprints for Ussuri-1: https://launchpad.net/neutron/+milestone/ussuri-1
 +
* https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/
 +
* https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes
 +
* https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - spec is here: https://review.opendev.org/#/c/657170
 +
* https://blueprints.launchpad.net/neutron/+spec/neutron-classifier-neutron-qos - there is series of patches in https://review.opendev.org/#/q/topic:qos-classifier+(status:open+OR+status:merged) - spec still not done https://review.opendev.org/#/c/678865/
  
Approximate stats for the current cycle:
+
=== Community Goals ===
  
* From the beginning of Ocata (Sept-16-2016):
+
This slot is to used to track the progress of the community goals.
** Total reports: '''87'''
+
https://governance.openstack.org/tc/goals/index.html#release-cycles
*** Fix released: '''25'''
+
 
*** Unassigned: '''30'''
+
* Support IPv6-Only Deployments (slaweq)
**** New: '''6'''
+
** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
**** Incomplete: '''7'''
+
** https://storyboard.openstack.org/#!/story/2005477 (This seems to be used to track gmann's job changes)
**** Confirmed: '''8'''
+
** Patches for stadium projects are needed:
**** Triaged: '''0'''
+
*** https://review.opendev.org/#/q/topic:ipv6-only-deployment-and-testing+(status:open+OR+status:merged)+(project:%255Eopenstack/neutron.*+OR+project:%255Eopenstack/networking-.*)
 +
*** I need to check and update https://review.opendev.org/#/c/686043/ - as we talked with gmann to propose one neutron-tempest-plugin ipv6 job which will run all tempest plugin tests using ipv6 only,
 +
 
 +
* Community goals for Ussuri
 +
** Proposals: https://etherpad.openstack.org/p/PVG-u-series-goals
 +
 
 +
=== Bugs and Gate issues ===
 +
 
 +
Bugs report for week of October 21th: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010393.html
 +
 
 +
More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI
  
 
* [https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.tag=gate-failure Confirmed gate failures]
 
* [https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.tag=gate-failure Confirmed gate failures]
Line 31: Line 50:
 
==== Bug deputy ====  
 
==== 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.
+
You can find more information about what the role is here: https://docs.openstack.org/neutron/latest/contributor/policies/bugs.html#neutron-bug-deputy
  
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
+
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:  
 
 
Next weeks:
 
  
 
{| class="wikitable" style="text-align: center;"
 
{| class="wikitable" style="text-align: center;"
 
|-
 
|-
! Date !! who  
+
! Date !! who !! note
|-
 
| May-30-2016 || kevinbenton
 
|-
 
| Jun-6-2016 || mangelajo
 
 
|-
 
|-
| Jun-13-2016 || dasm
+
| September-30-2019 || Bernard Cafarelli (bcafarel) ||
 
|-
 
|-
| Jun-20-2016 || john-davidge
+
| October-7-2019 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| Jun-27-2016 || rossella_s
+
| October-14-2019 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| Jul-4-2016 || johndperkins
+
| October-21-2019 || Brian Haley (haleyb)  ||
 
|-
 
|-
| Jul-11-2016 || blogan
+
| October-28-2019 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| Jul-18-2016 || mlavalle
+
| November-4-2019 || Ryan Tidwell (tidwellr)  ||
 
|-
 
|-
| Jul-25-2016 || jlibosva
+
| November-11-2019 || Swaminathan Vasudevan (Swami) ||
 
|-
 
|-
| Aug-01-2016 || electrocucaracha
+
| November-18-2019 || Akihiro Motoki (amotoki)  || switched with Miguel Lavalle (mlavalle)
 
|-
 
|-
| Aug-08-2016 || njohnston
+
| November-25-2019 || Nate Johnston (njohnston) ||
 
|-
 
|-
| Aug-15-2016 || armax
+
| December-2-2019 || Miguel Lavalle (mlavalle) || switched with Akihiro Motoki (amotoki)
 
|-
 
|-
| Aug-30-2016 || haleyb
+
| December-9-2019 || YAMAMOTO Takashi (yamamoto) ||
 
|-
 
|-
| Sep-04-2016 || jschwarz
+
| December-16-2019 || Bence Romsics (rubasov) ||
|-
 
| Sep-12-2016 || hichihara
 
|-
 
| Sep-19-2016 || ihrachys
 
|-
 
| Sep-26-2016 || ihrachys
 
 
|}
 
|}
 +
 +
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 ===
 
=== Docs ===
  
 
* The future of OpenStack documentation - http://lists.openstack.org/pipermail/openstack-dev/2016-July/099012.html
 
* 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
  
=== Transition to OSC ===
+
Status of changes to deliver OSC (this needs to be revisit)
Status of changes to deliver OSC
+
* https://etherpad.openstack.org/p/osc-transition-priorities
 
* http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html
 
* http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html
  
=== Neutron-lib ===
+
=== Neutron-lib, planned refactoring and other impacts ===
* https://review.openstack.org/#/q/project:openstack/neutron-lib+status:open
+
 
 +
HOUSE KEEPING
 +
* Neutron-lib work items and volunteers are being tracked via etherpad: https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list
 +
* For a list of "current" consumers who receive neutron-lib updates and consumption patches, see: http://codesearch.openstack.org/?q=neutron-lib-current
 +
* For a complete list of neutron-lib consumption patches that may impact consumers see: https://review.openstack.org/#/q/message:%22NeutronLibImpact%22
 +
 
 +
PATCHES THAT NEED REVIEWS
 +
* Decouple DB workstream/blueprint: https://review.openstack.org/#/q/status:open+topic:bp/neutronlib-decouple-db+label:Workflow%253D0
 +
* Callback payload workstream: https://review.openstack.org/#/q/status:open+topic:use-callback-payloads+label:Workflow%253D0
 +
* Updating projects for Zuul v3: https://review.openstack.org/#/q/status:open+topic:neutronlib-zuulv3
  
 
=== On Demand Agenda ===
 
=== 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:
 
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
 
** ankur-gupta-f: The feature classification matrix will provide information about plugins and the features they support.
 
*** RFE has been approved. Need to improve Neutron documentation about various backends and the feature they support: https://review.openstack.org/#/c/318192/ https://review.openstack.org/#/c/324048/
 
** ihrachys: adding stable deputy role to arrange sustain proactive backports process:
 
*** a new process to handle stable backports proposed: http://lists.openstack.org/pipermail/openstack-dev/2016-June/098552.html
 
* Let operator update subnet.cidr:
 
** yottatsa: as an operator I want to expand or shrink Public network without re-allocating all Floating IPs.
 
*** Although I don't see any reason to abandon it, there are many roadblocks like "unexpected side effects on plugins that do not handle well the CIDR update" on the way. RFE https://bugs.launchpad.net/neutron/+bug/1605343
 
* 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
 
** ishafran: There is a blueprint describing new feature: https://blueprints.launchpad.net/neutron/+spec/neutron-local-snat
 
*** I would like to understand the reasons the blueprint marked obsolete. Is there a developed / in development patch that solves the subject ?
 
* Recompiling a Cirros fork at the gate
 
** jschwarz: Basically, getting Cirros to support stuff that we need to test is going no where, so instead we propose forking Cirros and adding support for what we need on our own.
 
*** https://etherpad.openstack.org/p/cirros-respin . This has gotten support from at least 2 cores already (ajo, kevinbenton)
 
  
 
* Topic for the meeting (keep this template, please):
 
* Topic for the meeting (keep this template, please):
 
** (your nickname): brief description.
 
** (your nickname): brief description.
 
*** More details
 
*** More details
 +
** (slaweq) My availability next week
  
 
== Previous meeting logs ==
 
== Previous meeting logs ==
 
* Previous meetings, with their notes and logs, can be found [http://eavesdrop.openstack.org/meetings/networking/ here].
 
* Previous meetings, with their notes and logs, can be found [http://eavesdrop.openstack.org/meetings/networking/ here].
 +
** [http://eavesdrop.openstack.org/meetings/networking/2019/?C=M;O=D networking-2019]
 +
** [http://eavesdrop.openstack.org/meetings/networking/2018/?C=M;O=D networking-2018]
 +
** [http://eavesdrop.openstack.org/meetings/networking/2017/?C=M;O=D networking-2017]
 
** [http://eavesdrop.openstack.org/meetings/networking/2016/?C=M;O=D networking-2016]
 
** [http://eavesdrop.openstack.org/meetings/networking/2016/?C=M;O=D networking-2016]
 
** [http://eavesdrop.openstack.org/meetings/networking/2015/?C=M;O=D networking-2015]
 
** [http://eavesdrop.openstack.org/meetings/networking/2015/?C=M;O=D networking-2015]
Line 121: Line 131:
 
** [http://eavesdrop.openstack.org/meetings/quantum/2013/?C=M;O=D quantum-2013]
 
** [http://eavesdrop.openstack.org/meetings/quantum/2013/?C=M;O=D quantum-2013]
 
** [http://eavesdrop.openstack.org/meetings/quantum/2012/?C=M;O=D quantum-2012]
 
** [http://eavesdrop.openstack.org/meetings/quantum/2012/?C=M;O=D quantum-2012]
* Older meeting notes are here:  ../MeetingLogs.
 

Revision as of 21:50, 28 October 2019

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

Blueprints which we should include in Ussuri milestones:

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

Bugs and Gate issues

Bugs report for week of October 21th: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010393.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 note
September-30-2019 Bernard Cafarelli (bcafarel)
October-7-2019 Slawek Kaplonski (slaweq)
October-14-2019 Hongbin Lu (hongbin)
October-21-2019 Brian Haley (haleyb)
October-28-2019 Lajos Katona (lajoskatona)
November-4-2019 Ryan Tidwell (tidwellr)
November-11-2019 Swaminathan Vasudevan (Swami)
November-18-2019 Akihiro Motoki (amotoki) switched with Miguel Lavalle (mlavalle)
November-25-2019 Nate Johnston (njohnston)
December-2-2019 Miguel Lavalle (mlavalle) switched with Akihiro Motoki (amotoki)
December-9-2019 YAMAMOTO Takashi (yamamoto)
December-16-2019 Bence Romsics (rubasov)

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

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):
    • (your nickname): brief description.
      • More details
    • (slaweq) My availability next week

Previous meeting logs