Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Bugs and Gate issues)
(Bug deputy)
(87 intermediate revisions by 5 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Next milestone is T-3, week of September 9
+
* Still looking for "new daddies" for
** https://releases.openstack.org/train/schedule.html
+
** neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html
* Shanghai PTG planning etherpad
+
** neutron-vpnaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010931.html
** https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
+
* Removing of neutron-interconnection from stadium project is done
** If you are planning to attend, please enter your name at the top of the pad no later than August 4th
+
* It's Ussuri-1 milestone week: https://releases.openstack.org/ussuri/schedule.html
** Please also free to propose topics. We don't have deadline for this other than the PTG itself
+
* We now have review priority also in stadium projects' patches: https://review.opendev.org/#/c/696628/
* Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html
+
* Voting for "V" release name is now open: http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011477.html
 +
* Shanghai PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010702.html and also on http://kaplonski.pl/blog/shanghai_ptg_summary/ (with photos from team dinner)
  
 
=== Blueprints ===
 
=== Blueprints ===
  
Train-3 blueprints: https://launchpad.net/neutron/+milestone/train-3
 
  
Patches up for review:
+
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/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/neutron-ovn-merge - Convergence of ML2+OVS+DVR and OVN
* 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/multiple-segment-per-network-per-host - spec is here: https://review.opendev.org/#/c/657170
* 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
+
* 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/metadata-over-ipv6
 +
* https://blueprints.launchpad.net/neutron/+spec/tagging-on-post
 +
* https://blueprints.launchpad.net/neutron/+spec/evacuate-agent-resources
 +
* https://bugs.launchpad.net/neutron/+bug/1841067 - [RFE] SR-IOV agent depends on mac addresses for getting bound ports
 +
* https://blueprints.launchpad.net/neutron/+spec/fip-pf-description
 +
* https://blueprints.launchpad.net/neutron/+spec/default-dns-zone-per-tenant
  
 
=== Community Goals ===
 
=== Community Goals ===
Line 27: Line 34:
 
This slot is to used to track the progress of the 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
 
https://governance.openstack.org/tc/goals/index.html#release-cycles
 
* Run under Python 3 by default (njohnston)
 
** https://governance.openstack.org/tc/goals/stein/python3-first.html
 
  
 
* 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. He asked for neutron stadium projects and I did some list here http://lists.openstack.org/pipermail/openstack-discuss/2019-July/008084.html - please check it
+
** https://storyboard.openstack.org/#!/story/2005477 (This seems to be used to track gmann's job changes)
 +
** Patches for stadium projects are needed:
 +
*** 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,
 +
 
 +
* Drop Python 2.7 Support (njohnston)
 +
** https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
 +
** Etherpad: https://etherpad.openstack.org/p/neutron-train-zuulv3-py27drop
  
* Enabling PDF generation support for project documentation (amotoki)
+
* Project Specific PTL and Contributor Documentation
** https://governance.openstack.org/tc/goals/train/pdf-doc-generation.html
+
** Proposal not merged yet: https://review.opendev.org/#/c/691737/
  
 
=== Bugs and Gate issues ===
 
=== Bugs and Gate issues ===
  
Bugs report for week of July 29th: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008258.html
+
amotoki was bug deputy last week. I don't see any report from him yet.
  
 
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 60: Line 71:
 
! Date !! who !! note
 
! Date !! who !! note
 
|-
 
|-
| July-1-2019 || Bernard Cafarelli (bcafarel) ||
+
| September-30-2019 || Bernard Cafarelli (bcafarel) ||
 
|-
 
|-
| July-8-2019 || Slawek Kaplonski (slaweq) ||
+
| October-7-2019 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| July-15-2019 || Hongbin Lu (hongbin) ||
+
| October-14-2019 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| July-22-2019 || Boden Russel (boden) ||
+
| October-21-2019 || Brian Haley (haleyb) ||
 
|-
 
|-
| July-29-2019 || Brian Haley (haleyb) ||
+
| October-28-2019 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| August-5-2019 || Lajos Katona (lajoskatona) || replaced by amotoki for Aug 5
+
| November-4-2019 || Ryan Tidwell (tidwellr) ||
 
|-
 
|-
| August-12-2019 || Ryan Tidwell (tidwellr) ||
+
| November-11-2019 || Swaminathan Vasudevan (Swami) ||
 
|-
 
|-
| August-19-2019 || Swaminathan Vasudevan (Swami) ||
+
| November-18-2019 || Akihiro Motoki (amotoki) || switched with Miguel Lavalle (mlavalle)
 
|-
 
|-
| August-26-2019 || Akihiro Motoki (amotoki) || replaced by lajoskatona for Aug 26
+
| November-25-2019 || Nate Johnston (njohnston) ||
 
|-
 
|-
| September-2-2019 || Nate Johnston (njohnston) ||
+
| December-2-2019 || Miguel Lavalle (mlavalle) || switched with Akihiro Motoki (amotoki)
 
|-
 
|-
| September-9-2019 || Miguel Lavalle (mlavalle) ||
+
| December-9-2019 || YAMAMOTO Takashi (yamamoto) ||
 
|-
 
|-
| September-16-2019 || YAMAMOTO Takashi (yamamoto) ||
+
| December-16-2019 || Bence Romsics (rubasov) ||
 +
|}
 +
 
 +
