Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Blueprints)
(Announcements / Reminders)
(297 intermediate revisions by 18 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Next milestone, Rocky-1, April 16 - 20
+
* Shanghai PTG
* Rocky release schedule: https://releases.openstack.org/rocky/schedule.html
+
** planning etherpad https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
* Rocky PTG topics and agenda: https://etherpad.openstack.org/p/neutron-ptg-rocky
+
** schedule: https://usercontent.irccloud-cdn.com/file/z9iLyv8e/pvg-ptg-sched-2
* Those who attended the Queens and / or the Rocky PTG got an email with discount code to register for the Vancouver Summit
+
** forum session: https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24412/neutron-stadium-projects-the-path-forward
 +
** Who is interested to go for team dinner in shanghai? Please put info in etherpad https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
 +
* Train release
 +
** https://releases.openstack.org/train/schedule.html
 +
** next week is Train release,
 +
* Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html
  
 
=== Blueprints ===
 
=== Blueprints ===
  
mlavalle will update Launchpad this week with dashboard to track blueprint implementation during Rocky
+
Train blueprints: https://launchpad.net/neutron/+milestone/train-rc1
 +
All targeted to Train RC1 is merged now
  
==== OVO/no API downtime ====
+
Blueprints which we should include in Ussuri milestones:
 
+
* https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/
List here patches/topics that need core reviewer attention.
+
* https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes
 
+
* https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - spec is here: https://review.opendev.org/#/c/657170
* add your patch here
+
* 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/
  
 
=== Community Goals ===
 
=== Community Goals ===
Line 24: Line 30:
 
https://governance.openstack.org/tc/goals/index.html#release-cycles
 
https://governance.openstack.org/tc/goals/index.html#release-cycles
  
* policy-in-code (Queens)
+
* Run under Python 3 by default (njohnston)
* wsgi support (Pike)
+
** https://governance.openstack.org/tc/goals/stein/python3-first.html
* Enable mutable configuration (Rocky)
+
** https://storyboard.openstack.org/#!/story/2003242
* mox3 removal (Rocky) https://bugs.launchpad.net/python-neutronclient/+bug/1753504
+
** Etherpad https://etherpad.openstack.org/p/neutron_stadium_python3_status
 
+
*** According to etherpad only networking-midonet is not transitioned still,
* Split Tempest Plugins into Separate Repos/Projects (Queens) : Completed (we can drop it from the next meeting)
 
** https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html#neutron
 
 
 
=== Starter Approved RFEs ===
 
  
This section is for advertising approved RFEs that the Neutron Drivers team have deemed suitable for new contributors:
+
* Support IPv6-Only Deployments (slaweq)
 
+
** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
* Network router:external field not exported: https://bugs.launchpad.net/neutron/+bug/1653932
+
** 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-.*)
 +
*** 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,
  
 
=== Bugs and Gate issues ===
 
=== Bugs and Gate issues ===
  
Bug deputy report for week of February 12th: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127560.html
+
Bugs report for week of October 7th: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010107.html
  
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 59: Line 63:
 
{| class="wikitable" style="text-align: center;"
 
{| class="wikitable" style="text-align: center;"
 
|-
 
|-
! Date !! who  
+
! Date !! who !! note
 
|-
 
|-
| January-8-2018 || Hirofumi Ichihara (hichihara)
+
| September-30-2019 || Bernard Cafarelli (bcafarel) ||
 
|-
 
|-
| January-15-2018 || Gary Kotton (garyk)
+
| October-7-2019 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| January-22-2018 || Akihiro Motoki (amotoki)
+
| October-14-2019 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| January-29-2018 || Jakub Libosvar (jlibosva)
+
| October-21-2019 || Boden Russel (boden) ||
 
|-
 
|-
| February-5-2018 || Boden Russel (boden)
+
| October-28-2019 || Brian Haley (haleyb) ||
 
|-
 
|-
| February-12-2018 || James Anziano (janzian)
+
| November-4-2019 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| February-19-2018 || Ihar Hrachyshka (ihrachys)
+
| November-11-2019 || Ryan Tidwell (tidwellr) ||
 
|-
 
|-
| February-26-2018 || Slawek Kaplonski (slaweq)
+
| November-19-2019 || Swaminathan Vasudevan (Swami) ||
 
|-
 
|-
| March-5-2018 || Brian Haley (haleyb)
+
| November-25-2019 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| March-12-2018 || Zhao Bo(bzhao)
+
| December-2-2019 || Nate Johnston (njohnston) ||
 
|-
 
|-
| March-19-2018 || Armando Migliaccio (armax)
+
| December-9-2019 || Miguel Lavalle (mlavalle) ||
 
|-
 
|-
| March-26-2018 || Swaminathan Vasudevan (Swami)
+
| December-16-2019 || YAMAMOTO Takashi (yamamoto) ||
 
|-
 
|-
| April-2-2018 || Lujin Luo(lujinluo)
+
| December-23-2019 || Bence Romsics (rubasov) ||
|-
 
| April-9-2018 || YAMAMOTO Takashi (yamamoto)
 
|-
 
| April-16-2018 || Miguel Lavalle (mlavalle)
 
 
|}
 
|}
  
Line 100: Line 100:
  
 
=== CLI/SDK ===
 
=== 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 106: Line 110:
 
=== 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.
+
HOUSE KEEPING
 
+
* Neutron-lib work items and volunteers are being tracked via etherpad: https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list
'''DO NOT TOP POST - ADD PATCHES TO THE BOTTOM OF THE LIST'''
+
* For a list of "current" consumers who receive neutron-lib updates and consumption patches, see: http://codesearch.openstack.org/?q=neutron-lib-current
 
+
* For a complete list of neutron-lib consumption patches that may impact consumers see: https://review.openstack.org/#/q/message:%22NeutronLibImpact%22
* Open issues: https://review.openstack.org/#/q/status:open+message:%22NeutronLibImpact%22
 
** 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>
+
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 127: Line 127:
 
** (your nickname): brief description.
 
** (your nickname): brief description.
 
*** More details
 
*** More details
* Typo fixing patches
+
** (slaweq) My availability next week
** (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.
 
  
 
== 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 11:01, 14 October 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

Train blueprints: https://launchpad.net/neutron/+milestone/train-rc1 All targeted to Train RC1 is merged now

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

Bugs report for week of October 7th: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010107.html

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 Boden Russel (boden)
October-28-2019 Brian Haley (haleyb)
November-4-2019 Lajos Katona (lajoskatona)
November-11-2019 Ryan Tidwell (tidwellr)
November-19-2019 Swaminathan Vasudevan (Swami)
November-25-2019 Akihiro Motoki (amotoki)
December-2-2019 Nate Johnston (njohnston)
December-9-2019 Miguel Lavalle (mlavalle)
December-16-2019 YAMAMOTO Takashi (yamamoto)
December-23-2019 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

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

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
    • (slaweq) My availability next week

Previous meeting logs