Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Neutron-lib and planned neutron refactoring)
 
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 ===
 +
* Dalmatian / 2024.2 schedule: https://releases.openstack.org/dalmatian/schedule.html
 +
** We are now in Dalmatian release week (R - 23)
 +
** PTG was April 8-12
 +
*** https://etherpad.opendev.org/p/apr2024-ptg-neutron
 +
 +
* Ironic email
 +
** https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/5SX35AQZ65G6HWQ7WARLJTJK3ASAOWNU/
  
* Allowing Teams Based on Vendor-specific Drivers http://lists.openstack.org/pipermail/openstack-dev/2016-November/108074.html
+
* 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
  
=== Blueprints ===
+
* Proposal for Zed to go Unmaintained
 +
** https://review.opendev.org/c/openstack/releases/+/916492
  
Current milestone: https://launchpad.net/neutron/+milestone/ocata-2
+
* Ussuri and Train have transitioned to EOL
 +
** https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/UJ7Y76LRWTZQSSDAGMPWCCVVGGIX3TOG/
  
==== OVO/no API downtime ====
+
* Yoga/Xena/Wallaby/Victoria have all transitioned to "unmaintained"
 +
** https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/V7H6M5ANYOMFWSZ5BJSWAXVNQCUXI6D7/
  
List here patches/topics that need core reviewer attention.
+
* (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
  
* add your patch here
+
* Caracal (2024.1) cycle links:
 +
** Caracal (PTG): https://etherpad.opendev.org/p/oct2023-ptg-neutron
 +
 
 +
* 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
  
 
=== Bugs and Gate issues ===
 
=== Bugs and Gate issues ===
 +
* Report from elvira:
 +
** https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/6OLKNSOX2RRTYMMAGXLH7IEAI6VERF2B/
  
Approximate stats for the current cycle:
+
* Bugs without assignee or to be commented:
 +
** [fwaas] Duplicate entry <uuid> for key default_firewall_groups.PRIMARY'
 +
*** https://bugs.launchpad.net/neutron/+bug/2061883
  
* From the beginning of Ocata (Sept-16-2016):
+
* This week slaweq is the bug deputy, next week will be haleyb
** Total reports: '''329'''
+
 
*** Fix released: '''170'''
+
* Current bug count this week: 723, up 3 from last week
*** Unassigned: '''123'''
+
** [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]
**** New: '''27'''
+
 
**** Incomplete: '''25'''
+
* More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI
**** Confirmed: '''26'''
 
**** Triaged: '''4'''
 
  
 
* [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 37: Line 56:
 
==== Bug deputy ====  
 
==== Bug deputy ====  
  
Use this section to keep track of who volunteers for the 'bug deputy' role. Instructions and pointers available at:
+
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:  
 
 
http://docs.openstack.org/developer/neutron/policies/bugs.html#neutron-bug-deputy
 
 
 
This is usually edited at the end of the IRC Meeting.
 
 
 
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, kevinbenton, mangelajo, dasm, john-davidge, rossella_s, johndperkins, blogan, mlavalle, jlibosva, electrocucaracha, njohnston, armax, haleyb, jschwarz, hichihara, ihrachys, ihrachys, dougwig, john-davidge, dasanind_, dasm, dougwig
 
 
 
Next weeks:
 
 
 
 
{| class="wikitable" style="text-align: center;"
 
{| class="wikitable" style="text-align: center;"
 
|-
 
|-
! Date !! who  
+
! Date !! who !! note
 
|-
 
|-
| Nov-7-2016 || andreas_s
+
| 2024-4-22 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| Nov-14-2016 || electrocucaracha
+
| 2024-4-29 || Brian Haley (haleyb) ||
 
|-
 
|-
| Nov-21-2016 || kevinbenton
+
| 2024-5-6 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| Nov-28-2016 || ihrachys
+
| 2024-5-13 || Miguel Lavalle (mlavalle)  ||
 
|-
 
|-
| Dec-05-2016 || haleyb
+
| 2024-5-20 || Rodolfo Alonso Hernandez (ralonsoh) ||
 
|-
 
|-
| Dec-12-2016 || mlavalle
+
| 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) ||
 +
|-
 +
| 2024-7-8 || Yatin Karel (ykarel) ||
 +
|-
 +
| 2024-7-15 || Miro Tomaska (mtomaska) ||
 +
|-
 +
| 2024-7-22 || Bernard Cafarelli (bcafarel) ||
 +
|-
 +
| 2024-7-29 || Elvira García Ruiz (elvira) ||
 
|}
 
|}
  
=== 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
  
* The future of OpenStack documentation - http://lists.openstack.org/pipermail/openstack-dev/2016-July/099012.html
+
=== ryu os-ken ===
* Documentation bugs - https://bugs.launchpad.net/neutron/+bugs?field.tag=doc
 
  
=== Transition to OSC ===
+
* To move os-ken from https://storyboard.openstack.org/ to launchpad.
Status of changes to deliver OSC
+
** (former) Story board to track ryu backports: https://storyboard.openstack.org/#!/story/2009283
* http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html
 
  
=== Neutron-lib and planned neutron refactoring ===
+
* Active os-ken patches: https://review.opendev.org/q/project:openstack/os-ken+status:open
  
List here any planned potential disruption that may be caused by a new neutron-lib release and adoption of its latest features.
+
* New patches in ryu:
  
* periodic neutron-lib check: http://grafana.openstack.org/dashboard/db/neutron-lib-failure-rate?panelId=4&fullscreen
+
=== Specs ===
* Open issues: https://review.openstack.org/#/q/status:open+message:%22NeutronLibImpact%22
+
 
* Past issues: https://review.openstack.org/#/q/status:merged+message:%22NeutronLibImpact%22
+
* Specs: https://review.opendev.org/q/project:openstack%252Fneutron-specs+status:open
* Removal of *_MAX_LEN constants, use db *_FIELD_SIZE constants from neutron-lib instead. (These reviews are based on top of remove-PLURALS reviews.)
+
* Open reviews:
  * Core patch: https://review.openstack.org/399891
+
** https://review.opendev.org/c/openstack/neutron-specs/+/899210?usp=search
  * Subprojects: https://review.openstack.org/#/q/status:open+topic:use-db-field-sizes
+
 
  * See also: http://lists.openstack.org/pipermail/openstack-dev/2016-October/105789.html
+
=== Community Goals ===
* Removal of long-since deprecated model_base mixins from neutron core.
+
 
  * Core patch: https://review.openstack.org/403329
+
* Last TC meeting summary: https://meetings.opendev.org/meetings/tc/2023/tc.2023-11-14-18.00.html
  * Subprojects: https://review.openstack.org/#/q/status:open+topic:use-lib-model_base
+
 
* <Highlight patch(es) here for discussion>
+
* 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 April 15th
* Topic for the meeting (keep this template, please):
+
** (irc nick) topic
** (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 105: Line 149:
 
** [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 17:09, 23 April 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 slaweq is the bug deputy, next week will be haleyb

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-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)
2024-7-8 Yatin Karel (ykarel)
2024-7-15 Miro Tomaska (mtomaska)
2024-7-22 Bernard Cafarelli (bcafarel)
2024-7-29 Elvira García Ruiz (elvira)

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:

  • Week of April 15th
    • (irc nick) topic

Previous meeting logs