Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Blueprints)
 
Line 1: Line 1:
 +
The OpenStack Networking Team ([[Neutron]]) holds public meetings as advertised on [http://eavesdrop.openstack.org/#Neutron_Team_Meeting OpenStack IRC Meetings Calendar]. If you are unable to attend, please check the most recent [http://eavesdrop.openstack.org/meetings/networking/ logs.]
  
The OpenStack Networking Team ([[Neutron]]) holds public meetings as advertised on [http://eavesdrop.openstack.org/#Neutron_Team_Meeting OpenStack IRC Meetings Calendar]. If you are unable to attend, please check the most recent [http://eavesdrop.openstack.org/meetings/networking/ logs.]
+
'''Ping list''': bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki, haleyb, ralonsoh
  
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
 +
* Caracal / 2024.1 schedule: https://releases.openstack.org/caracal/schedule.html
 +
** Release countdown - see Thierry's email for more info:
 +
*** https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/ZXHVRNGEMCZGOK4YG5EQDNXTEU24CJ5T/
 +
** We are now final RC phase (R - 1)
 +
*** Final RC deadline: March 28th, 2024 (R-1 week)
 +
*** Final 2024.1 Caracal release: April 3rd, 2024
 +
*** stable/2024.1 branches have been created
 +
**** Release-critical bugs must be cherry-picked to stable/2024.1
 +
**** https://review.opendev.org/q/project:openstack/neutron+branch:stable/2024.1
 +
 +
* I proposed Ihar as neutron core (again) - please vote +1/-1 on the ML
 +
** https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/DWH32U4SFZGR3Y6A6LVQFVTZLAFKILMJ/
 +
 +
* Dalmatian / 2024.2 schedule proposed: https://review.opendev.org/c/openstack/releases/+/906050
 +
** PTG April 8-12, please register if have not already
 +
*** https://ptg2024.openinfra.dev/
 +
*** Please also add name and topics to Etherpad
 +
**** https://etherpad.opendev.org/p/apr2024-ptg-neutron
 +
 +
* Reminder: If you have a topic for the drivers meeting on Friday, please add it to the wiki @ https://wiki.openstack.org/wiki/Meetings/NeutronDrivers
 +
 +
* Ussuri and Train have transitioned to EOL
 +
** https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/UJ7Y76LRWTZQSSDAGMPWCCVVGGIX3TOG/
 +
 +
* Yoga/Xena/Wallaby/Victoria have all transitioned to "unmaintained"
 +
** https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/V7H6M5ANYOMFWSZ5BJSWAXVNQCUXI6D7/
 +
 +
* (Permanent link during this release) Caracal (2024.1) cycle PTG summary and etherpad:
 +
** Caracal (PTG): https://etherpad.opendev.org/p/oct2023-ptg-neutron
 +
*** PTG links (all projects): https://ptg.opendev.org/etherpads.html
 +
 +
* Caracal (2024.1) cycle links:
 +
** Caracal (PTG): https://etherpad.opendev.org/p/oct2023-ptg-neutron
  
* Release countdown for week R-0 - http://lists.openstack.org/pipermail/openstack-dev/2016-September/104809.html
+
* Permanent links:
 +
** OpenInfra Live event - https://openinfra.dev/live/#all-episodes - there are some interesting presentations there, maybe You would be interested in some of them
  
=== Blueprints ===
+
=== Bugs and Gate issues ===
 +
* Report from lajoskatona:
 +
** https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/7HCJITIBJRTM6ULYQK6STMBA5Q3M22EA/
  
Current milestone: https://launchpad.net/neutron/+milestone/ocata-1
+
* Bugs without assignee or to be commented:
 +
** https://bugs.launchpad.net/neutron/+bug/2058433
 +
*** Might be related to https://bugs.launchpad.net/neutron/+bug/2035281
  
=== Bugs and Gate failures ===
+
* This week ykarel is the bug deputy, next week will be mtomaska
  
Approximate stats for the current cycle:
+
* Current bug count this week: 720, down 3 from last week
 +
** [https://bugs.launchpad.net/neutron/?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on All neutron bugs]
  
* From Newton beginning (Mar-16-2016):
+
* More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI
** Total reports: '''789'''
 
*** Fix released: '''308'''
 
*** Unassigned: '''104'''
 
**** New: '''39'''
 
**** Incomplete: '''30'''
 
**** Confirmed: '''26'''
 
**** Triaged: '''10'''
 
  
 
* [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]
Line 31: Line 64:
 
==== Bug deputy ====  
 
==== Bug deputy ====  
  
Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.
+
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:  
 
 
Previous deputies in order per week: iharchys, regXboi, markmcclain, armax, mestery, mangelajo, garyk, rosella_s, dougwig, HenryG, carl_baldwin, amotoki, kevinbenton, amuller, Zzelle, mlavalle, njohnston, mhickey, rosella_s, dasm, scheuran, HenryG, Amotoki, reedip, blogan, dougwig, armax, regXboi, haleyb, hichihara, carl_baldwin
 
 
 
Next weeks:
 
 
 
 
{| class="wikitable" style="text-align: center;"
 
{| class="wikitable" style="text-align: center;"
 
|-
 
|-
! Date !! who  
+
! Date !! who !! note
 
|-
 
|-
| May-30-2016 || kevinbenton
+
| 2024-3-25 || Yatin Karel (ykarel) ||
 
|-
 
|-
| Jun-6-2016 || mangelajo
+
| 2024-4-1 || Miro Tomaska (mtomaska) ||
 
|-
 
|-
| Jun-13-2016 || dasm
+
| 2024-4-8 || Bernard Cafarelli (bcafarel) ||
 
|-
 
|-
| Jun-20-2016 || john-davidge
+
| 2024-4-15 || Elvira García Ruiz (elvira) ||
 
|-
 
|-
| Jun-27-2016 || rossella_s
+
| 2024-4-22 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| Jul-4-2016 || johndperkins
+
| 2024-4-29 || Brian Haley (haleyb) ||
 
|-
 
|-
| Jul-11-2016 || blogan
+
| 2024-5-6 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| Jul-18-2016 || mlavalle
+
| 2024-5-13 || Miguel Lavalle (mlavalle)  ||
 
|-
 
|-
| Jul-25-2016 || jlibosva
+
| 2024-5-20 || Rodolfo Alonso Hernandez (ralonsoh) ||
 
|-
 
|-
| Aug-01-2016 || electrocucaracha
+
| 2024-5-27 || Bence Romsics (rubasov) ||
 
|-
 
|-
| Aug-08-2016 || njohnston
+
| 2024-6-3 || Lucas Alvares Gomes (lucasgomes) ||
 
|-
 
|-
| Aug-15-2016 || armax
+
| 2024-6-10 || Jakub Libosvar (jlibosva) ||
 
|-
 
|-
| Aug-30-2016 || haleyb
+
| 2024-6-17 || Oleg Bondarev (obondarev) ||
 
|-
 
|-
| Sep-04-2016 || jschwarz
+
| 2024-6-24 || Mamatisa Nurmatov (isabek) ||
 
|-
 
|-
| Sep-12-2016 || hichihara
+
| 2024-7-1 || Lajos Katona (lajoskatona) ||
|-
 
| Sep-19-2016 || ihrachys
 
|-
 
| Sep-26-2016 || ihrachys
 
 
|}
 
|}
  
=== Docs ===
+
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
 +
 
 +
=== ryu os-ken ===
 +
 
 +
* To move os-ken from https://storyboard.openstack.org/ to launchpad.
 +
** (former) Story board to track ryu backports: https://storyboard.openstack.org/#!/story/2009283
  
* The future of OpenStack documentation - http://lists.openstack.org/pipermail/openstack-dev/2016-July/099012.html
+
* Active os-ken patches: https://review.opendev.org/q/project:openstack/os-ken+status:open
  
=== Transition to OSC ===
+
* New patches in ryu:
Status of changes to deliver OSC
 
* http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html
 
  
=== Moving to Keystone v3 API in Neutron ===
+
=== Specs ===
* https://github.com/openstack/neutron-specs/blob/master/specs/newton/moving-to-keystone-v3.rst
 
  
=== Neutron-lib ===
+
* Specs: https://review.opendev.org/q/project:openstack%252Fneutron-specs+status:open
* https://review.openstack.org/#/q/project:openstack/neutron-lib+status:open
+
* Open reviews:
 +
** https://review.opendev.org/c/openstack/neutron-specs/+/899209?usp=search
 +
** https://review.opendev.org/c/openstack/neutron-specs/+/899210?usp=search
 +
 
 +
=== Community Goals ===
 +
 
 +
* Last TC meeting summary: https://meetings.opendev.org/meetings/tc/2023/tc.2023-11-14-18.00.html
 +
 
 +
* Current Selected (Active) Goals:
 +
** Add support for the service role in neutron API policies
 +
*** Service role implementation: https://bugs.launchpad.net/neutron/+bug/2026182
 +
**** Patches complete, Slawek to follow-up with Gmann about integrated testing for it all
 +
** Neutron client deprecation
 +
*** https://bugs.launchpad.net/neutron/+bug/1999774
 +
*** Agenda: https://etherpad.opendev.org/p/python-neutronclient_deprecation
 +
*** Active patches to review:
 +
**** https://review.opendev.org/c/openstack/horizon/+/891205
 +
 
 +
=== Neutron-lib, planned refactoring and other impacts ===
 +
 
 +
* (nothing)
  
 
=== 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:
 
+
* Week of March 25th
* Feature Classification Framework/Matrix
+
** (irc nick) topic
** ankur-gupta-f: The feature classification matrix will provide information about plugins and the features they support.
+
** (haleyb) https://review.opendev.org/c/openstack/neutron/+/914146 (update lieutenants)
*** RFE has been approved. Need to improve Neutron documentation about various backends and the feature they support: https://review.openstack.org/#/c/318192/ https://review.openstack.org/#/c/324048/
+
** (haleyb) Updates to job templates for 2024.1/2 - please review
** ihrachys: adding stable deputy role to arrange sustain proactive backports process:
+
*** https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/913450 (merged)
*** a new process to handle stable backports proposed: http://lists.openstack.org/pipermail/openstack-dev/2016-June/098552.html
+
*** https://review.opendev.org/c/openstack/neutron/+/913451
* Let operator update subnet.cidr:
+
*** https://review.opendev.org/c/openstack/neutron/+/913923
** yottatsa: as an operator I want to expand or shrink Public network without re-allocating all Floating IPs.
 
*** Although I don't see any reason to abandon it, there are many roadblocks like "unexpected side effects on plugins that do not handle well the CIDR update" on the way. RFE https://bugs.launchpad.net/neutron/+bug/1605343
 
* Transaction guards on *_port methods, and l3 service plugins.
 
** oanson: create_port, update_port, and delete_port have a transaction guard which breaks existing l3 service plugins. There is a workaround (GUARD_TRANSACTION=false), but what is the long-term solution?
 
*** I understand that GUARD_TRANSACTION=false is a workaround. What would be the correct solution to continue using port modification functions on the core plugin in case of transactions in the service plugin code, or how to correct the client code? I ran into this in Dragonflow, but I have seen it in Midonet as well. Neutron change: https://review.openstack.org/#/c/275110/ , Dragonflow change: https://review.openstack.org/#/c/355736/ .
 
* Distributed gateway for optimized local SNAT
 
** ishafran: There is a blueprint describing new feature: https://blueprints.launchpad.net/neutron/+spec/neutron-local-snat
 
*** I would like to understand the reasons the blueprint marked obsolete. Is there a developed / in development patch that solves the subject ?
 
* Recompiling a Cirros fork at the gate
 
** jschwarz: Basically, getting Cirros to support stuff that we need to test is going no where, so instead we propose forking Cirros and adding support for what we need on our own.
 
*** https://etherpad.openstack.org/p/cirros-respin . This has gotten support from at least 2 cores already (ajo, kevinbenton)
 
 
 
* Topic for the meeting (keep this template, please):
 
** (your nickname): brief description.
 
*** 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/2024/?C=M;O=D networking-2024]
 +
** [http://eavesdrop.openstack.org/meetings/networking/2023/?C=M;O=D networking-2023]
 +
** [http://eavesdrop.openstack.org/meetings/networking/2022/?C=M;O=D networking-2022]
 +
** [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/2016/?C=M;O=D networking-2016]
 
** [http://eavesdrop.openstack.org/meetings/networking/2016/?C=M;O=D networking-2016]
 
** [http://eavesdrop.openstack.org/meetings/networking/2015/?C=M;O=D networking-2015]
 
** [http://eavesdrop.openstack.org/meetings/networking/2015/?C=M;O=D networking-2015]
Line 124: Line 163:
 
** [http://eavesdrop.openstack.org/meetings/quantum/2013/?C=M;O=D quantum-2013]
 
** [http://eavesdrop.openstack.org/meetings/quantum/2013/?C=M;O=D quantum-2013]
 
** [http://eavesdrop.openstack.org/meetings/quantum/2012/?C=M;O=D quantum-2012]
 
** [http://eavesdrop.openstack.org/meetings/quantum/2012/?C=M;O=D quantum-2012]
* Older meeting notes are here:  ../MeetingLogs.
 

Latest revision as of 14:50, 26 March 2024

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.

Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki, haleyb, ralonsoh

Announcements / Reminders

Bugs and Gate issues

  • This week ykarel is the bug deputy, next week will be mtomaska

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
2024-3-25 Yatin Karel (ykarel)
2024-4-1 Miro Tomaska (mtomaska)
2024-4-8 Bernard Cafarelli (bcafarel)
2024-4-15 Elvira García Ruiz (elvira)
2024-4-22 Slawek Kaplonski (slaweq)
2024-4-29 Brian Haley (haleyb)
2024-5-6 Akihiro Motoki (amotoki)
2024-5-13 Miguel Lavalle (mlavalle)
2024-5-20 Rodolfo Alonso Hernandez (ralonsoh)
2024-5-27 Bence Romsics (rubasov)
2024-6-3 Lucas Alvares Gomes (lucasgomes)
2024-6-10 Jakub Libosvar (jlibosva)
2024-6-17 Oleg Bondarev (obondarev)
2024-6-24 Mamatisa Nurmatov (isabek)
2024-7-1 Lajos Katona (lajoskatona)

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

ryu os-ken

  • New patches in ryu:

Specs

Community Goals

Neutron-lib, planned refactoring and other impacts

  • (nothing)

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