Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Bugs and Gate issues)
(Bug deputy)
(314 intermediate revisions by 15 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Next milestone, Rocky-1, April 16 - 20
+
* Still looking for "new daddies" for
** Rocky release schedule: https://releases.openstack.org/rocky/schedule.html
+
** neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html
* Deadline to suggest topics for the forum in April 15th: http://forumtopics.openstack.org/
+
** neutron-vpnaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010931.html
** Brainstorming etherpad: https://etherpad.openstack.org/p/YVR-neutron-brainstorming
+
* Removing of neutron-interconnection from stadium project is done
* Rocky PTG summary: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128183.html
+
* It's Ussuri-1 milestone week: https://releases.openstack.org/ussuri/schedule.html
 +
* We now have review priority also in stadium projects' patches: https://review.opendev.org/#/c/696628/
 +
* Voting for "V" release name is now open: http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011477.html
 +
* 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 ===
  
Rocky-1 blueprints: https://launchpad.net/neutron/+milestone/rocky-1
 
  
==== OVO/no API downtime ====
+
Blueprints which we should include in Ussuri milestones:
 
+
* Blueprints for Ussuri-1: https://launchpad.net/neutron/+milestone/ussuri-1
List here patches/topics that need core reviewer attention.
+
* 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/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes
* add your patch here
+
* https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge - Convergence of ML2+OVS+DVR and OVN
 +
* 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/neutron-classifier-neutron-qos - there is series of patches in https://review.opendev.org/#/q/topic:qos-classifier+(status:open+OR+status:merged) - spec still not done https://review.opendev.org/#/c/678865/
 +
* https://blueprints.launchpad.net/neutron/+spec/metadata-over-ipv6
 +
* https://blueprints.launchpad.net/neutron/+spec/tagging-on-post
 +
* https://blueprints.launchpad.net/neutron/+spec/evacuate-agent-resources
 +
* 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
 +
* https://blueprints.launchpad.net/neutron/+spec/default-dns-zone-per-tenant
  
 
=== Community Goals ===
 
=== Community Goals ===
Line 25: Line 35:
 
https://governance.openstack.org/tc/goals/index.html#release-cycles
 
https://governance.openstack.org/tc/goals/index.html#release-cycles
  
* policy-in-code (Queens) -- amotoki
+
* Support IPv6-Only Deployments (slaweq)
* wsgi support (Pike) -- annp
+
** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
* Enable mutable configuration (Rocky) https://governance.openstack.org/tc/goals/rocky/enable-mutable-configuration.html -- slaweq
+
** https://storyboard.openstack.org/#!/story/2005477 (This seems to be used to track gmann's job changes)
* mox3 removal (Rocky) https://bugs.launchpad.net/python-neutronclient/+bug/1753504 -- hongbin (neutronclient), amotoki (fwaas/vpnaas-dashboard), (perhaps) yamamoto (networking-midonet)
+
** Patches for stadium projects are needed:
* python3.5 fully support https://etherpad.openstack.org/p/py3-neutron-pike
+
*** https://review.opendev.org/#/q/topic:ipv6-only-deployment-and-testing+(status:open+OR+status:merged)+(project:%255Eopenstack/neutron.*+OR+project:%255Eopenstack/networking-.*)
 +
*** I need to check and update https://review.opendev.org/#/c/686043/ - as we talked with gmann to propose one neutron-tempest-plugin ipv6 job which will run all tempest plugin tests using ipv6 only,
  
=== Starter Approved RFEs ===
+
* Drop Python 2.7 Support (njohnston)
 +
** 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
 
+
** Proposal not merged yet: https://review.opendev.org/#/c/691737/
* Network router:external field not exported: https://bugs.launchpad.net/neutron/+bug/1653932
 
  
 
=== Bugs and Gate issues ===
 
=== Bugs and Gate issues ===
  
Bug deputy report for week of March 26th: https://docs.google.com/spreadsheets/d/1xP0QWZZuKyCf1vKMbCFN9haFqfVXlqyjBVfUc3COb3M/edit#gid=0
+
amotoki was bug deputy last week. I don't see any report from him yet.
  
A full hour is dedicated to this topic, and more during the following meeting:
+
More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI
  
* 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 58: Line 69:
 
{| class="wikitable" style="text-align: center;"
 
{| class="wikitable" style="text-align: center;"
 
|-
 
|-
! Date !! who  
+
! Date !! who !! note
 +
|-
 +
| September-30-2019 || Bernard Cafarelli (bcafarel) ||
 +
|-
 +
| October-7-2019 || Slawek Kaplonski (slaweq) ||
 +
|-
 +
| October-14-2019 || Hongbin Lu (hongbin) ||
 +
|-
 +
| October-21-2019 || Brian Haley (haleyb)  ||
 +
|-
 +
| October-28-2019 || Lajos Katona (lajoskatona) ||
 +
|-
 +
| November-4-2019 || Ryan Tidwell (tidwellr)  ||
 
|-
 
|-
| January-8-2018 || Hirofumi Ichihara (hichihara)
+
| November-11-2019 || Swaminathan Vasudevan (Swami) ||
 
|-
 
|-
| January-15-2018 || Gary Kotton (garyk)
+
| November-18-2019 || Akihiro Motoki (amotoki)  || switched with Miguel Lavalle (mlavalle)
 
|-
 
|-
| January-22-2018 || Akihiro Motoki (amotoki)
+
| November-25-2019 || Nate Johnston (njohnston) ||
 
|-
 
|-
| January-29-2018 || Jakub Libosvar (jlibosva)
+
| December-2-2019 || Miguel Lavalle (mlavalle) || switched with Akihiro Motoki (amotoki)
 
|-
 
|-
| February-5-2018 || Boden Russel (boden)
+
| December-9-2019 || YAMAMOTO Takashi (yamamoto) ||
 
|-
 
|-
| February-12-2018 || James Anziano (janzian)
+
| December-16-2019 || Bence Romsics (rubasov) ||
 +
|}
 +
 
 +
Next bug deputy round
 +
{| class="wikitable" style="text-align: center;"
 
|-
 
|-
| February-19-2018 || Ihar Hrachyshka (ihrachys)
+
! Date !! who !! note
 
|-
 
|-
| February-26-2018 || Slawek Kaplonski (slaweq)
+
| December-23-2019 || Bernard Cafarelli (bcafarel) || switched with Miguel Lavalle (mlavalle)
 
|-
 
|-
| March-5-2018 || Brian Haley (haleyb)
+
| December-30-2019 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| March-12-2018 || Zhao Bo(bzhao)
+
| January-6-2020 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| March-19-2018 || Armando Migliaccio (armax)
+
| Januaryu-13-2020 || Brian Haley (haleyb) ||
 
|-
 
|-
| March-26-2018 || Swaminathan Vasudevan (Swami)
+
| January-20-2020 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| April-2-2018 || Lujin Luo(lujinluo)
+
| January-27-2020 || Ryan Tidwell (tidwellr) ||
 
|-
 
|-
| April-9-2018 || YAMAMOTO Takashi (yamamoto)
+
| February-3-2020 || Swaminathan Vasudevan (Swami) ||
 
|-
 
|-
| April-16-2018 || Miguel Lavalle (mlavalle)
+
| February-10-2020 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| April-23-2018 || Pawel Suder (pasuder)
+
| February-17-2020 || Nate Johnston (njohnston) ||
 
|-
 
|-
| April-30-2018 || Hongbin Lu (hongbin)
+
| 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
 
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 113: Line 154:
 
=== 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.
+
I proposed release of new neutron-lib version without:
 +
* https://review.opendev.org/#/c/695205/
 +
 
 +
Those are included:
 +
* https://review.opendev.org/#/c/692580/ - merged
 +
* https://review.opendev.org/#/c/696308/ - merged
 +
* https://review.opendev.org/#/c/696070/ - merged
  
'''DO NOT TOP POST - ADD PATCHES TO THE BOTTOM OF THE LIST'''
+
Release patch https://review.opendev.org/#/c/697956/
  
* Open issues: https://review.openstack.org/#/q/status:open+message:%22NeutronLibImpact%22
+
HOUSE KEEPING
** 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.
+
* Neutron-lib work items and volunteers are being tracked via etherpad: https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list
** 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).
+
* For a list of "current" consumers who receive neutron-lib updates and consumption patches, see: http://codesearch.openstack.org/?q=neutron-lib-current
* Patches that need high-level input from neutron cores: https://review.openstack.org/#/q/message:%22NeutronCoreInputNeeded%22
+
* For a complete list of neutron-lib consumption patches that may impact consumers see: https://review.openstack.org/#/q/message:%22NeutronLibImpact%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>
+
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 134: Line 181:
 
** (your nickname): brief description.
 
** (your nickname): brief description.
 
*** More details
 
*** More details
* (toshii) (Maintenance) plans for the ryu library. [https://etherpad.openstack.org/p/neutron-ryu-future-plans (etherpad memo)]
 
  
 
== 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/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]

Revision as of 21:58, 9 December 2019

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

amotoki was bug deputy last week. I don't see any report from him 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 current scheduled rotation is the following:

Date who note
September-30-2019 Bernard Cafarelli (bcafarel)
October-7-2019 Slawek Kaplonski (slaweq)
October-14-2019 Hongbin Lu (hongbin)
October-21-2019 Brian Haley (haleyb)
October-28-2019 Lajos Katona (lajoskatona)
November-4-2019 Ryan Tidwell (tidwellr)
November-11-2019 Swaminathan Vasudevan (Swami)
November-18-2019 Akihiro Motoki (amotoki) switched with Miguel Lavalle (mlavalle)
November-25-2019 Nate Johnston (njohnston)
December-2-2019 Miguel Lavalle (mlavalle) switched with Akihiro Motoki (amotoki)
December-9-2019 YAMAMOTO Takashi (yamamoto)
December-16-2019 Bence Romsics (rubasov)

Next bug deputy round

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 Swaminathan Vasudevan (Swami)
February-10-2020 Akihiro Motoki (amotoki)
February-17-2020 Nate Johnston (njohnston)
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

I proposed release of new neutron-lib version without:

Those are included:

Release patch https://review.opendev.org/#/c/697956/

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):
    • (your nickname): brief description.
      • More details

Previous meeting logs