Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Bugs and Gate issues)
(Announcements / Reminders)
 
(118 intermediate revisions by 7 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Next milestone is T-3, week of September 9
+
* We reached Ussuri-2 milestone: https://releases.openstack.org/ussuri/schedule.html last week,
** https://releases.openstack.org/train/schedule.html
+
** next important dates are:
* PTL self nominations are in week of August 26th - if someone considers nominating him self, please be aware of this
+
*** Final release for non-client libraries - week of March 30th,
** https://releases.openstack.org/train/schedule.html#u-ptl-nominations
+
*** Ussuri-3 (feature freeze) - week of April 6th
* Shanghai PTG planning etherpad
+
** Related to that are new releases of Stein and Train:
** https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
+
*** https://review.opendev.org/#/c/707822/
* Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html
+
*** https://review.opendev.org/#/c/707840/
 +
* neutron-fwaas deprecation started: https://review.opendev.org/#/q/topic:deprecate-fwaas+(status:open+OR+status:merged),
 +
* We are also getting close to Rocky EM. It's next week: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012207.html
 +
** Open neutron reviews for Rocky: https://review.opendev.org/#/q/branch:%255Estable/rocky+status:open+(project:%255Eopenstack/neutron)
 +
** Open stadium projects reviews for Rocky: https://review.opendev.org/#/q/branch:^stable/rocky+status:open+(project:^openstack/neutron)
 +
* 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-3 blueprints: https://launchpad.net/neutron/+milestone/train-3
 
  
Patches up for review:
+
Blueprints which we should include in Ussuri milestones:
* https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/
+
* Blueprints for Ussuri-3: https://launchpad.net/neutron/+milestone/ussuri-3
* https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - spec is here: https://review.opendev.org/#/c/657170 - please review it,
+
** https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge - Convergence of ML2+OVS+DVR and OVN
* 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/tagging-on-post - almost done, only SDK/OSC part is todo
* 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://bugs.launchpad.net/neutron/+bug/1841067 - [RFE] SR-IOV agent depends on mac addresses for getting bound ports
* 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/fip-pf-description - almost done, only SDK and OSC part left todo
 +
** 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
 +
** https://blueprints.launchpad.net/neutron/+spec/neutron-classifier-neutron-qos
  
 
=== Community Goals ===
 
=== Community Goals ===
Line 27: Line 40:
 
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
 
** Etherpad https://etherpad.openstack.org/p/neutron_stadium_python3_status
 
  
 
* 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
 
** According to my email http://lists.openstack.org/pipermail/openstack-discuss/2019-July/008084.html we should also have similar jobs proposed for:
 
*** 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)
+
* Drop Python 2.7 Support (njohnston) - DONE
** https://governance.openstack.org/tc/goals/train/pdf-doc-generation.html
+
** https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
 +
** Etherpad: https://etherpad.openstack.org/p/neutron-train-zuulv3-py27drop
 +
 
 +
* Project Specific PTL and Contributor Documentation
 +
** https://governance.openstack.org/tc/goals/proposed/project-ptl-and-contrib-docs.html
 +
** patch proposed: https://review.opendev.org/#/c/707486/
  
 
=== Bugs and Gate issues ===
 
=== Bugs and Gate issues ===
  
Bugs report for week of August 26th: https://docs.google.com/spreadsheets/d/1JjcSHL6hFYsAvlrcgK7_Eje1S4vvJdvm363_Mmy557I/edit#gid=0
+
Tidwellr was on bug deputy. I don't see summary yet.
  
 
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 71:
 
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 77:
 
! Date !! who !! note
 
! Date !! who !! note
 
|-
 
|-
| July-1-2019 || Bernard Cafarelli (bcafarel) ||
+
| December-23-2019 || Bernard Cafarelli (bcafarel) || switched with Miguel Lavalle (mlavalle)
 
|-
 
|-
| July-8-2019 || Slawek Kaplonski (slaweq) ||
+
| December-30-2019 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| July-15-2019 || Hongbin Lu (hongbin) ||
+
| January-6-2020 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| July-22-2019 || Boden Russel (boden) ||
+
| Januaryu-13-2020 || Brian Haley (haleyb) ||
 
|-
 
|-
| July-29-2019 || Brian Haley (haleyb) ||
+
| January-20-2020 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| August-5-2019 || Lajos Katona (lajoskatona) || replaced by amotoki for Aug 5
+
| January-27-2020 || Ryan Tidwell (tidwellr) ||
 
|-
 
|-
| August-12-2019 || Ryan Tidwell (tidwellr) ||
+
| February-3-2020 || Nate Johnston (njohnston) ||
 
|-
 
|-
| August-19-2019 || Swaminathan Vasudevan (Swami) ||
+
| February-10-2020 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| August-26-2019 || Akihiro Motoki (amotoki) || replaced by lajoskatona for Aug 26
+
| Fabruary-24-2020 || Miguel Lavalle (mlavalle) || switched with Bernard Cafarelli (bcafarel)
 
|-
 
|-
| September-2-2019 || Nate Johnston (njohnston) ||
+
| March-2-2020 || YAMAMOTO Takashi (yamamoto) ||
 
|-
 
|-
| September-9-2019 || Miguel Lavalle (mlavalle) ||
+
| March-9-2020 || Bence Romsics (rubasov) ||
|-
 
| September-16-2019 || YAMAMOTO Takashi (yamamoto) ||
 
|-
 
| September-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 ===
Line 113: Line 128:
 
=== 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/
+
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 128: Line 143:
  
 
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.
+
** (ralonsoh): https://bugs.launchpad.net/neutron/+bug/1476527. Question: merge API, DB and server changes without backend ones? Or not?
 
*** More details
 
*** More details
 +
** (imalinovskiy): RBAC support for address scope and subnet pool. Core developer's opinion on this, suggestions for the implementation.
 +
*** https://bugs.launchpad.net/neutron/+bug/1862968 and https://bugs.launchpad.net/neutron/+bug/1862032
  
 
== 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:04, 20 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. I don't see summary yet.

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