Jump to: navigation, search

Difference between revisions of "Network/Meetings"

m (Community Goals)
(Bugs and Gate issues)
 
(762 intermediate revisions by 22 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Next milestone, Rocky-1, April 16 - 20
+
* Xena cycle calendar https://releases.openstack.org/xena/schedule.html
* Rocky release schedule: https://releases.openstack.org/rocky/schedule.html
+
** Next week is fina RC week and the week after is the Xena release week:
* Rocky PTG summary: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128183.html
+
*** Link to prioroty patches: shorturl.at/wDTY7
 +
*** The priority patches are candidates for RC2.
 +
* October PTG:
 +
** announcement http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023370.html
 +
** etherpad https://etherpad.opendev.org/p/neutron-yoga-ptg
 +
** for now I booked 3h slots every day, 1300-1600 UTC except Monday when there is 2h 1300 - 1500 UTC
 +
*** there will be also TC & PTLs session in Monday 1500-1700 UTC
 +
** Operators pain points: http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024487.html
 +
* OpenInfra Live event - https://openinfra.dev/live/#all-episodes - there are some interesting presentations there, maybe You would be interested in some of them,
 +
** PTG summary at http://lists.openstack.org/pipermail/openstack-discuss/2021-April/022044.html and also at http://kaplonski.pl/blog/virtual_ptg_april_2021_summary/
  
 
=== Blueprints ===
 
=== Blueprints ===
  
Rocky-1 blueprints: https://launchpad.net/neutron/+milestone/rocky-1
+
Blueprints which we should include in Xena milestones:
  
==== OVO/no API downtime ====
+
* Neutron Xena-RC2 https://bugs.launchpad.net/neutron/+milestone/xena-rc2
 +
** Perhaps this bug also a candidate for attention: https://bugs.launchpad.net/neutron/+bug/1944201
 +
*** Comes from Ironic, but this week I have seen some failures in Neutron jobs as well
 +
*** http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22error%20Datapath%20Invalid%5C%22
 +
** neutron-tempest-plugin Xena - 1.7.0 release: https://review.opendev.org/c/openstack/releases/+/809571
 +
*** Is there any patches we should include?
 +
*** https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/800758 Bump OVN version for master jobs
 +
*** https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/804238 Add logging API delete corresponding SG test
 +
*** https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/809770 Make neutron-tempest-plugin-vpnaas job OVS based
 +
*** Tap-as-a-service related patches are not urgent as I see (https://review.opendev.org/q/topic:%22taas_tests%22+(status:open%20OR%20status:merged) ), as x/tap-as-a-service-tempest-plugin covers taas
  
List here patches/topics that need core reviewer attention.
+
* Moved to neutron-next:
 
+
** https://blueprints.launchpad.net/neutron/+spec/sg-sharing-as-readonly
* add your patch here
+
** https://blueprints.launchpad.net/neutron/+spec/bfd-support-for-neutron
 +
** https://blueprints.launchpad.net/neutron/+spec/explicit-management-of-default-routes
 +
** https://blueprints.launchpad.net/neutron/+spec/multiple-external-gateways
 +
** https://blueprints.launchpad.net/neutron/+spec/bgp-enhancement
 +
** https://blueprints.launchpad.net/neutron/+spec/evacuate-agent-resources
 +
** https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes
 +
** 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/bugs/1931100
  
 
=== Community Goals ===
 
=== Community Goals ===
Line 22: Line 48:
 
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
 
* policy-in-code (Queens) -- amotoki
 
* wsgi support (Pike) -- annp
 
* Enable mutable configuration (Rocky) https://governance.openstack.org/tc/goals/rocky/enable-mutable-configuration.html -- slaweq
 
* mox3 removal (Rocky) https://bugs.launchpad.net/python-neutronclient/+bug/1753504 -- hongbin (neutronclient), amotoki (fwaas/vpnaas-dashboard), (perhaps) yamamoto (networking-midonet)
 
* python3.5 fully support https://etherpad.openstack.org/p/py3-neutron-pike
 
 
* Split Tempest Plugins into Separate Repos/Projects (Queens) : Completed (we can drop it from the next meeting)
 
** https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html#neutron
 
 
=== Starter Approved RFEs ===
 
 
This section is for advertising approved RFEs that the Neutron Drivers team have deemed suitable for new contributors:
 
 
* Network router:external field not exported: https://bugs.launchpad.net/neutron/+bug/1653932
 
  
 
=== Bugs and Gate issues ===
 
=== Bugs and Gate issues ===
  
Bug deputy report for week of March 5th: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128182.html
+
amotoki was bug deputy last week: http://lists.openstack.org/pipermail/openstack-discuss/2021-September/024972.html
  
A full hour is dedicated to this topic, and more during the following meeting:
+
More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI
  
* https://wiki.openstack.org/wiki/Meetings/NeutronCI
 
 
* [https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.tag=gate-failure Confirmed gate failures]
 
* [https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.tag=gate-failure Confirmed gate failures]
 
* [https://bugs.launchpad.net/neutron/+bugs?field.tag=needs-attention Bugs that need attention]
 
* [https://bugs.launchpad.net/neutron/+bugs?field.tag=needs-attention Bugs that need attention]
Line 55: Line 65:
 
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
 
|-
 
|-
| January-8-2018 || Hirofumi Ichihara (hichihara)
+
| Aug-9-2021 || Bernard Cafarelli (bcafarel) || switch with Miguel Lavalle (mlavalle)
 
|-
 
|-
| January-15-2018 || Gary Kotton (garyk)
+
| Aug-16-2021 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| January-22-2018 || Akihiro Motoki (amotoki)
+
| Aug-23-2021 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| January-29-2018 || Jakub Libosvar (jlibosva)
+
| Aug-30-2021 || Brian Haley (haleyb) ||
 
|-
 
|-
| February-5-2018 || Boden Russel (boden)
+
| Sep-6-2021 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| February-12-2018 || James Anziano (janzian)
+
| Sep-13-2021 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| February-19-2018 || Ihar Hrachyshka (ihrachys)
+
| Sep-20-2021 || Miguel Lavalle (mlavalle)  || switch with Bernard Cafarelli (bcafarel)
 
|-
 
|-
| February-26-2018 || Slawek Kaplonski (slaweq)
+
| Sep-27-2021 || Bence Romsics (rubasov) ||
 
|-
 
|-
| March-5-2018 || Brian Haley (haleyb)
+
| Oct-4-2021 || Rodolfo Alonso Hernandez (ralonsoh) ||
 
|-
 
|-
| March-12-2018 || Zhao Bo(bzhao)
+
| Oct-11-2021 || Lucas Alvares Gomes (lucasgomes) ||
 
|-
 
|-
| March-19-2018 || Armando Migliaccio (armax)
+
| Oct-18-2021 || Jakub Libosvar (jlibosva) ||
 
|-
 
|-
| March-26-2018 || Swaminathan Vasudevan (Swami)
+
| Oct-27-2021 || Oleg Bondarev (obondarev) ||
|-
 
| April-2-2018 || Lujin Luo(lujinluo)
 
|-
 
| April-9-2018 || YAMAMOTO Takashi (yamamoto)
 
|-
 
| April-16-2018 || Miguel Lavalle (mlavalle)
 
|-
 
| April-23-2018 || Pawel Suder (pasuder)
 
|-
 
| April-30-2018 || Hongbin Lu (hongbin)
 
 
|}
 
|}
  
 
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
 +
 +
=== L3 subteam ===
 +
No topics from Liu (This week is Mid-Autumn Festival: https://en.wikipedia.org/wiki/Mid-Autumn_Festival )
 +
 +
=== Neutron performance subteam ===
 +
 +
obondarev is doing a lot of great work in that area recently. His patches https://review.opendev.org/q/owner:oleg.bondarev%2540huawei.com+project:openstack/neutron+status:open
  
 
=== Docs ===
 
=== Docs ===
Line 102: Line 109:
 
* 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
 
=== 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)
 
* https://etherpad.openstack.org/p/osc-transition-priorities
 
* http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html
 
  
 
=== Neutron-lib, planned refactoring and other impacts ===
 
=== Neutron-lib, planned refactoring and other impacts ===
  
List here any planned potential disruption that may be caused by a new neutron-lib release and adoption of its latest features.
+
HOUSE KEEPING
 
+
* Neutron-lib work items and volunteers are being tracked via etherpad: https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list
'''DO NOT TOP POST - ADD PATCHES TO THE BOTTOM OF THE LIST'''
+
* For a list of "current" consumers who receive neutron-lib updates and consumption patches, see: http://codesearch.openstack.org/?q=neutron-lib-current
 
+
* For a complete list of neutron-lib consumption patches that may impact consumers see: https://review.openstack.org/#/q/message:%22NeutronLibImpact%22
* Open issues: https://review.openstack.org/#/q/status:open+message:%22NeutronLibImpact%22
 
** In most cases all consumers using neutron/neutron-lib stable branches are updated as part of consumption. For those who "pin" neutron/neutron-lib, they will have to address the consumption as they move their "pin" up.
 
** To see all consumption patches for a lib impact change, view the topic branch of the corresponding lib impact change (or search using the same subject).
 
* Patches that need high-level input from neutron cores: https://review.openstack.org/#/q/message:%22NeutronCoreInputNeeded%22
 
* Past issues: https://review.openstack.org/#/q/status:merged+message:%22NeutronLibImpact%22
 
* UpgradeImpact changes: https://review.openstack.org/#/q/status:open+message:%22UpgradeImpact%22+project:openstack/neutron
 
* Periodic neutron-lib check: http://grafana.openstack.org/dashboard/db/neutron-lib-failure-rate?panelId=4&fullscreen
 
  
* <Highlight patch(es) here for discussion>
+
PATCHES THAT NEED REVIEWS
 +
* 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
  
 
=== On Demand Agenda ===
 
=== On Demand Agenda ===
Line 133: Line 126:
  
 
* Topic for the meeting (keep this template, please):
 
* Topic for the meeting (keep this template, please):
** (your nickname): brief description.
+
** (nick): topic
*** More details
+
**
* Typo fixing patches
 
** (jlibosva, slaweq) There has been some patches coming from a certain group of people that just fix one typo in either a comment in code or documentation. e.g. https://review.openstack.org/#/c/540225/ . There has been already a ML thread started about this behavior in our community: http://lists.openstack.org/pipermail/openstack-dev/2017-September/122472.html Although typo fixes bring some value, they bring a very tiny value being sent one by one as that triggers CI systems and require two cores to approve such patch. This topic is to kick off the discussion about what approach should Neutron cores take.
 
* Use of existing tools to aid backporting bugfixes etc. to stable branches
 
** (aspiers) I have written a Python module [https://github.com/aspiers/git-deps git-deps] which can [https://github.com/aspiers/git-deps#use-case-1-porting-between-branches predict the complexity of porting tasks]
 
*** This could be wrapped in a non-voting check pipeline job to warn when complexity is above a certain threshold, and recommend that the backport be done now while the fix is fresh in the developer's head (or that the fix could be reworked to avoid potential conflicts during backport). Mentioned to mlavalle who suggested raising here. Worth discussing in [https://wiki.openstack.org/wiki/Meetings/NeutronCI Neutron CI meeting] as well / instead?
 
** (aspiers) I have written another (as yet unpublished) tool git-explode which wraps git-deps and allows decomposition of logically related changes into separate git branches; this could potentially be used to accelerate backporting.
 
** (aspiers) [https://blog.adamspiers.org/2013/10/02/more-uses-for-git-notes/ Unfinished / unused tools from a long time ago to aid with more complex backporting] - worth resurrecting?
 
** (ndefigueiredo) [https://bugs.launchpad.net/neutron/+bug/1753466 Stateless security groups] - Email sent out addressing this.
 
  
 
== 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/2021/?C=M;O=D networking-2021]
 +
** [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/2018/?C=M;O=D networking-2018]
 
** [http://eavesdrop.openstack.org/meetings/networking/2017/?C=M;O=D networking-2017]
 
** [http://eavesdrop.openstack.org/meetings/networking/2017/?C=M;O=D networking-2017]
 
** [http://eavesdrop.openstack.org/meetings/networking/2016/?C=M;O=D networking-2016]
 
** [http://eavesdrop.openstack.org/meetings/networking/2016/?C=M;O=D networking-2016]

Latest revision as of 14:00, 21 September 2021

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 Xena 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

amotoki was bug deputy last week: http://lists.openstack.org/pipermail/openstack-discuss/2021-September/024972.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
Aug-9-2021 Bernard Cafarelli (bcafarel) switch with Miguel Lavalle (mlavalle)
Aug-16-2021 Slawek Kaplonski (slaweq)
Aug-23-2021 Hongbin Lu (hongbin)
Aug-30-2021 Brian Haley (haleyb)
Sep-6-2021 Lajos Katona (lajoskatona)
Sep-13-2021 Akihiro Motoki (amotoki)
Sep-20-2021 Miguel Lavalle (mlavalle) switch with Bernard Cafarelli (bcafarel)
Sep-27-2021 Bence Romsics (rubasov)
Oct-4-2021 Rodolfo Alonso Hernandez (ralonsoh)
Oct-11-2021 Lucas Alvares Gomes (lucasgomes)
Oct-18-2021 Jakub Libosvar (jlibosva)
Oct-27-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

L3 subteam

No topics from Liu (This week is Mid-Autumn Festival: https://en.wikipedia.org/wiki/Mid-Autumn_Festival )

Neutron performance subteam

obondarev is doing a lot of great work in that area recently. His patches https://review.opendev.org/q/owner:oleg.bondarev%2540huawei.com+project:openstack/neutron+status:open

Docs

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

Previous meeting logs