Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Announcements / Reminders)
(Bugs and Gate issues)
(418 intermediate revisions by 23 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* If you are attending the Summit in Sydney, please register your name in https://etherpad.openstack.org/p/neutron-sydney-summit-attendees. Team social event to be scheduled
+
* We reached Ussuri-2 milestone: https://releases.openstack.org/ussuri/schedule.html last week,
* Neutron team will be present in the Upstream Institute session in Sydney on Sunday 5th
+
** next important dates are:
* Neutron will have a new contributors on-boarding session during Summit. Day and time yet to be defined
+
*** Final release for non-client libraries - week of March 30th,
* PTG Summary Email - http://lists.openstack.org/pipermail/openstack-dev/2017-September/122583.html
+
*** Ussuri-3 (feature freeze) - week of April 6th
 +
** Related to that are new releases of Stein and Train:
 +
*** https://review.opendev.org/#/c/707822/
 +
*** https://review.opendev.org/#/c/707840/
 +
* neutron-fwaas didn't found new maintainers so this week I will start marking it as deprecated,
 +
* We are also getting close to Rocky EM. It's next week: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012207.html
 +
** Open neutron reviews for Rocky: https://review.opendev.org/#/q/branch:%255Estable/rocky+status:open+(project:%255Eopenstack/neutron)
 +
** Open stadium projects reviews for Rocky: https://review.opendev.org/#/q/branch:^stable/rocky+status:open+(project:^openstack/neutron)
 +
* Victoria PTG planning etherpad: https://etherpad.openstack.org/p/neutron-victoria-ptg
 +
* Shanghai PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010702.html and also on http://kaplonski.pl/blog/shanghai_ptg_summary/ (with photos from team dinner)
  
 
=== Blueprints ===
 
=== Blueprints ===
  
Current milestone: https://launchpad.net/neutron/+milestone/queens-1
 
  
Current cycle: https://blueprints.launchpad.net/neutron/queens
+
Blueprints which we should include in Ussuri milestones:
 +
* Blueprints for Ussuri-3: https://launchpad.net/neutron/+milestone/ussuri-3
 +
** https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge - Convergence of ML2+OVS+DVR and OVN
 +
** https://blueprints.launchpad.net/neutron/+spec/tagging-on-post - almost done, only SDK/OSC part is todo
 +
** https://bugs.launchpad.net/neutron/+bug/1841067 - [RFE] SR-IOV agent depends on mac addresses for getting bound ports
 +
** https://blueprints.launchpad.net/neutron/+spec/fip-pf-description - almost done, only SDK and OSC part left todo
 +
** https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes
 +
** https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/
 +
** https://blueprints.launchpad.net/neutron/+spec/metadata-over-ipv6
 +
* Removed target milestone:
 +
** https://blueprints.launchpad.net/neutron/+spec/evacuate-agent-resources
 +
** https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - spec is here: https://review.opendev.org/#/c/657170
 +
** https://blueprints.launchpad.net/neutron/+spec/default-dns-zone-per-tenant
 +
** https://blueprints.launchpad.net/neutron/+spec/neutron-classifier-neutron-qos
  
==== OVO/no API downtime ====
+
=== Community Goals ===
  
List here patches/topics that need core reviewer attention.
+
This slot is to used to track the progress of the community goals.
 +
https://governance.openstack.org/tc/goals/index.html#release-cycles
  
* add your patch here
+
* Support IPv6-Only Deployments (slaweq)
 +
** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
 +
** https://storyboard.openstack.org/#!/story/2005477 (This seems to be used to track gmann's job changes)
 +
** Patches for stadium projects are needed:
 +
*** https://review.opendev.org/#/q/topic:ipv6-only-deployment-and-testing+(status:open+OR+status:merged)+(project:%255Eopenstack/neutron.*+OR+project:%255Eopenstack/networking-.*)
  
=== Starter Approved RFEs ===
+
* Drop Python 2.7 Support (njohnston) - DONE
 +
** https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
 +
** Etherpad: https://etherpad.openstack.org/p/neutron-train-zuulv3-py27drop
  
This section is for advertising approved RFEs that the Neutron Drivers team have deemed suitable for new contributors:
+
* Project Specific PTL and Contributor Documentation
 
+
** https://governance.openstack.org/tc/goals/proposed/project-ptl-and-contrib-docs.html
* Network router:external field not exported: https://bugs.launchpad.net/neutron/+bug/1653932
+
** patch proposed: https://review.opendev.org/#/c/707486/
* Add attribute to the a port that lists the UUIDs of other ports that the port is allowed to impersonate: https://bugs.launchpad.net/neutron/+bug/1689830
 
* Make get-me-a-network work with any network topology: https://bugs.launchpad.net/neutron/+bug/1690438
 
  
 
=== Bugs and Gate issues ===
 
=== Bugs and Gate issues ===
  
A full hour is dedicated to this topic, and more during the following meeting:
+
Tidwellr was on bug deputy. I don't see summary yet.
  
* https://wiki.openstack.org/wiki/Meetings/NeutronCI
+
More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI
 
 
 
 
Approximate stats for the current cycle:
 
 
 
* From the beginning of Ocata (Sept-16-2016):
 
** Total reports: '''415'''
 
*** Fix released: '''135'''
 
*** Unassigned: '''135'''
 
**** New: '''27'''
 
**** Incomplete: '''15'''
 
**** Confirmed: '''24'''
 
**** 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 57: Line 71:
 
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
 
|-
 
|-
| October-2-2017 || Miguel Lavalle (mlavalle)
+
| December-23-2019 || Bernard Cafarelli (bcafarel) || switched with Miguel Lavalle (mlavalle)
 
|-
 
|-
| October-9-2017 || Jakub Libosvar (jlibosva)
+
| December-30-2019 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| October-16-2017 || Boden Russel (boden)
+
| January-6-2020 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| October-23-2017 || James Anziano (janzian)
+
| Januaryu-13-2020 || Brian Haley (haleyb) ||
 
|-
 
|-
| October-30-2017 || Ihar Hrachyshka (ihrachys)
+
| January-20-2020 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| November-6-2017 || Slawek Kaplonski (slaweq)
+
| January-27-2020 || Ryan Tidwell (tidwellr) ||
 
|-
 
|-
| November-13-2017 || Brian Haley (haleyb)
+
| February-3-2020 || Nate Johnston (njohnston) ||
 
|-
 
|-
| November-20-2017 || Zhao Bo(bzhao)
+
| February-10-2020 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| November-27-2017 || Armando Migliaccio (armax)
+
| Fabruary-24-2020 || Miguel Lavalle (mlavalle) || switched with Bernard Cafarelli (bcafarel)
 
|-
 
|-
| December-4-2017 || Swaminathan Vasudevan (Swami)
+
| March-2-2020 || YAMAMOTO Takashi (yamamoto) ||
 
|-
 
|-
| December-11-2017 || David Shaughnessy (davidsha)
+
| March-9-2020 || Bence Romsics (rubasov) ||
|-
 
| December-18-2017 || Rodolfo Alonso (ralonsoh)
 
|-
 
| December-25-2017 || Lujin Luo(lujinluo)
 
|-
 
| January-1-2018 || YAMAMOTO Takashi (yamamoto)
 
|-
 
| January-8-2018 || Akihiro Motoki (amotoki)
 
|-
 
| January-15-2018 || Hirofumi Ichihara (hichihara)
 
|-
 
| January-22-2018 || Gary Kotton (garyk)
 
 
|}
 
