Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Bug deputy)
 
(155 intermediate revisions by 10 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Milestone Train-1 is this week
+
* Next week is Ussuri-2 milestone: https://releases.openstack.org/ussuri/schedule.html
** https://releases.openstack.org/train/schedule.html
+
* Still looking for "new daddies" for
* Open Infrastructure Summit CFP Open - Deadline: July 2
+
** neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html
** http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006262.html
+
*** LAST CALL reminder was sent: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012099.html
* Photos from recent Denver PTG:
+
* We are also getting close to Rocky EM. It's in 3 weeks from now: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012207.html
** https://www.dropbox.com/sh/fydqjehy9h5y728/AAC1gIc5bJwwNd5JkcQ6Pqtra/Neutron?dl=0&subfolder_nav_tracking=1
+
** Open neutron reviews for Rocky: https://review.opendev.org/#/q/branch:%255Estable/rocky+status:open+(project:%255Eopenstack/neutron)
* Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html
+
** Open stadium projects reviews for Rocky: https://review.opendev.org/#/q/branch:^stable/rocky+status:open+(project:^openstack/neutron)
 +
* We now have new member of our drivers team - Nate Johnston welcome :)
 +
* Victoria PTG planning etherpad: https://etherpad.openstack.org/p/neutron-victoria-ptg
 +
* 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-1 blueprints: https://launchpad.net/neutron/+milestone/train-1
 
  
Patches up for review:
+
Blueprints which we should include in Ussuri milestones:
* for https://blueprints.launchpad.net/neutron/+spec/event-notifier-ironic - is something else needed on Neutron's side? We have merged https://review.opendev.org/#/c/658787/ already
+
* Blueprints for Ussuri-2: https://launchpad.net/neutron/+milestone/ussuri-2
* for https://blueprints.launchpad.net/neutron/+spec/smart-nic-ovs - we have merged  https://review.opendev.org/#/c/586252/ - is there anything else related to this BP?
+
* https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge - Convergence of ML2+OVS+DVR and OVN
* for https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - patch https://review.opendev.org/#/c/657170 waiting for review
+
* 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/tagging-on-post - almost done, only SDK/OSC part is todo
 +
* 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 - almost done, only SDK and OSC part left todo
 +
* Moved to Ussuri-3:
 +
** https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes
 +
** 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/metadata-over-ipv6
 +
* Removed target milestone:
 +
** https://blueprints.launchpad.net/neutron/+spec/evacuate-agent-resources
 +
** 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/default-dns-zone-per-tenant
  
 
=== Community Goals ===
 
=== Community Goals ===
Line 26: Line 39:
 
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-.*)
  
* Support IPv6-Only Deployments
+
* Drop Python 2.7 Support (njohnston)
** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
+
** 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
+
* Project Specific PTL and Contributor Documentation
** https://governance.openstack.org/tc/goals/train/pdf-doc-generation.html
+
** https://governance.openstack.org/tc/goals/proposed/project-ptl-and-contrib-docs.html
  
 
=== Bugs and Gate issues ===
 
=== Bugs and Gate issues ===
  
No report yet...
+
Tidwellr was on bug deputy: http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012332.html
 +
 
 +
* Should we treat https://bugs.launchpad.net/neutron/+bug/1860338 as RFE or more like a bug?
  
 
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 51: Line 70:
 
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)
 
|-
 
| April-8-2019 || Slawek Kaplonski (slaweq)
 
|-
 
| April-15-2019 || Hongbin Lu (hongbin)
 
 
|-
 
|-
| April-22-2019 || Boden Russel (boden)
+
| December-23-2019 || Bernard Cafarelli (bcafarel) || switched with Miguel Lavalle (mlavalle)
 
|-
 
|-
| April-29-2019 || Nate Johnston (njohnston)  
+
| December-30-2019 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| May-6-2019 || Lajos Katona (lajoskatona)  
+
| January-6-2020 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| May-13-2019 || Ryan Tidwell (tidwellr)  
+
| Januaryu-13-2020 || Brian Haley (haleyb) ||
 
|-
 
|-
| May-20-2019 || Swaminathan Vasudevan (Swami)
+
| January-20-2020 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| May-27-2019 || Akihiro Motoki (amotoki)
+
| January-27-2020 || Ryan Tidwell (tidwellr) ||
 
|-
 
|-
| June-3-2019 || Brian Haley (haleyb)
+
| February-3-2020 || Nate Johnston (njohnston) ||
 
|-
 
|-
| June-10-2019 || Manjeet  Bhatia (manjeets)
+
| February-10-2020 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| June-17-2019 || YAMAMOTO Takashi (yamamoto)
+
| Fabruary-24-2020 || Miguel Lavalle (mlavalle) || switched with Bernard Cafarelli (bcafarel)
 
|-
 
|-
| June-24-2019 || Miguel Lavalle (mlavalle)
+
| March-2-2020 || YAMAMOTO Takashi (yamamoto) ||
 
|-
 
|-
| July-1-2019 || Bence Romsics (rubasov)
+
| March-9-2020 || Bence Romsics (rubasov) ||
|-
 
| July-8-2019 || Vikram Choudhary (vikram)
 
|-
 
| July-15-2019 || Gabriele Cerami (panda) (tentative)
 
 
|}
 
|}
  
 
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) ===
  
* Do we still need this section?
+
=== 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 111: Line 126:
  
 
=== 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 127: Line 144:
  
 
* Topic for the meeting (keep this template, please):
 
* Topic for the meeting (keep this template, please):
** (njohnston): Cleaning old OVO compatibility code.
+
** (ralonsoh): https://bugs.launchpad.net/neutron/+bug/1476527. Question: merge API, DB and server changes without backend ones? Or not?
*** In [https://review.opendev.org/658155 change 658155], ralonsoh proposed removing old OVO compatibility code for QOS objects.  The OVO compatibility code is meant to facilitate rolling upgrades so that a server can communicate with an agent when the version difference is 1-off.  Therefore there should not be any need to keep code beyond 2 cycles after the object version change; all of the changes ralonsoh proposed changing were >1 year old.  I think this is useful housecleaning and I wanted to suggest to the community that we undertake such cleaning more broadly.  See the discussion [https://review.opendev.org/#/c/658155/2/neutron/objects/qos/policy.py here].
 
*** (ralonsoh): what I propose (considering njohnston's recommendations) is (1) document in devref how to implement OVO compatibility methods with examples, (2) document how to test them with examples too, (3) submit per object (or related group, as in QoS) a patch describing the OVOs cleaned, documenting in the commit message when was the last time this object was modified (recommendation: only >1-1,5 year old OVOs).
 
** (boden|slaweq): More +2 power in stadium projects
 
** (your nickname): brief description.
 
 
*** More details
 
*** 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]

Latest revision as of 21:09, 15 February 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

Tidwellr was on bug deputy: http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012332.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 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 Nate Johnston (njohnston)
February-10-2020 Akihiro Motoki (amotoki)
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:

Previous meeting logs