Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Bugs and Gate issues)
(Bug deputy)
(47 intermediate revisions by 5 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Next milestone is T-3, week of September 9
+
* Shanghai PTG
 +
** 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
 +
** Who is interested to go for team dinner in shanghai? Please put info in etherpad https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
 +
* Train release
 
** https://releases.openstack.org/train/schedule.html
 
** https://releases.openstack.org/train/schedule.html
* PTL self nominations are in week of August 26th - if someone considers nominating him self, please be aware of this
+
** next week is Train release,
** https://releases.openstack.org/train/schedule.html#u-ptl-nominations
 
* Shanghai PTG planning etherpad
 
** https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
 
** Please also feel free to propose topics. We don't have deadline for this other than the PTG itself
 
 
* Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html
 
* Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html
  
 
=== Blueprints ===
 
=== Blueprints ===
  
Train-3 blueprints: https://launchpad.net/neutron/+milestone/train-3
 
  
Patches up for review:
+
Blueprints which we should include in Ussuri milestones:
 
* 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/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/
* https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - spec is here: https://review.opendev.org/#/c/657170 - please review it,
+
* https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes
* https://blueprints.launchpad.net/neutron/+spec/subnets-different-pools-same-net - patch https://review.opendev.org/#/c/667511/ - looks that is in good shape now, please review,
+
* 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)
+
* 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/
* https://blueprints.launchpad.net/neutron/+spec/improve-extraroute-api - patches https://review.opendev.org/#/q/topic:extraroute+(status:open+OR+status:merged) - there is good progress on that one IMO, many patches are waiting for review now
 
  
 
=== Community Goals ===
 
=== Community Goals ===
Line 31: Line 30:
 
* Run under Python 3 by default (njohnston)
 
* Run under Python 3 by default (njohnston)
 
** https://governance.openstack.org/tc/goals/stein/python3-first.html
 
** https://governance.openstack.org/tc/goals/stein/python3-first.html
 +
** https://storyboard.openstack.org/#!/story/2003242
 
** Etherpad https://etherpad.openstack.org/p/neutron_stadium_python3_status
 
** Etherpad https://etherpad.openstack.org/p/neutron_stadium_python3_status
 +
*** According to etherpad only networking-midonet is not transitioned still,
  
 
* Support IPv6-Only Deployments (slaweq)
 
* Support IPv6-Only Deployments (slaweq)
 
** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
 
** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
** gmann started pushing some patches to various projects.
+
** https://storyboard.openstack.org/#!/story/2005477 (This seems to be used to track gmann's job changes)
** gmann's patch for neutron is merged - we are good with it for now - https://review.opendev.org/#/c/671899/ - IIUC goal completion criteria, we are good on Neutron's side. Still some patches for stadium projects are needed:
+
** Patches for stadium projects are needed:
*** https://review.opendev.org/#/c/673488/ - networking-ovn
+
*** https://review.opendev.org/#/q/topic:ipv6-only-deployment-and-testing+(status:open+OR+status:merged)+(project:%255Eopenstack/neutron.*+OR+project:%255Eopenstack/networking-.*)
*** https://review.opendev.org/#/c/673501/ - networking-odl
+
*** 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,
According to my email http://lists.openstack.org/pipermail/openstack-discuss/2019-July/008084.html we should also have similar jobs proposed for:
 
*** neutron-dynamic-routing - to confirm with tidwelr
 
*** networking-bagpipe - someone who knows bagpipe better should take a look, I will try to ask tmorin about that,
 
*** networking-midonet
 
 
 
* Enabling PDF generation support for project documentation (amotoki)
 
** https://governance.openstack.org/tc/goals/train/pdf-doc-generation.html
 
  
 
=== Bugs and Gate issues ===
 
=== Bugs and Gate issues ===
  
Bugs report for week of August 12th: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008589.html
+
Bugs report for week of October 14th: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010249.html
  
 
More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI
 
More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI
Line 69: Line 63:
 
! Date !! who !! note
 
! Date !! who !! note
 
|-
 
|-
| July-1-2019 || Bernard Cafarelli (bcafarel) ||
+
| September-30-2019 || Bernard Cafarelli (bcafarel) ||
|-
 
| July-8-2019 || Slawek Kaplonski (slaweq) ||
 
 
|-
 
|-
| July-15-2019 || Hongbin Lu (hongbin) ||
+
| October-7-2019 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| July-22-2019 || Boden Russel (boden) ||
+
| October-14-2019 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| July-29-2019 || Brian Haley (haleyb)  ||
+
| October-21-2019 || Brian Haley (haleyb)  ||
 
|-
 
|-
| August-5-2019 || Lajos Katona (lajoskatona) || replaced by amotoki for Aug 5
+
| October-28-2019 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| August-12-2019 || Ryan Tidwell (tidwellr)  ||
+
| November-4-2019 || Ryan Tidwell (tidwellr)  ||
 
|-
 
|-
| August-19-2019 || Swaminathan Vasudevan (Swami) ||
+
| November-11-2019 || Swaminathan Vasudevan (Swami) ||
 
|-
 
|-
| August-26-2019 || Akihiro Motoki (amotoki)  || replaced by lajoskatona for Aug 26
+
| November-18-2019 || Akihiro Motoki (amotoki)  ||
 
|-
 
|-
| September-2-2019 || Nate Johnston (njohnston) ||
+
| November-25-2019 || Nate Johnston (njohnston) ||
 
|-
 
|-
| September-9-2019 || Miguel Lavalle (mlavalle) ||
+
| December-2-2019 || Miguel Lavalle (mlavalle) ||
 
|-
 
|-
| September-16-2019 || YAMAMOTO Takashi (yamamoto) ||
+
| December-9-2019 || YAMAMOTO Takashi (yamamoto) ||
 
|-
 
|-
| September-23-2019 || Bence Romsics (rubasov) ||
+
| December-16-2019 || Bence Romsics (rubasov) ||
 
|}
 
|}
  
Line 113: Line 105:
  
 
=== Neutron-lib, planned refactoring and other impacts ===
 
=== Neutron-lib, planned refactoring and other impacts ===
 
* proposed release of 1.28: https://review.opendev.org/#/c/666870/
 
  
 
HOUSE KEEPING
 
HOUSE KEEPING
Line 133: Line 123:
 
** (your nickname): brief description.
 
** (your nickname): brief description.
 
*** More details
 
*** More details
 
+
** (slaweq) My availability next week
  
 
== Previous meeting logs ==
 
== Previous meeting logs ==

Revision as of 15:08, 22 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 14th: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010249.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)
November-25-2019 Nate Johnston (njohnston)
December-2-2019 Miguel Lavalle (mlavalle)
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