Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Bugs and Gate issues)
(Bugs and Gate issues)
 
(325 intermediate revisions by 8 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Next milestone is T-3, week of September 9
+
* Wallaby cycle calendar https://releases.openstack.org/wallaby/schedule.html
** https://releases.openstack.org/train/schedule.html
+
** First milestone is next week,
* PTL self nominations are in week of August 26th - if someone considers nominating him self, please be aware of this
+
** Please focus on reviewing opened specs - https://review.opendev.org/q/project:openstack/neutron-specs+status:open
** https://releases.openstack.org/train/schedule.html#u-ptl-nominations
+
* Gerrit migration done - http://lists.opendev.org/pipermail/service-announce/2020-November/000014.html
* Shanghai PTG planning etherpad
+
* Virtual PTG summary http://kaplonski.pl/blog/virtual_ptg_october_2020_summary/
** https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
 
* Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html
 
  
 
=== Blueprints ===
 
=== Blueprints ===
  
Train-3 blueprints: https://launchpad.net/neutron/+milestone/train-3
+
Blueprints which we should include in Wallaby milestones:
  
Patches up for review:
+
* Wallaby-1 https://bugs.launchpad.net/neutron/+milestone/wallaby-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
* https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - spec is here: https://review.opendev.org/#/c/657170 - please review it,
+
*** Patches: https://review.opendev.org/#/q/status:open+topic:bp/enginefacade-switch
* 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/address-groups-in-sg-rules
* 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)
+
*** Patches https://review.opendev.org/#/q/topic:bp/address-groups-in-sg-rules
* 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/default-dns-zone-per-tenant
 +
*** Neutron patch https://review.opendev.org/#/c/686343/
 +
*** neutron-tempest-plugin test https://review.opendev.org/#/c/733994/
 +
** https://blueprints.launchpad.net/neutron/+spec/nftables-migration
 +
** https://bugs.launchpad.net/neutron/+bug/1863113
 +
** https://bugs.launchpad.net/neutron/+bug/1882804
 +
*** Patch: https://review.opendev.org/#/c/756892/
 +
*** Tempest test https://review.opendev.org/#/c/743695/
 +
** https://bugs.launchpad.net/neutron/+bug/1863113 - George framework
 +
*** patches https://review.opendev.org/#/q/topic:george+(status:open+OR+status:merged) - all ready for review now
 +
** https://bugs.launchpad.net/neutron/+bug/1882804 - allow replacing the QoS policy of bound port
 +
*** Patches: https://review.opendev.org/#/q/topic:bug/1882804+(status:open+OR+status:merged)
 +
 
 +
* Additional question
 +
** Please review https://review.opendev.org/#/c/742785/
 +
 
 +
* Moved to neutron-next:
 +
** https://blueprints.launchpad.net/neutron/+spec/evacuate-agent-resources
 +
** https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes
 +
** https://blueprints.launchpad.net/neutron/+spec/sg-sharing-as-readonly
  
 
=== Community Goals ===
 
=== Community Goals ===
Line 28: Line 45:
 
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 from oslo.rootwrap to oslo.privsep (ralonsoh)
** https://governance.openstack.org/tc/goals/stein/python3-first.html
+
** https://governance.openstack.org/tc/goals/selected/wallaby/migrate-to-privsep.html
** Etherpad https://etherpad.openstack.org/p/neutron_stadium_python3_status
+
** tracking progress: https://etherpad.opendev.org/p/neutron-migration-to-privsep
 +
 
 +
* Migrate RBAC Policy Format from JSON to YAML (amotoki)
  
 
* 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.
+
** https://storyboard.openstack.org/#!/story/2005477 (This seems to be used to track gmann's job changes)
** gmann's patch for neutron is merged - we are good with it for now - https://review.opendev.org/#/c/671899/ - IIUC goal completion criteria, we are good on Neutron's side. Still some patches for stadium projects are needed:
+
** Patches for stadium projects are needed:
*** https://review.opendev.org/#/c/673488/ - networking-ovn
+
*** 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/#/c/673501/ - networking-odl
+
*** there are some patches for networking-bagpipe/bgpvpn and networking-odl there - maintainers of those projects, please take a look at them :)
** According to my email http://lists.openstack.org/pipermail/openstack-discuss/2019-July/008084.html we should also have similar jobs proposed for:
+
*** I just rebased neutron-tempest-plugin patch https://review.opendev.org/686043 and will try to continue work on it,
*** neutron-dynamic-routing - to confirm with tidwelr
 
*** networking-bagpipe - someone who knows bagpipe better should take a look, I will try to ask tmorin about that,
 
