Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Open Items for Liberty: (reviews needed))
(On Demand Agenda)
 
Line 1: Line 1:
  
{{:Network/Header}}
+
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.]
'''Meeting time: The OpenStack Networking Team ([[Neutron]]) holds public meetings alternating between Mondays at 2100 UTC (#openstack-meeting) and Tuesdays at 1400 UTC (#openstack-meeting). Everyone is encouraged to attend.'''
 
  
== Apologies for Absence ==
+
=== Announcements / Reminders ===
 +
* Zed schedule: https://releases.openstack.org/zed/schedule.html
 +
* Release countdown for week R-20: #link http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028537.html
 +
* pike branches are deleted
 +
 
 +
* OpenInfra Live event - https://openinfra.dev/live/#all-episodes - there are some interesting presentations there, maybe You would be interested in some of them
 +
* Zed cycle PTG summary: https://lists.openstack.org/pipermail/openstack-discuss/2022-April/028164.html
 +
 
 +
=== Bugs and Gate issues ===
  
== Agenda for Next Neutron Team Meeting ==
+
* Report from lajoskatona https://lists.openstack.org/pipermail/openstack-discuss/2022-May/028546.html
'''Monday(9/8/2015) at 1400 UTC on #openstack-meeting'''
+
** OVN revision_number infinite update loop (#link https://bugs.launchpad.net/neutron/+bug/1973347 )
  
=== Announcements / Reminders ===
+
This week slaweq is the deputy and next week bcafarel will be.
* Tempest plugin interface is ready to roll!
+
 
** We can now add external tempest tests in the neutron repo
+
More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI
** Example change: https://review.openstack.org/#/c/201955/
+
 
** Docs: http://docs.openstack.org/developer/tempest/plugin.html
+
* [https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.tag=gate-failure Confirmed gate failures]
* Liberty Release Notes
+
* [https://bugs.launchpad.net/neutron/+bugs?field.tag=needs-attention Bugs that need attention]
** Lets focus on updating these
+
* [https://bugs.launchpad.net/neutron/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=OPINION&field.status%3Alist=INVALID&field.status%3Alist=WONTFIX&field.status%3Alist=EXPIRED&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.tag=deprecation All bug reports associated to deprecation issues]
** https://wiki.openstack.org/wiki/ReleaseNotes/Liberty#OpenStack_Liberty_Release_Notes
+
* [https://goo.gl/KtEwbL Bugs Sheet]
* Neutron Policies are documented here:
+
* [http://grafana.openstack.org/dashboard/db/neutron-failure-rate Grafana dashboards]
** http://git.openstack.org/cgit/openstack/neutron/tree/doc/source/policies
+
 
 +
==== 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:
 +
 
 +
{| class="wikitable" style="text-align: center;"
 +
|-
 +
! Date !! who !! note
 +
|-
 +
| May-9-2022 || Lajos Katona (lajoskatona) ||
 +
|-
 +
| May-16-2022 || Bernard Cafarelli (bcafarel) || Switched with slaweq
 +
|-
 +
| May-23-2022 || Slawek Kaplonski (slaweq) || Switched with bcafarel
 +
|-
 +
| May-30-2022 || Brian Haley (haleyb)  ||
 +
|-
 +
| June-6-2022 || Akihiro Motoki (amotoki) ||
 +
|-
 +
| June-13-2022 || Miguel Lavalle (mlavalle)  ||
 +
|-
 +
| June-20-2022 || Bence Romsics (rubasov) ||
 +
|-
 +
| June-27-2022 || Rodolfo Alonso Hernandez (ralonsoh) ||
 +
|-
 +
| July-4-2022 || Lucas Alvares Gomes (lucasgomes) ||
 +
|-
 +
| July-11-2022 || Jakub Libosvar (jlibosva) ||
 +
|-
 +
| July-18-2022 || Oleg Bondarev (obondarev) ||
 +
|-
 +
| July-25-2022 || Mamatisa Nurmatov (isabek) ||
 +
|-
 +
| August-1-2022 || 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
 +
 
 +
=== L3 subteam ===
 +
 
 +
=== ryu os-ken ===
 +
 
 +
* No new changes in ryu.
 +
 
 +
https://ethercalc.openstack.org/make_os-ken_and_ryu_sync
 +
 
 +
=== Outreachy ideas ===
 +
 
 +
* The selected "low-hanging-RFE":
 +
** https://bugs.launchpad.net/neutron/+bug/1870319 - [RFE] Network cascade deletion API call
 +
** Meeting discussion: https://meetings.opendev.org/meetings/networking/2022/networking.2022-03-01-14.03.log.html#l-42
 +
** Project on Outreachy page: https://www.outreachy.org/outreachy-may-2022-internship-round/communities/openstack/add-possibility-for-network-cascade-deletion-in-op/cfp/
 +
 
 +
Outreachy mail for 2022 spring semester: http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027239.html
 +
Summary from Dmitry Tantsur: https://owlet.today/posts/how-to-propose-the-best-project-for-outreachy/
 +
Last meeting discussion: https://meetings.opendev.org/meetings/networking/2022/networking.2022-02-22-14.08.log.html#l-73
 +
 
 +
* RFE:
 +
** https://bugs.launchpad.net/neutron/+bug/1042049 -  [RFE] auto-associate floating ips,
 +
** https://bugs.launchpad.net/neutron/+bug/1824856 -  [RFE] Add new state "ERROR" for HA routers,
 +
** https://bugs.launchpad.net/neutron/+bug/1828494 - [RFE][L3] l3-agent should have its capacity,
 +
** https://bugs.launchpad.net/neutron/+bug/1870319 - [RFE] Network cascade deletion API call,
 +
** https://bugs.launchpad.net/neutron/+bug/1892200 -  Make keepalived healthcheck more configurable,
 +
** https://bugs.launchpad.net/neutron/+bug/1915151 -  [RFE] There should be a way to set ethertype for the vlan_transparent networks,
 +
* DOC fix, unit tests
 +
** ?
 +
* Check overlapping tests between neutron-tempest-plugin and tempest
 +
** example: https://review.opendev.org/c/openstack/tempest/+/824440
 +
 
 +
=== Neutron performance subteam ===
 +
 
 +
=== Blueprints ===
 +
 
 +
Blueprints which we should include in Yoga milestones:
 +
 
 +
=== Community Goals ===
  
=== Bugs ===
+
* TC discussed this topic: http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026280.html (look for "Community-wide goal updates")
 +
** mail from gmann: http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026218.html
 +
** Current Selected (Active) Goals:
 +
*** Migrate from oslo.rootwrap to oslo.privsep
 +
*** Consistent and Secure Default RBAC
  
<br>
+
** Etherpad with notes: https://etherpad.opendev.org/p/policy-popup-yoga-ptg
Important bugs:
+
** https://review.opendev.org/c/openstack/governance/+/815158
** [https://bugs.launchpad.net/neutron/+bug/1484148] neutronclient gate broken following VPNaaS infra changes
 
** [https://bugs.launchpad.net/neutron/+bug/1488282] Gate failures with 'the resource could not be found'
 
** [https://bugs.launchpad.net/neutron/+bug/1477192] neutron test_multi_prefix_slaac failing in the gate with ping failures starting around 7/22
 
** [https://bugs.launchpad.net/neutron/+bug/1439696] Referencing a lb-healthmonitor ID for the first time from Heat would fail
 
** [https://bugs.launchpad.net/neutron/+bug/1163569] security groups don't work with vip and ovs plugin
 
** [https://bugs.launchpad.net/neutron/+bug/1491131] Ipset race condition
 
  
* The following bugs are hurting the functional job in the gate:
+
This slot is to used to track the progress of the community goals.
** https://bugs.launchpad.net/neutron/+bugs?field.tag=functional-tests
+
https://governance.openstack.org/tc/goals/index.html#release-cycles
  
* Linuxbridge Gate Parity Bugs
+
=== Docs ===
** [https://bugs.launchpad.net/neutron/+bug/1312016] nova libvirtError: Unable to add bridge brqxxx-xx port tapxxx-xx: Device or resource busy
 
<br/>
 
  
=== Docs (emagana)===
+
* 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
  
==== Open Items for Liberty: (reviews needed) ====
+
=== Neutron-lib, planned refactoring and other impacts ===
* https://review.openstack.org/#/q/status:open+project:openstack/openstack-manuals,n,z
 
  
* QoS Sub Chapter: https://review.openstack.org/#/c/221990/ (WIP - emagana and ajo)
+
HOUSE KEEPING
* <strike>IPv6 Prefix: https://review.openstack.org/#/c/178739  (Merged)
+
* Neutron-lib work items and volunteers are being tracked via etherpad: https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list
* <strike>Update PD section to mention plugin configuration: https://review.openstack.org/#/c/182373/ (Merged)
+
* For a list of "current" consumers who receive neutron-lib updates and consumption patches, see: http://codesearch.openstack.org/?q=neutron-lib-current
* <strike>Update PD section to include dhcpv6_pd_agent info: https://review.openstack.org/#/c/182375/ (Merged)
+
* For a complete list of neutron-lib consumption patches that may impact consumers see: https://review.openstack.org/#/q/message:%22NeutronLibImpact%22
* <strike>Update L3 HA scenarios: https://review.openstack.org/#/c/216462/ </strike> (Need Assaf Muller Approval, Merged)
 
* <strike>Namespaces: https://review.openstack.org/#/c/196541/</strike> (Abandoned - Chapter was a verbatim copy from the internet - Needs a new owner)
 
* <strike>L3 HA - Clean up: https://review.openstack.org/#/c/196890/</strike> (Abandoned)
 
* <strike>IPv6: https://review.openstack.org/#/c/181049/</strike>  (Merged)
 
* <strike>OVS Update: https://review.openstack.org/#/c/196856/</strike> (Merged)
 
* <strike>Debugging Section: https://review.openstack.org/#/c/178000/</strike> (Merged but more work needed on this chapter)
 
  
==== Networking Guide ====
+
PATCHES THAT NEED REVIEWS
* Etherpad: https://etherpad.openstack.org/p/networking-guide
+
* Decouple DB workstream/blueprint: https://review.openstack.org/#/q/status:open+topic:bp/neutronlib-decouple-db+label:Workflow%253D0
* ToC: https://wiki.openstack.org/wiki/NetworkingGuide/TOC
+
* Callback payload workstream: https://review.openstack.org/#/q/status:open+topic:use-callback-payloads+label:Workflow%253D0
* Gerrit: https://github.com/openstack/openstack-manuals/tree/master/doc/networking-guide
 
  
 
=== On Demand Agenda ===
 
=== On Demand Agenda ===
* Mitaka Design Summit Sessions
+
 
** Collecting ideas on the following etherpad
+
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:
** https://etherpad.openstack.org/p/neutron-mitaka-designsummit
+
 
* Liberty-RC1
+
* Topic for the meeting (keep this template, please):
** https://launchpad.net/neutron/+milestone/liberty-rc1
+
** (nick): topic
* Concrete plan to merge back pecan work
 
** Need to do this very early after Liberty-2 is cut this week
 
* Liberty-3 walk-through
 
** https://launchpad.net/neutron/+milestone/liberty-3
 
* Vendor decomposition
 
** Which vendors have not started final decomposition?
 
*** Should we maintain a list of stragglers in devref until they are all done?
 
*** Send an email notice about decomposition to -dev: what should it say?
 
** Does anything need to be left in the tree for packaging?
 
*** Currently requirements.txt is left in the vendor dir with the name of the vendor package, but no one seems to know if it is needed.
 
* Stable branches for networking subproject
 
** networking sub-projects can perform a release
 
** Working with networking-midonet as a test example
 
** These projects will have a version of 1.0.0
 
* Liberty-3 BPs and reviews
 
** https://launchpad.net/neutron/+milestone/liberty-3
 
** Focus here for the remaining weeks
 
** Handy dandy gerrit dashboard link: https://goo.gl/x9bO7i
 
** We need to merge all of this for Liberty (or make our best shot)
 
** Email to openstack-dev ML on this topic: http://lists.openstack.org/pipermail/openstack-dev/2015-August/071786.html
 
* nova-network compatibility tasks
 
** Summit session(s) in Vancouver were very productive
 
** Tasks tracked here: https://etherpad.openstack.org/p/YVR-nova-network
 
** Need to find owners for a few of these
 
*** Rolling upgrades (mostly a grenade patch)
 
*** Distributed SNAT with DVR
 
*** "Get me a network (https://review.openstack.org/#/c/184857/) (kevinbenton to own this)
 
*** ARP Spoof patch series is stalled, need to make a decision on how to proceed. (kevinbenton will do this after beating requirements out of markmcclain)
 
* macvtap ml2 driver and agent - will land in neutron tree. Question is how to procede with agent code (scheuran)
 
** '''Aug 17 2015 update''' - sc68cal is working with scheuran in this gerrit topic https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bug/1468803,n,z
 
** 1) Copy (duplicate) required agent code like in the past.
 
** 2) Extract a common base class for macvtap, linuxbridge and sriov-nic (impls are close to each other). Purpose: Sharing base agent code. Starting with macvtap only in liberty. Moving others to common base class in Mitaka. New agent base class cannot be used for OVS, as it already diverged too much from others.
 
*** Liberty: only methods that are obious common and only differ in details that can be abstracted (_setup_rpc, _report_state, _device_info_has_changes, _process_network_devices)
 
*** Mitaka: Methods that have a lot of common code, but require fruther thinking (treat_devices_added_updated, scan_devices, daemon_loop)
 
*** N: Having a common agent with interface drivers?
 
** Modular l2 agent (spec not in a good shape) and agent extension (is just for extending existing agents) is is not an option
 
* Need decision on how to handle test jobs for Neutron client
 
** Email with details: http://lists.openstack.org/pipermail/openstack-dev/2015-August/072772.html
 
  
 
== 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/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]
 
** [http://eavesdrop.openstack.org/meetings/networking/2014/?C=M;O=D networking-2014]
 
** [http://eavesdrop.openstack.org/meetings/networking/2014/?C=M;O=D networking-2014]
Line 110: Line 151:
 
** [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 13:43, 17 May 2022

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

Bugs and Gate issues

This week slaweq is the deputy and next week bcafarel will be.

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
May-9-2022 Lajos Katona (lajoskatona)
May-16-2022 Bernard Cafarelli (bcafarel) Switched with slaweq
May-23-2022 Slawek Kaplonski (slaweq) Switched with bcafarel
May-30-2022 Brian Haley (haleyb)
June-6-2022 Akihiro Motoki (amotoki)
June-13-2022 Miguel Lavalle (mlavalle)
June-20-2022 Bence Romsics (rubasov)
June-27-2022 Rodolfo Alonso Hernandez (ralonsoh)
July-4-2022 Lucas Alvares Gomes (lucasgomes)
July-11-2022 Jakub Libosvar (jlibosva)
July-18-2022 Oleg Bondarev (obondarev)
July-25-2022 Mamatisa Nurmatov (isabek)
August-1-2022 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

L3 subteam

ryu os-ken

  • No new changes in ryu.

https://ethercalc.openstack.org/make_os-ken_and_ryu_sync

Outreachy ideas

Outreachy mail for 2022 spring semester: http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027239.html Summary from Dmitry Tantsur: https://owlet.today/posts/how-to-propose-the-best-project-for-outreachy/ Last meeting discussion: https://meetings.opendev.org/meetings/networking/2022/networking.2022-02-22-14.08.log.html#l-73

Neutron performance subteam

Blueprints

Blueprints which we should include in Yoga 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

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