|}
  
 
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
 +
 +
=== Neutron performance subteam (Monday meetings) ===
 +
 +
=== Networking OVN and ML2+OVS+DVR Convergence (Tuesday meetings) ===
 +
 +
Merge OVN into Neutron tree:
 +
* Blueprint: https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge
 +
* Proposed rehome plan: https://ethercalc.openstack.org/networking-ovn-migration
 +
* Planning Etherpad https://etherpad.openstack.org/p/neutron-networking-ovn-merge
 +
* Spec: https://review.opendev.org/#/c/658414/
  
 
=== Docs ===
 
=== Docs ===
Line 105: Line 117:
 
* Documentation bugs - https://bugs.launchpad.net/neutron/+bugs?field.tag=doc
 
* Documentation bugs - https://bugs.launchpad.net/neutron/+bugs?field.tag=doc
  
=== Transition to OSC ===
+
=== CLI/SDK ===
Status of changes to deliver OSC
+
 
 +
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
 
* https://etherpad.openstack.org/p/osc-transition-priorities
 
* http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html
 
* http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html
Line 112: Line 128:
 
=== 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.
+
We just released neutron-lib 2.0.0 - with dropped support for python 2.7 and fix for bug introduced accidentally in 1.31.0
 
 
FRIENDLY REMINDER: Neutron/driver cores please try to make a pass through the [https://etherpad.openstack.org/p/neutron-lib-core-review-queue curated neutron rehoming patches].
 
 
 
'''DO NOT TOP POST - ADD PATCHES TO THE BOTTOM OF THE LIST'''
 
  
* UpgradeImpact changes: https://review.openstack.org/#/q/status:open+message:%22UpgradeImpact%22+project:openstack/neutron
+
HOUSE KEEPING
* Periodic neutron-lib check: http://grafana.openstack.org/dashboard/db/neutron-lib-failure-rate?panelId=4&fullscreen
+
* Neutron-lib work items and volunteers are being tracked via etherpad: https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list
* Open issues: https://review.openstack.org/#/q/status:open+message:%22NeutronLibImpact%22
+
* For a list of "current" consumers who receive neutron-lib updates and consumption patches, see: http://codesearch.openstack.org/?q=neutron-lib-current
* Past issues: https://review.openstack.org/#/q/status:merged+message:%22NeutronLibImpact%22
+
* For a complete list of neutron-lib consumption patches that may impact consumers see: https://review.openstack.org/#/q/message:%22NeutronLibImpact%22
  
* <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
 +
* Updating projects for Zuul v3: https://review.openstack.org/#/q/status:open+topic:neutronlib-zuulv3
  
 
=== On Demand Agenda ===
 
=== On Demand Agenda ===
Line 130: Line 145:
  
 
* Topic for the meeting (keep this template, please):
 
* Topic for the meeting (keep this template, please):
** (your nickname): brief description.
+
** (ralonsoh): https://bugs.launchpad.net/neutron/+bug/1476527. Question: merge API, DB and server changes without backend ones? Or not?
 
*** More details
 
*** More details
 +
** (imalinovskiy): RBAC support for address scope and subnet pool. Core developer's opinion on this, suggestions for the implementation.
 +
*** https://bugs.launchpad.net/neutron/+bug/1862968 and https://bugs.launchpad.net/neutron/+bug/1862032
  
 
== 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/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]
Line 142: Line 162:
 
** [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.
 

Revision as of 13:34, 17 February 2020

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

Tidwellr was on bug deputy. I don't see summary yet.

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
December-23-2019 Bernard Cafarelli (bcafarel) switched with Miguel Lavalle (mlavalle)
December-30-2019 Slawek Kaplonski (slaweq)
January-6-2020 Hongbin Lu (hongbin)
Januaryu-13-2020 Brian Haley (haleyb)
January-20-2020 Lajos Katona (lajoskatona)
January-27-2020 Ryan Tidwell (tidwellr)
February-3-2020 Nate Johnston (njohnston)
February-10-2020 Akihiro Motoki (amotoki)
Fabruary-24-2020 Miguel Lavalle (mlavalle) switched with Bernard Cafarelli (bcafarel)
March-2-2020 YAMAMOTO Takashi (yamamoto)
March-9-2020 Bence Romsics (rubasov)

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

Neutron performance subteam (Monday meetings)

Networking OVN and ML2+OVS+DVR Convergence (Tuesday meetings)

Merge OVN into Neutron tree:

Docs

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)

Neutron-lib, planned refactoring and other impacts

We just released neutron-lib 2.0.0 - with dropped support for python 2.7 and fix for bug introduced accidentally in 1.31.0

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:

Previous meeting logs