*** networking-midonet
 
  
* Enabling PDF generation support for project documentation (amotoki)
+
=== Bugs and Gate issues ===
** https://governance.openstack.org/tc/goals/train/pdf-doc-generation.html
 
  
=== Bugs and Gate issues ===
+
jlibosva was on bug deputy.
 +
 
 +
Bugs which needs attention:
  
Bugs report for week of August 26th:
 
  
 
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 62: Line 78:
 
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 68: Line 84:
 
! Date !! who !! note
 
! Date !! who !! note
 
|-
 
|-
| July-1-2019 || Bernard Cafarelli (bcafarel) ||
+
| Aug-31-2020 || Bernard Cafarelli (bcafarel) ||
 
|-
 
|-
| July-8-2019 || Slawek Kaplonski (slaweq) ||
+
| Sep-7-2020 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| July-15-2019 || Hongbin Lu (hongbin) ||
+
| Sep-14-2020 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| July-22-2019 || Boden Russel (boden) ||
+
| Sep-21-2020 || Brian Haley (haleyb) ||
 
|-
 
|-
| July-29-2019 || Brian Haley (haleyb) ||
+
| Sep-28-2020 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| August-5-2019 || Lajos Katona (lajoskatona) || replaced by amotoki for Aug 5
+
| Oct-5-2020 || Nate Johnston (njohnston) ||
 
|-
 
|-
| August-12-2019 || Ryan Tidwell (tidwellr) ||
+
| Oct-12-2020 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| August-19-2019 || Swaminathan Vasudevan (Swami) ||
+
| Oct-19-2020 || Miguel Lavalle (mlavalle) ||
 
|-
 
|-
| August-26-2019 || Akihiro Motoki (amotoki) || replaced by lajoskatona for Aug 26
+
| Oct-26-2020 || Bence Romsics (rubasov) ||
 
|-
 
|-
| September-2-2019 || Nate Johnston (njohnston) ||
+
| Nov-2-2020 || Rodolfo Alonso Hernandez (ralonsoh) ||
 
|-
 
|-
| September-9-2019 || Miguel Lavalle (mlavalle) ||
+
| Nov-9-2020 || Lucas Alvares Gomes (lucasgomes) ||
 
|-
 
|-
| September-16-2019 || YAMAMOTO Takashi (yamamoto) ||
+
| Nov-16-2020 || Jakub Libosvar (jlibosva) ||
 
|-
 
|-
| September-23-2019 || Bence Romsics (rubasov) ||
+
| Nov-23-2020 || Oleg Bondarev (obondarev) ||
 
|}
 
|}
  
 +
Next round
 +
{| class="wikitable" style="text-align: center;"
 +
|-
 +
! Date !! who !! note
 +
|-
 +
| Nov-30-2020 || Bernard Cafarelli (bcafarel) ||
 +
|-
 +
| Dec-7-2020 || Slawek Kaplonski (slaweq) ||
 +
|-
 +
| Dec-14-2020 || Hongbin Lu (hongbin) ||
 +
|-
 +
| Dec-21-2020 || Brian Haley (haleyb)  ||
 +
|-
 +
| Dec-28-2020 || Lajos Katona (lajoskatona) ||
 +
|-
 +
| Jan-4-2021 || Akihiro Motoki (amotoki) ||
 +
|-
 +
| Jan-11-2021 || Miguel Lavalle (mlavalle)  ||
 +
|-
 +
| Jan-18-2021 || Bence Romsics (rubasov) ||
 +
|-
 +
| Jan-25-2021 || Rodolfo Alonso Hernandez (ralonsoh) ||
 +
|-
 +
| Feb-1-2021 || Lucas Alvares Gomes (lucasgomes) ||
 +
|-
 +
| Feb-8-2021 || Jakub Libosvar (jlibosva) ||
 +
|-
 +
| Feb-15-2021 || Oleg Bondarev (obondarev) ||
 +
|}
 
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 ===
 +
Next week I plan to profile neutron dhcp/l3 agents with Miguel. We will keep You updated in this section about our progress
 +
 +
=== New engine facade ===
 +
* BP: https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch
 +
* Neutron "progress" patch: https://review.opendev.org/#/c/545501/
 +
* Patch https://review.opendev.org/#/c/715315/ should finish it in Neutron
 +
* Stadium projects' required changes: TBD
  
 
=== Docs ===
 
=== Docs ===
Line 103: Line 157:
  
 
=== CLI/SDK ===
 
=== CLI/SDK ===
 +
 +
Allow not defined arguments to be passed in OSC,
 +
Documentation of neutronclient https://docs.openstack.org/python-neutronclient/latest/cli/neutron.html#extra-arguments-for-create-update-operation
 +
