Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Community Goals)
(Bugs and Gate issues)
 
(164 intermediate revisions by 7 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Shanghai PTG
+
* We released Ussuri version! Congrats everyone!
** planning etherpad https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
+
** https://releases.openstack.org/ussuri/
** schedule: https://usercontent.irccloud-cdn.com/file/z9iLyv8e/pvg-ptg-sched-2
+
* we are now in the Victoria cycle already https://releases.openstack.org/victoria/schedule.html
** forum session: https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24412/neutron-stadium-projects-the-path-forward
+
** Victoria-1 milestone is in the week of Jun 15th - in 4 weeks
* Train release
+
* Victoria PTG
** https://releases.openstack.org/train/schedule.html
+
** In 2 weeks
** this week is time for final RC if we will need it,
+
** planning etherpad: https://etherpad.openstack.org/p/neutron-victoria-ptg - next week I will start planning sessions so would be good to have list of topics more or less finalized,
** next week is Train release,
+
** Registration is live: http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014649.html
* Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html
+
** we will have nova-neutron session on Friday 13:00 UTC, we will also discuss some Cyborg related topics on this session,
 +
** More info http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014126.html
 +
* Virtual OpenDev http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014297.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 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 Victoria milestones:
* https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/
+
* Blueprints for Victoria-1: https://launchpad.net/neutron/+milestone/victoria-1
* 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/dns-records-in-neutron - mlavalle, can You be approver of this one?
* 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,
+
*** spec is now proposed https://review.opendev.org/#/c/726904/ - we need to review it
* 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/sg-sharing-as-readonly - amotoki, can You be approver of this one?
 +
*** rm_work - can You be assigned to this one?
  
 
=== Community Goals ===
 
=== Community Goals ===
Line 30: Line 32:
 
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)
+
* Migrate to zuulv3
** https://governance.openstack.org/tc/goals/stein/python3-first.html
+
** Etherpad: https://etherpad.openstack.org/p/neutron-train-zuulv3-py27drop
** 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 40:
 
** 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,  
+
*** there are some patches for networking-bagpipe/bgpvpn and networking-odl there - maintainers of those projects, please take a look at them :)
 
+
*** I just rebased neutron-tempest-plugin patch https://review.opendev.org/686043 and will try to continue work on it,
* Enabling PDF generation support for project documentation (amotoki)
 
** https://governance.openstack.org/tc/goals/train/pdf-doc-generation.html
 
** https://storyboard.openstack.org/#!/story/2006099
 
** 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?
 
  
 
=== Bugs and Gate issues ===
 
=== Bugs and Gate issues ===
  
Bugs report for week of September 23th: http://lists.openstack.org/pipermail/openstack-discuss/2019-September/009803.html
+
rubasov was bug deputy; Report http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014913.html
 
 
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:
+
Some bugs needs volunteers:
* https://bugs.launchpad.net/neutron/+bug/1845176
+
* https://bugs.launchpad.net/neutron/+bug/1877977 - do we really need veth interconnection still?
 +
* https://bugs.launchpad.net/neutron/+bug/1878299 - needs L3 subteam attention probably,
  
 
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 73: Line 63:
 
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 79: Line 69:
 
! Date !! who !! note
 
! Date !! who !! note
 
|-
 
|-
| September-30-2019 || Bernard Cafarelli (bcafarel) ||
+
| March-9-2020 || Bernard Cafarelli (bcafarel) ||
 +
|-
 +
| March-16-2020 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| October-7-2019 || Slawek Kaplonski (slaweq) ||
+
| March-23-2020 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| October-14-2019 || Hongbin Lu (hongbin) ||
+
| March-30-2020 || Brian Haley (haleyb) ||
 
|-
 
|-
| October-21-2019 || Boden Russel (boden) ||
+
| April-6-2020 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| October-28-2019 || Brian Haley (haleyb)  ||
+
| April-13-2020 || Ryan Tidwell (tidwellr)  ||
 
|-
 
|-
| November-4-2019 || Lajos Katona (lajoskatona) ||
+
| April-20-2020 || Nate Johnston (njohnston) ||
 
|-
 
|-
| November-11-2019 || Ryan Tidwell (tidwellr)  ||
+
| April-27-2020 || Akihiro Motoki (amotoki)  ||
 
|-
 
|-
| November-19-2019 || Swaminathan Vasudevan (Swami) ||
+
| May-4-2020 || Miguel Lavalle (mlavalle) ||
 
|-
 
|-
| November-25-2019 || Akihiro Motoki (amotoki) ||
+
| May-11-2020 || Bence Romsics (rubasov) ||
 
|-
 
|-
| December-2-2019 || Nate Johnston (njohnston) ||
+
| May-18-2020 || Maciej Jozefczyk (maciejjozefczyk) ||
 
|-
 
|-
| December-9-2019 || Miguel Lavalle (mlavalle) ||
+
| May-25-2020 || Rodolfo Alonso Hernandez (ralonsoh) ||
 
|-
 
|-
| December-16-2019 || YAMAMOTO Takashi (yamamoto) ||
+
| June-1-2020 || Lucas Alvares Gomes (lucasgomes) ||
 
|-
 
|-
| December-23-2019 || Bence Romsics (rubasov) ||
+
| June-8-2020 || Jakub Libosvar (jlibosva) ||
 
|}
 
|}
  
 
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) ===
  
 
=== 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 124: Line 117:
  
 
=== 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/
 
  
 
HOUSE KEEPING
 
HOUSE KEEPING
Line 135: Line 126:
 
* Decouple DB workstream/blueprint: https://review.openstack.org/#/q/status:open+topic:bp/neutronlib-decouple-db+label:Workflow%253D0
 
* Decouple DB workstream/blueprint: https://review.openstack.org/#/q/status:open+topic:bp/neutronlib-decouple-db+label:Workflow%253D0
 
* Callback payload workstream: https://review.openstack.org/#/q/status:open+topic:use-callback-payloads+label:Workflow%253D0
 
* Callback payload workstream: https://review.openstack.org/#/q/status:open+topic:use-callback-payloads+label:Workflow%253D0
* Updating projects for Zuul v3: https://review.openstack.org/#/q/status:open+topic:neutronlib-zuulv3
 
  
 
=== On Demand Agenda ===
 
=== On Demand Agenda ===
Line 142: Line 132:
  
 
* Topic for the meeting (keep this template, please):
 
* Topic for the meeting (keep this template, please):
** (your nickname): brief description.
+
** (nick): Topic
 
*** More details
 
*** More details
 +
** Review https://review.opendev.org/#/c/665467
 +
*** please review this and provide feedback so it can be merged.
  
 
== 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 11:35, 19 May 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 Victoria 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

rubasov was bug deputy; Report http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014913.html

Some bugs needs volunteers:

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
March-9-2020 Bernard Cafarelli (bcafarel)
March-16-2020 Slawek Kaplonski (slaweq)
March-23-2020 Hongbin Lu (hongbin)
March-30-2020 Brian Haley (haleyb)
April-6-2020 Lajos Katona (lajoskatona)
April-13-2020 Ryan Tidwell (tidwellr)
April-20-2020 Nate Johnston (njohnston)
April-27-2020 Akihiro Motoki (amotoki)
May-4-2020 Miguel Lavalle (mlavalle)
May-11-2020 Bence Romsics (rubasov)
May-18-2020 Maciej Jozefczyk (maciejjozefczyk)
May-25-2020 Rodolfo Alonso Hernandez (ralonsoh)
June-1-2020 Lucas Alvares Gomes (lucasgomes)
June-8-2020 Jakub Libosvar (jlibosva)

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)

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):

Previous meeting logs