Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Bugs and Gate issues)
(On Demand Agenda)
(172 intermediate revisions by 10 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Cut Stein-RC1
+
* Still looking for "new daddies" for
** https://review.openstack.org/#/c/644339/
+
** neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html
* We have until April 5th if another RC is needed:
+
*** I just sent LAST CALL reminder as we talked last week: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012099.html
** https://releases.openstack.org/stein/schedule.html
+
* We are getting close to Ussuri-2, it will be in the week of February 10: https://releases.openstack.org/ussuri/schedule.html
* Message sent to ML with planning etherpad for Train PTG
+
* I forgot about it last week, next release will be Victoria: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011947.html :)
** http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003895.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)
** https://etherpad.openstack.org/p/openstack-networking-train-ptg
 
* Stein PTG summary: http://lists.openstack.org/pipermail/openstack-dev/2018-September/135032.html
 
  
 
=== Blueprints ===
 
=== Blueprints ===
  
Stein-3 blueprints: https://launchpad.net/neutron/+milestone/stein-rc1
 
  
Patches up for review:
+
Blueprints which we should include in Ussuri milestones:
 
+
* Blueprints for Ussuri-2: https://launchpad.net/neutron/+milestone/ussuri-2
* https://review.openstack.org/#/c/624708/
+
* https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/
* https://review.openstack.org/#/c/624709/
+
* https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes
 
+
* https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge - Convergence of ML2+OVS+DVR and OVN
==== OVO/no downtime API ====
+
* 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/
* OVO backlog control spreadsheet: https://docs.google.com/spreadsheets/d/1Mz7V40GSdcUH_aBoNWjsFaNRp4wf-duz1GFWligiNXc/edit#gid=1051788848
+
* https://blueprints.launchpad.net/neutron/+spec/metadata-over-ipv6
* Weekly meeting on Thursday at 1400UTC: http://eavesdrop.openstack.org/#Neutron_Upgrades_Meeting
+
* 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 32: Line 33:
 
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)
+
* Support IPv6-Only Deployments (slaweq)
** https://governance.openstack.org/tc/goals/stein/python3-first.html
+
** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
 +
** 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-.*)
  
=== Starter Approved RFEs ===
+
* 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
  
This section is for advertising approved RFEs that the Neutron Drivers team have deemed suitable for new contributors:
+
* Project Specific PTL and Contributor Documentation
 +
** https://governance.openstack.org/tc/goals/proposed/project-ptl-and-contrib-docs.html
  
* Create a vlan transparent network in mixed driver environment: https://bugs.launchpad.net/neutron/+bug/1745192
+
=== Bugs and Gate issues ===
  
* [RFE] subnet pool can not delete prefixes https://bugs.launchpad.net/neutron/+bug/1792901
+
haleyb was on bug deputy: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012094.html
  
=== Bugs and Gate issues ===
+
I propose to add new official tag "ovn" to launchpad and our docs. What do You think?
 
 
Bug deputy report for week of March 25th: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/004371.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 59: Line 64:
 