OSC work: TBD
  
 
SDK migration of neutronclient python bindings
 
SDK migration of neutronclient python bindings
Line 112: Line 170:
  
 
=== 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/
 
  
 
HOUSE KEEPING
 
HOUSE KEEPING
Line 123: Line 179:
 
* 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 ===
  
 
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:
 
* From the Oslo team: SIGHUP causing process restart when mutating config
 
** (njohnston) This is an FYI that there is an issue with using SIGHUP signals to reload mutable configs
 
** Fix is in process: https://review.opendev.org/#/c/641907/
 
 
* (rubasov): Adding member actions to a resource that already had member actions, how to?
 
I have a weird functional test failure in the extraroute-atomic implementation change:
 
https://zuul.opendev.org/t/openstack/build/8292a52f4ee747b3b754da6da000279b
 
The router resource had member actions for a long time:
 
PUT /v2.0/routers/router-id/add_router_interface
 
PUT /v2.0/routers/router-id/remove_router_interface
 
The extraroute api-def added two more: https://review.opendev.org/670849
 
PUT /v2.0/routers/router-id/add_extraroutes
 
PUT /v2.0/routers/router-id/remove_extraroutes
 
To my best understanding api-defs of dependent extensions should not be repeated in new api-defs, instead they should be automerged.
 
All 4 PUT methods above work.
 
But there's a test neutron.tests.functional.pecan_wsgi.test_controllers.TestRouterController.test_unsupported_method_member_action,
 
that tries to POST/GET /v2.0/routers/router-id/add_router_interface,
 
and expects 405 "method not allowed". It did get that before.
 
But now with the extraroute-atomic api-def the error code changed to 404.
 
But it again gives 405 if I repeat the PUT add/remove_router_interfaces member actions in the extraroute-atomic api-def.
 
It's unclear to me what is the expectation on not repeating stuff in api-defs and what's at fault.
 
Should I just change the test to expect 404 (this is simple but it kind of smells)?
 
Or should I repeat the PUT add/remove_router_interface member actions in the extraroute-atomic api-def (this is also simple but it's repetitive and I think it is not supposed to be needed)?
 
Or is this a bug in pecan or in how neutron uses pecan (if this is the agreement I shall sit down and locate the bug)?
 
  
 
* 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
  
 
== 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:36, 24 November 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 Wallaby 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

  • Migrate RBAC Policy Format from JSON to YAML (amotoki)

Bugs and Gate issues

jlibosva was on bug deputy.

Bugs which needs attention:


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
Aug-31-2020 Bernard Cafarelli (bcafarel)
Sep-7-2020 Slawek Kaplonski (slaweq)
Sep-14-2020 Hongbin Lu (hongbin)
Sep-21-2020 Brian Haley (haleyb)
Sep-28-2020 Lajos Katona (lajoskatona)
Oct-5-2020 Nate Johnston (njohnston)
Oct-12-2020 Akihiro Motoki (amotoki)
Oct-19-2020 Miguel Lavalle (mlavalle)
Oct-26-2020 Bence Romsics (rubasov)
Nov-2-2020 Rodolfo Alonso Hernandez (ralonsoh)
Nov-9-2020 Lucas Alvares Gomes (lucasgomes)
Nov-16-2020 Jakub Libosvar (jlibosva)
Nov-23-2020 Oleg Bondarev (obondarev)

Next round

Date who note
Nov-30-2020 Bernard Cafarelli (bcafarel)
Dec-7-2020 Slawek Kaplonski (slaweq)
Dec-14-2020 Hongbin Lu (hongbin)
Dec-21-2020 Brian Haley (haleyb)
Dec-28-2020 Lajos Katona (lajoskatona)
Jan-4-2021 Akihiro Motoki (amotoki)
Jan-11-2021 Miguel Lavalle (mlavalle)
Jan-18-2021 Bence Romsics (rubasov)
Jan-25-2021 Rodolfo Alonso Hernandez (ralonsoh)
Feb-1-2021 Lucas Alvares Gomes (lucasgomes)
Feb-8-2021 Jakub Libosvar (jlibosva)
Feb-15-2021 Oleg Bondarev (obondarev)

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

Next week I plan to profile neutron dhcp/l3 agents with Miguel. We will keep You updated in this section about our progress

New engine facade

Docs

CLI/SDK

Allow not defined arguments to be passed in OSC, Documentation of neutronclient https://docs.openstack.org/python-neutronclient/latest/cli/neutron.html#extra-arguments-for-create-update-operation OSC work: TBD

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):
    • (nick): Topic
      • More details

Previous meeting logs