Next bug deputy round
 +
{| class="wikitable" style="text-align: center;"
 
|-
 
|-
| September-23-2019 || Bence Romsics (rubasov) ||
+
! Date !! who !! note
 +
|-
 +
| December-23-2019 || Bernard Cafarelli (bcafarel) || switched with Miguel Lavalle (mlavalle)
 +
|-
 +
| December-30-2019 || Slawek Kaplonski (slaweq) ||
 +
|-
 +
| January-6-2020 || Hongbin Lu (hongbin) ||
 +
|-
 +
| Januaryu-13-2020 || Brian Haley (haleyb)  ||
 +
|-
 +
| January-20-2020 || Lajos Katona (lajoskatona) ||
 +
|-
 +
| January-27-2020 || Ryan Tidwell (tidwellr)  ||
 +
|-
 +
| February-3-2020 || Swaminathan Vasudevan (Swami) ||
 +
|-
 +
| February-10-2020 || Akihiro Motoki (amotoki)  ||
 +
|-
 +
| February-17-2020 || Nate Johnston (njohnston) ||
 +
|-
 +
| Fabruary-24-2020 || Miguel Lavalle (mlavalle) || switched with Bernard Cafarelli (bcafarel)
 +
|-
 +
| March-2-2020 || YAMAMOTO Takashi (yamamoto) ||
 +
|-
 +
| March-9-2020 || 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
 
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
 +
 +
=== Neutron performance subteam (Monday meetings) ===
 +
 +
=== Networking OVN and ML2+OVS+DVR Convergence (Tuesday meetings) ===
 +
 +
Merge OVN into Neutron tree:
 +
* Blueprint: https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge
 +
* Proposed rehome plan: https://ethercalc.openstack.org/networking-ovn-migration
 +
* Planning Etherpad https://etherpad.openstack.org/p/neutron-networking-ovn-merge
 +
* Spec: https://review.opendev.org/#/c/658414/
  
 
=== Docs ===
 
=== Docs ===
Line 105: Line 154:
 
=== 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/
+
I proposed release of new neutron-lib version without:
 +
* https://review.opendev.org/#/c/695205/
 +
 
 +
Those are included:
 +
* https://review.opendev.org/#/c/692580/ - merged
 +
* https://review.opendev.org/#/c/696308/ - merged
 +
* https://review.opendev.org/#/c/696070/ - merged
 +
 
 +
Release patch https://review.opendev.org/#/c/697956/
  
 
HOUSE KEEPING
 
HOUSE KEEPING
Line 124: Line 181:
 
** (your nickname): brief description.
 
** (your nickname): brief description.
 
*** More details
 
*** More details
 
 
* neutron-lib backports/ neutron backports from neutron-lib
 
** (bcafarel): should we start doing neutron-lib backports (and point releases)? And if no, what to do with neutron backports (older branch) coming from a neutron-lib fix?
 
*** Current case: https://review.opendev.org/#/c/672166/ is a Rocky neutron backport of neutron-lib Stein https://review.opendev.org/#/c/672165/
 
*** question was asked in neutron-lib backport: should we start doing such backports and point releases?
 
*** rocky/queens backports are in neutron itself, but waiting for the newer stable version to get the fix (stein in that case for neutron-lib)
 
  
 
== Previous meeting logs ==
 
== Previous meeting logs ==

Revision as of 21:58, 9 December 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

amotoki was bug deputy last week. I don't see any report from him yet.

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)

Next bug deputy round

Date who note
December-23-2019 Bernard Cafarelli (bcafarel) switched with Miguel Lavalle (mlavalle)
December-30-2019 Slawek Kaplonski (slaweq)
January-6-2020 Hongbin Lu (hongbin)
Januaryu-13-2020 Brian Haley (haleyb)
January-20-2020 Lajos Katona (lajoskatona)
January-27-2020 Ryan Tidwell (tidwellr)
February-3-2020 Swaminathan Vasudevan (Swami)
February-10-2020 Akihiro Motoki (amotoki)
February-17-2020 Nate Johnston (njohnston)
Fabruary-24-2020 Miguel Lavalle (mlavalle) switched with Bernard Cafarelli (bcafarel)
March-2-2020 YAMAMOTO Takashi (yamamoto)
March-9-2020 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

Neutron performance subteam (Monday meetings)

Networking OVN and ML2+OVS+DVR Convergence (Tuesday meetings)

Merge OVN into Neutron tree:

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

I proposed release of new neutron-lib version without:

Those are included:

Release patch https://review.opendev.org/#/c/697956/

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

Previous meeting logs