Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Ryu support)
(On Demand Agenda)
(244 intermediate revisions by 11 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Next milestone is Stein-1, October 22 - 26
+
* Still looking for "new daddies" for
** https://releases.openstack.org/stein/schedule.html
+
** neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html
* Stein PTG summary: http://lists.openstack.org/pipermail/openstack-dev/2018-September/135032.html
+
*** I just sent LAST CALL reminder as we talked last week: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012099.html
 +
* We are getting close to Ussuri-2, it will be in the week of February 10: https://releases.openstack.org/ussuri/schedule.html
 +
* I forgot about it last week, next release will be Victoria: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011947.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 ===
  
stein-1 blueprints: https://launchpad.net/neutron/+milestone/stein-1
 
  
==== OVO/no downtime API ====
+
Blueprints which we should include in Ussuri milestones:
 
+
* Blueprints for Ussuri-2: https://launchpad.net/neutron/+milestone/ussuri-2
* OVO backlog control spreadsheet: https://docs.google.com/spreadsheets/d/1Mz7V40GSdcUH_aBoNWjsFaNRp4wf-duz1GFWligiNXc/edit#gid=1051788848
+
* https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/
* Weekly meeting on Thursday at 1400UTC: http://eavesdrop.openstack.org/#Neutron_Upgrades_Meeting
+
* https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes
 +
* 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 22: Line 33:
 
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)
* Run under Python 3 by default (njohnston)
+
** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
** https://governance.openstack.org/tc/goals/stein/python3-first.html
+
** https://storyboard.openstack.org/#!/story/2005477 (This seems to be used to track gmann's job changes)
* Support Pre Upgrade Checks (slaweq)
+
** Patches for stadium projects are needed:
** https://governance.openstack.org/tc/goals/stein/upgrade-checkers.html
+
*** 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)
 +
** 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
  
* Create a vlan transparent network in mixed driver environment: https://bugs.launchpad.net/neutron/+bug/1745192
+
=== Bugs and Gate issues ===
  
=== Bugs and Gate issues ===
+
haleyb was on bug deputy: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012094.html
  
Bug deputy report for week of September 17th: http://lists.openstack.org/pipermail/openstack-dev/2018-September/135008.html
+
I propose to add new official tag "ovn" to launchpad and our docs. What do You think?
  
 
More discussion on this topic takes place during the Neutron CI meeting: 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
Line 50: Line 64:
 
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
|-
 
| August-6-2018 || Bernard Cafarelli (bcafarel)
 
|-
 
| August-13-2018 || Pawel Suder (pasuder)
 
|-
 
| August-20-2018 || Hongbin Lu (hongbin)
 
 
|-
 
|-
| Augustl-27-2018 || Hirofumi Ichihara (hichihara)
+
| December-23-2019 || Bernard Cafarelli (bcafarel) || switched with Miguel Lavalle (mlavalle)
 
|-
 
|-
| September-10-2018 || Akihiro Motoki (amotoki)
+
| December-30-2019 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| September-17-2018 || Boden Russel (boden)
+
| January-6-2020 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| September-24-2018 || Nate Johnston (njohnston)  
+
| Januaryu-13-2020 || Brian Haley (haleyb) ||
 
|-
 
|-
| October-1-2018 || Swaminathan Vasudevan (Swami)
+
| January-20-2020 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| October-8-2018 || Slawek Kaplonski (slaweq)
+
| January-27-2020 || Ryan Tidwell (tidwellr) ||
 
|-
 
|-
| October-15-2018 || Brian Haley (haleyb)
+
| February-3-2020 || Swaminathan Vasudevan (Swami) ||
 
|-
 
|-
| October-22-2018 || Armando Migliaccio (armax)
+
| February-10-2020 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| October-29-2018 || Zhao Bo(bzhao)
+
| February-17-2020 || Nate Johnston (njohnston) ||
 
|-
 
|-
| November-5-2018 || Manjeet  Bhatia (manjeets)
+
| Fabruary-24-2020 || Miguel Lavalle (mlavalle) || switched with Bernard Cafarelli (bcafarel)
 
|-
 
|-
| November-12-2018 || Lujin Luo(lujinluo)
+
| March-2-2020 || YAMAMOTO Takashi (yamamoto) ||
 
|-
 
|-
| November-19-2018 || YAMAMOTO Takashi (yamamoto)
+
| March-9-2020 || Bence Romsics (rubasov) ||
|-
 
| November-26-2018 || Miguel Lavalle (mlavalle)
 
 
|}
 
|}
  
 
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
  
=== os-ken ===
+
=== Neutron performance subteam (Monday meetings) ===
  
# How to manage the divergence between ryu and os-ken
+
=== Networking OVN and ML2+OVS+DVR Convergence (Tuesday meetings) ===
# Set up CI on gerrit
+
 
# Go through the Neutron code and change the imports. Much like we do when we re-home code to neutron-lib
+
Merge OVN into Neutron tree:
# Have a point person who knows about Ryu and can orient other team members when changes might be needed
+
* Blueprint: https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge
# Packaging, documentation, etc.
+
* 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 115: Line 123:
 
=== 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
  
'''DO NOT TOP POST - ADD PATCHES TO THE BOTTOM OF THE LIST'''
+
HOUSE KEEPING
 +
* Neutron-lib work items and volunteers are being tracked via etherpad: https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-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
+
PATCHES THAT NEED REVIEWS
** 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.
+
* Decouple DB workstream/blueprint: https://review.openstack.org/#/q/status:open+topic:bp/neutronlib-decouple-db+label:Workflow%253D0
** 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).
+
* Callback payload workstream: https://review.openstack.org/#/q/status:open+topic:use-callback-payloads+label:Workflow%253D0
* Patches that need high-level input from neutron cores: https://review.openstack.org/#/q/message:%22NeutronCoreInputNeeded%22
+
* Updating projects for Zuul v3: https://review.openstack.org/#/q/status:open+topic:neutronlib-zuulv3
* 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>
 
  
 
=== On Demand Agenda ===
 
=== On Demand Agenda ===
Line 133: Line 139:
 
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:
  
 +
* standardize on zuul v3 syntax:
 +
** Do we need to change job definitions on stable branches as well?
 +
*** The question come up for bagpipe job conversions. The old legacy job definitions are here: https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/zuul-legacy-jobs.yaml#L367-L377.
 +
If we do the conversion for master only, the legacy job definitions will remain in openstack-zuul-jobs repo, but if we remove them we have to backport the new job template to stable branches ase well.
 
* Topic for the meeting (keep this template, please):
 
* Topic for the meeting (keep this template, please):
 
+
** (your nickname): brief description.
* SNAT log - Get advice about moving libnetfilter_log to neutron_lib:
+
*** More details
** Due to neutron-lib doesn't allow eventlet. How do we deal with this issue?  Because libnetfilter_log use eventlet.green.zmp for communicating between libnetfilter_log process (privilege process) and log-application( un-privilege process).
 
  
 
== 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/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]

Revision as of 13:44, 24 January 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

haleyb was on bug deputy: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012094.html

I propose to add new official tag "ovn" to launchpad and our docs. What do You think?

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

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:

If we do the conversion for master only, the legacy job definitions will remain in openstack-zuul-jobs repo, but if we remove them we have to backport the new job template to stable branches ase well.

  • Topic for the meeting (keep this template, please):
    • (your nickname): brief description.
      • More details

Previous meeting logs