Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Bugs and Gate issues)
(On Demand Agenda)
 
(69 intermediate revisions by 3 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Shanghai PTG
+
* Still looking for "new daddies" for
** planning etherpad https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
+
** neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html
** schedule: https://usercontent.irccloud-cdn.com/file/z9iLyv8e/pvg-ptg-sched-2
+
*** I just sent LAST CALL reminder as we talked last week: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012099.html
** forum session: https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24412/neutron-stadium-projects-the-path-forward
+
* We are getting close to Ussuri-2, it will be in the week of February 10: https://releases.openstack.org/ussuri/schedule.html
* Train release
+
* I forgot about it last week, next release will be Victoria: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011947.html :)
** https://releases.openstack.org/train/schedule.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)
** this week is time for final RC if we will need it,
 
** next week is Train release,
 
* Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html
 
  
 
=== Blueprints ===
 
=== Blueprints ===
  
Train blueprints: https://launchpad.net/neutron/+milestone/train-rc1
 
All targeted to Train RC1 is merged now
 
  
Blueprints' patches up for review:
+
Blueprints which we should include in Ussuri milestones:
 +
* Blueprints for Ussuri-2: https://launchpad.net/neutron/+milestone/ussuri-2
 
* 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/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes - should this be targeted to rc-1?
+
* 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 and still not merged, this should be probably moved to Ussuri now,
+
* 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) - spec still not done https://review.opendev.org/#/c/678865/ - should we move it to Ussuri?
+
* 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/
 +
* 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 29: Line 32:
 
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
 
** https://storyboard.openstack.org/#!/story/2003242
 
** Etherpad https://etherpad.openstack.org/p/neutron_stadium_python3_status
 
*** According to etherpad we are still missing some small bits in networking-bagpipe and networking-midonet is not transitioned,
 
  
 
* Support IPv6-Only Deployments (slaweq)
 
* Support IPv6-Only Deployments (slaweq)
Line 41: Line 38:
 
** Patches for stadium projects are needed:
 
** 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-.*)
 
*** 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,
 
  
* Enabling PDF generation support for project documentation (amotoki)
+
* Drop Python 2.7 Support (njohnston)
** https://governance.openstack.org/tc/goals/train/pdf-doc-generation.html
+
** https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
** https://storyboard.openstack.org/#!/story/2006099
+
** Etherpad: https://etherpad.openstack.org/p/neutron-train-zuulv3-py27drop
** Reviews: https://review.opendev.org/#/q/topic:build-pdf-docs+(status:open+OR+status:merged)+(project:%255Eopenstack/neutron.*+OR+project:%255Eopenstack/networking-.*) - looks that all is merged now, can we remove this from this list?
+
 
 +
* Project Specific PTL and Contributor Documentation
 +
** https://governance.openstack.org/tc/goals/proposed/project-ptl-and-contrib-docs.html
  
 
=== Bugs and Gate issues ===
 
=== Bugs and Gate issues ===
  
Bugs report for week of September 30th: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/009970.html
+
haleyb was on bug deputy: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012094.html
 
 
This one https://bugs.launchpad.net/neutron/+bug/1846494 is not assigned and for me it looks like easy bug for someone new :)
 
 
 
RFE about routed networks: https://bugs.launchpad.net/neutron/+bug/1846285
 
 
 
For L3 subteam:
 
* https://bugs.launchpad.net/neutron/+bug/1845360
 
 
 
For FWaaS/CI teams:
 
* https://bugs.launchpad.net/neutron/+bug/1845300
 
  
If someone has any cycles:
+
I propose to add new official tag "ovn" to launchpad and our docs. What do You think?
* https://bugs.launchpad.net/neutron/+bug/1845176
 
  
 
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 77: 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;"
Line 83: Line 70:
 
! Date !! who !! note
 
! Date !! who !! note
 
|-
 
|-
| September-30-2019 || Bernard Cafarelli (bcafarel) ||
+
| December-23-2019 || Bernard Cafarelli (bcafarel) || switched with Miguel Lavalle (mlavalle)
 
|-
 
|-
| October-7-2019 || Slawek Kaplonski (slaweq) ||
+
| December-30-2019 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| October-14-2019 || Hongbin Lu (hongbin) ||
+
| January-6-2020 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| October-21-2019 || Boden Russel (boden) ||
+
| Januaryu-13-2020 || Brian Haley (haleyb) ||
 
|-
 
|-
| October-28-2019 || Brian Haley (haleyb) ||
+
| January-20-2020 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| November-4-2019 || Lajos Katona (lajoskatona) ||
+
| January-27-2020 || Ryan Tidwell (tidwellr) ||
 
|-
 
|-
| November-11-2019 || Ryan Tidwell (tidwellr) ||
+
| February-3-2020 || Swaminathan Vasudevan (Swami) ||
 
|-
 
|-
| November-19-2019 || Swaminathan Vasudevan (Swami) ||
+
| February-10-2020 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| November-25-2019 || Akihiro Motoki (amotoki) ||
+
| February-17-2020 || Nate Johnston (njohnston) ||
 
|-
 
|-
| December-2-2019 || Nate Johnston (njohnston) ||
+
| Fabruary-24-2020 || Miguel Lavalle (mlavalle) || switched with Bernard Cafarelli (bcafarel)
 
|-
 
|-
| December-9-2019 || Miguel Lavalle (mlavalle) ||
+
| March-2-2020 || YAMAMOTO Takashi (yamamoto) ||
 
|-
 
|-
| December-16-2019 || YAMAMOTO Takashi (yamamoto) ||
+
| March-9-2020 || Bence Romsics (rubasov) ||
|-
 
| December-23-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
 +
 +
=== 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 ===
  
As boden is mostly stepping down now, we will need someone new as docs CrossProjectLiaison: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation - any volunteers?
 
 
* 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
 
* Documentation bugs - https://bugs.launchpad.net/neutron/+bugs?field.tag=doc
Line 129: Line 123:
 
=== Neutron-lib, planned refactoring and other impacts ===
 
=== Neutron-lib, planned refactoring and other impacts ===
  
* Released last week 1.29.1: https://review.opendev.org/#/c/679986/ - this is version for Train, and patch to use it in Neutron is https://review.opendev.org/#/c/680980/
+
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 145: 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):
 
** (your nickname): brief description.
 
** (your nickname): brief description.
Line 151: Line 149:
 
== 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 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