Jump to: navigation, search

Difference between revisions of "Network/Meetings"

m (→‎Community Goals)
 
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 - 24)
 +
** PTG was April 8-12
 +
*** https://etherpad.opendev.org/p/apr2024-ptg-neutron
  
−
* Next milestone, Rocky-1, April 16 - 20
+
* 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
−
* Rocky release schedule: https://releases.openstack.org/rocky/schedule.html
 
−
* Rocky PTG summary: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128183.html
 
  
−
=== Blueprints ===
+
* Ussuri and Train have transitioned to EOL
 +
** https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/UJ7Y76LRWTZQSSDAGMPWCCVVGGIX3TOG/
  
−
Rocky-1 blueprints: https://launchpad.net/neutron/+milestone/rocky-1
+
* Yoga/Xena/Wallaby/Victoria have all transitioned to "unmaintained"
 +
** https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/V7H6M5ANYOMFWSZ5BJSWAXVNQCUXI6D7/
  
−
==== OVO/no API downtime ====
+
* (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
  
−
List here patches/topics that need core reviewer attention.
+
* Caracal (2024.1) cycle links:
 +
** Caracal (PTG): https://etherpad.opendev.org/p/oct2023-ptg-neutron
  
−
* add your patch here
+
* 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
  
−
=== Community Goals ===
+
=== Bugs and Gate issues ===
−
 
+
* Report from bcafarel:
−
This slot is to used to track the progress of the community goals.
+
** https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/YBZCITD44VLW2LGSHTOJUJSBLARL4SFQ/
−
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)
+
* Bugs without assignee or to be commented:
−
** https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html#neutron
+
** https://bugs.launchpad.net/neutron/+bug/2059405
 +
*** OVN DNS not working as documented
 +
** https://bugs.launchpad.net/neutron/+bug/2060828
 +
*** [OVN] Changing public network MTU does not update router port gateway_mtu option
  
−
=== Starter Approved RFEs ===
+
* This week elvira is the bug deputy, next week will be slaweq
  
−
This section is for advertising approved RFEs that the Neutron Drivers team have deemed suitable for new contributors:
+
* Current bug count this week: 720, same as 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]
  
−
* Network router:external field not exported: https://bugs.launchpad.net/neutron/+bug/1653932
+
* More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI
  
−
=== Bugs and Gate issues ===
 
−
 
−
Bug deputy report for week of March 5th: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128182.html
 
−
 
−
A full hour is dedicated to this topic, and more during the following meeting:
 
−
 
−
* 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 53: Line 52:
 
==== Bug deputy ====  
 
==== 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
+
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:  
−
 
 
−
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:  
 
−
 
 
 
{| class="wikitable" style="text-align: center;"
 
{| class="wikitable" style="text-align: center;"
 
|-
 
|-
−
! Date !! who  
+
! Date !! who !! note
 
|-
 
|-
−
| January-8-2018 || Hirofumi Ichihara (hichihara)
+
| 2024-4-15 || Elvira García Ruiz (elvira) ||
 
|-
 
|-
−
| January-15-2018 || Gary Kotton (garyk)
+
| 2024-4-22 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
−
| January-22-2018 || Akihiro Motoki (amotoki)
+
| 2024-4-29 || Brian Haley (haleyb) ||
 
|-
 
|-
−
| January-29-2018 || Jakub Libosvar (jlibosva)
+
| 2024-5-6 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
−
| February-5-2018 || Boden Russel (boden)
+
| 2024-5-13 || Miguel Lavalle (mlavalle) ||
 
|-
 
|-
−
| February-12-2018 || James Anziano (janzian)
+
| 2024-5-20 || Rodolfo Alonso Hernandez (ralonsoh) ||
 
|-
 
|-
−
| February-19-2018 || Ihar Hrachyshka (ihrachys)
+
| 2024-5-27 || Bence Romsics (rubasov) ||
 
|-
 
|-
−
| February-26-2018 || Slawek Kaplonski (slaweq)
+
| 2024-6-3 || Lucas Alvares Gomes (lucasgomes) ||
 
|-
 
|-
−
| March-5-2018 || Brian Haley (haleyb)
+
| 2024-6-10 || Jakub Libosvar (jlibosva) ||
 
|-
 
|-
−
| March-12-2018 || Zhao Bo(bzhao)
+
| 2024-6-17 || Oleg Bondarev (obondarev) ||
 
|-
 
|-
−
| March-19-2018 || Armando Migliaccio (armax)
+
| 2024-6-24 || Mamatisa Nurmatov (isabek) ||
 
|-
 
|-
−
| March-26-2018 || Swaminathan Vasudevan (Swami)
+
| 2024-7-1 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
−
| April-2-2018 || Lujin Luo(lujinluo)
+
| 2024-7-8 || Yatin Karel (ykarel) ||
 
|-
 
|-
−
| April-9-2018 || YAMAMOTO Takashi (yamamoto)
+
| 2024-7-15 || Miro Tomaska (mtomaska) ||
 
|-
 
|-
−
| April-16-2018 || Miguel Lavalle (mlavalle)
+
| 2024-7-22 || Bernard Cafarelli (bcafarel) ||
−
|-
 
−
| 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
  
−
=== Docs ===
+
=== ryu os-ken ===
  
−
* The future of OpenStack documentation - http://lists.openstack.org/pipermail/openstack-dev/2016-July/099012.html
+
* To move os-ken from https://storyboard.openstack.org/ to launchpad.
−
* Documentation bugs - https://bugs.launchpad.net/neutron/+bugs?field.tag=doc
+
** (former) Story board to track ryu backports: https://storyboard.openstack.org/#!/story/2009283
  
−
=== CLI/SDK ===
+
* Active os-ken patches: https://review.opendev.org/q/project:openstack/os-ken+status:open
  
−
SDK migration of neutronclient python bindings
+
* New patches in ryu:
−
https://etherpad.openstack.org/p/neutron-openstacksdk-migration
 
  
−
Status of changes to deliver OSC (this needs to be revisit)
+
=== Specs ===
−
* 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 ===
+
* Specs: https://review.opendev.org/q/project:openstack%252Fneutron-specs+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 ===
  
−
List here any planned potential disruption that may be caused by a new neutron-lib release and adoption of its latest features.
+
* Last TC meeting summary: https://meetings.opendev.org/meetings/tc/2023/tc.2023-11-14-18.00.html
  
−
'''DO NOT TOP POST - ADD PATCHES TO THE BOTTOM OF THE LIST'''
+
* 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
  
−
* Open issues: https://review.openstack.org/#/q/status:open+message:%22NeutronLibImpact%22
+
=== Neutron-lib, planned refactoring and other impacts ===
−
** 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>
+
* (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
 
−
* 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/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/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 20:43, 16 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 elvira is the bug deputy, next week will be slaweq

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-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)
2024-7-8 Yatin Karel (ykarel)
2024-7-15 Miro Tomaska (mtomaska)
2024-7-22 Bernard Cafarelli (bcafarel)

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

Retrieved from "https://wiki.openstack.org/w/index.php?title=Network/Meetings&oldid=184683"