You can find more information about what the role is here: https://docs.openstack.org/neutron/latest/contributor/policies/bugs.html#neutron-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:  
+
During the Denver PTG we made the decision to institute a fixed rotation for the the bugs deputy role. The currently scheduled rotation is the following:  
  
 
{| class="wikitable" style="text-align: center;"
 
{| class="wikitable" style="text-align: center;"
 
|-
 
|-
! Date !! who  
+
! Date !! who !! note
 
|-
 
|-
| April-1-2019 || Bernard Cafarelli (bcafarel)
+
| December-23-2019 || Bernard Cafarelli (bcafarel) || switched with Miguel Lavalle (mlavalle)
 
|-
 
|-
| April-8-2019 || Pawel Suder (pasuder)
+
| December-30-2019 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| April-15-2019 || Hongbin Lu (hongbin)
+
| January-6-2020 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| April-22-2019 || Slawek Kaplonski (slaweq)
+
| Januaryu-13-2020 || Brian Haley (haleyb) ||
 
|-
 
|-
| April-29-2019 || Boden Russel (boden)
+
| January-20-2020 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| May-6-2019 || Nate Johnston (njohnston)  
+
| January-27-2020 || Ryan Tidwell (tidwellr) ||
 
|-
 
|-
| May-13-2019 || Lajos Katona (lajoskatona)  
+
| February-3-2020 || Swaminathan Vasudevan (Swami) ||
 
|-
 
|-
| May-20-2019 || Ryan Tidwell (tidwellr)  
+
| February-10-2020 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| May-27-2019 || Swaminathan Vasudevan (Swami)
+
| February-17-2020 || Nate Johnston (njohnston) ||
 
|-
 
|-
| June-3-2019 || Akihiro Motoki (amotoki)
+
| Fabruary-24-2020 || Miguel Lavalle (mlavalle) || switched with Bernard Cafarelli (bcafarel)
 
|-
 
|-
| June-10-2019 || Brian Haley (haleyb)
+
| March-2-2020 || YAMAMOTO Takashi (yamamoto) ||
 
|-
 
|-
| June-17-2019 || Manjeet  Bhatia (manjeets)
+
| March-9-2020 || Bence Romsics (rubasov) ||
|-
 
| June-24-2019 || YAMAMOTO Takashi (yamamoto)
 
|-
 
| July-1-2019 || Miguel Lavalle (mlavalle)
 
|-
 
| July-8-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
 
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 ===
+
=== Neutron performance subteam (Monday meetings) ===
  
* Progress report for week of October 29th: http://lists.openstack.org/pipermail/openstack-dev/2018-November/136329.html
+
=== 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 117: Line 122:
  
 
=== Neutron-lib, planned refactoring and other impacts ===
 
=== Neutron-lib, planned refactoring and other impacts ===
 +
 +
We just released neutron-lib 2.0.0 - with dropped support for python 2.7 and fix for bug introduced accidentally in 1.31.0
  
 
HOUSE KEEPING
 
HOUSE KEEPING
Line 132: Line 139:
 
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:
  
 +
* standardize on zuul v3 syntax:
 +
** Do we need to change job definitions on stable branches as well?
 +
*** The question come up for bagpipe job conversions. The old legacy job definitions are here: https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/zuul-legacy-jobs.yaml#L367-L377.
 +
If we do the conversion for master only, the legacy job definitions will remain in openstack-zuul-jobs repo, but if we remove them we have to backport the new job template to stable branches ase well.
 
* Topic for the meeting (keep this template, please):
 
* Topic for the meeting (keep this template, please):
** (slaweq) Review-priority flag, ML thread: http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001374.html - do we want something like that in Neutron? Example of Cinder dashboard done with it https://review.openstack.org/#/dashboard/?foreach=%28project%3Aopenstack%2Fcinder+OR%0Aproject%3Aopenstack%2Fpython-cinderclient+OR%0Aproject%3Aopenstack%2Fpython-brick-cinderclient-ext+OR%0Aproject%3Aopenstack%2Fos-brick%29+status%3Aopen&title=Cinder+Priorities+Dashboard&High+Priority+Changes=label%3AReview-Priority%3D2&Priority+Changes=label%3AReview-Priority%3D1&Blocked+Reviews=label%3AReview-Priority%3D-1
+
** (your nickname): brief description.
 +
*** More details
  
 
== 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/2020/?C=M;O=D networking-2020]
 
** [http://eavesdrop.openstack.org/meetings/networking/2019/?C=M;O=D networking-2019]
 
** [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/2018/?C=M;O=D networking-2018]

Revision as of 13:44, 24 January 2020

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

haleyb was on bug deputy: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012094.html

I propose to add new official tag "ovn" to launchpad and our docs. What do You think?

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 currently scheduled rotation is the following:

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

We just released neutron-lib 2.0.0 - with dropped support for python 2.7 and fix for bug introduced accidentally in 1.31.0

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:

If we do the conversion for master only, the legacy job definitions will remain in openstack-zuul-jobs repo, but if we remove them we have to backport the new job template to stable branches ase well.

  • Topic for the meeting (keep this template, please):
    • (your nickname): brief description.
      • More details

Previous meeting logs