Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Community Goals)
(Neutron-lib, planned refactoring and other impacts)
 
(243 intermediate revisions by 12 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Next milestone is RC-1. Planning to cut RC-1 at the end of the week!
+
* 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
* PTL elections close on Aug 07, 2018 23:45 UTC
+
** neutron-vpnaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010931.html
** Current nominations: https://governance.openstack.org/election/#how-to-submit-your-candidacy
+
* Removing of neutron-interconnection from stadium project is almost done: https://review.opendev.org/#/q/branch:master+topic:neutron-interconnection-retire,
* PTG in Denver on September 10 -14:
+
** We are waiting for last patch https://review.opendev.org/#/c/694480/ to be merged,
** https://www.openstack.org/ptg/
+
* We started process of moving networking-ovn code into neutron tree
** http://lists.openstack.org/pipermail/openstack-dev/2018-August/132922.html
+
** BP: https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge
* Rocky PTG summary: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128183.html
+
** Patches: https://review.opendev.org/#/q/topic:bp/neutron-ovn-merge
 +
* Next week is Ussuri-1 milestone: https://releases.openstack.org/ussuri/schedule.html
 +
* I proposed patch to add review priority also to stadium projects: https://review.opendev.org/#/c/696628/
 +
* 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-rc1 blueprints: https://launchpad.net/neutron/+milestone/rocky-rc1
 
  
==== OVO/no downtime API ====
+
Blueprints which we should include in Ussuri milestones:
 
+
* Blueprints for Ussuri-1: https://launchpad.net/neutron/+milestone/ussuri-1
* 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 27: Line 38:
 
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)
* <s>wsgi support (Pike) -- annp
+
** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
* <s>Enable mutable configuration (Rocky) https://governance.openstack.org/tc/goals/rocky/enable-mutable-configuration.html</s> -- slaweq
+
** https://storyboard.openstack.org/#!/story/2005477 (This seems to be used to track gmann's job changes)
* <s>mox3 removal (Rocky) https://bugs.launchpad.net/python-neutronclient/+bug/1753504</s> -- 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-.*)
** Thread on overall community plan to move to a Python 3 only world: http://lists.openstack.org/pipermail/openstack-dev/2018-April/129866.html
+
*** 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 ===
 
  
This section is for advertising approved RFEs that the Neutron Drivers team have deemed suitable for new contributors:
+
* Drop Python 2.7 Support (njohnston)
 +
** https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
  
* Create a vlan transparent network in mixed driver environment: https://bugs.launchpad.net/neutron/+bug/1745192
+
* Project Specific PTL and Contributor Documentation
 +
** Proposal not merged yet: https://review.opendev.org/#/c/691737/
  
 
=== Bugs and Gate issues ===
 
=== Bugs and Gate issues ===
  
Bug deputy report for week of July 30th - August 6th: http://lists.openstack.org/pipermail/openstack-dev/2018-August/132932.html
+
njohnston 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
 
More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI
Line 60: Line 71:
 
{| 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) ||
 
|-
 
|-
| August-6-2018 || Bernard Cafarelli (bcafarel)
+
| October-21-2019 || Brian Haley (haleyb) ||
 
|-
 
|-
| August-13-2018 || Pawel Suder (pasuder)
+
| October-28-2019 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| August-20-2018 || Hongbin Lu (hongbin)
+
| November-4-2019 || Ryan Tidwell (tidwellr) ||
 
|-
 
|-
| Augustl-27-2018 || Hirofumi Ichihara (hichihara)
+
| November-11-2019 || Swaminathan Vasudevan (Swami) ||
 
|-
 
|-
| September-3-2018 || Gary Kotton (garyk)
+
| November-18-2019 || Akihiro Motoki (amotoki)  || switched with Miguel Lavalle (mlavalle)
 
|-
 
|-
| September-10-2018 || Akihiro Motoki (amotoki)
+
| November-25-2019 || Nate Johnston (njohnston) ||
 
|-
 
|-
| September-17-2018 || Boden Russel (boden)
+
| December-2-2019 || Miguel Lavalle (mlavalle) || switched with Akihiro Motoki (amotoki)
 
|-
 
|-
| September-24-2018 || Nate Johnston (njohnston)  
+
| December-9-2019 || YAMAMOTO Takashi (yamamoto) ||
 
|-
 
|-
| October-1-2018 || Swaminathan Vasudevan (Swami)
+
| December-16-2019 || Bence Romsics (rubasov) ||
 +
|}
 +
 
 +
Next bug deputy round
 +
{| class="wikitable" style="text-align: center;"
 
|-
 
|-
| October-8-2018 || Slawek Kaplonski (slaweq)
+
! Date !! who !! note
 
|-
 
|-
| October-15-2018 || Brian Haley (haleyb)
+
| December-23-2019 || Bernard Cafarelli (bcafarel) ||
 
|-
 
|-
| October-22-2018 || Armando Migliaccio (armax)
+
| December-30-2019 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| October-29-2018 || Zhao Bo(bzhao)
+
| January-6-2020 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| November-5-2018 || Manjeet  Bhatia (manjeets)
+
| Januaryu-13-2020 || Brian Haley (haleyb) ||
 
|-
 
|-
| November-12-2018 || Lujin Luo(lujinluo)
+
| January-20-2020 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| November-19-2018 || YAMAMOTO Takashi (yamamoto)
+
| January-27-2020 || Ryan Tidwell (tidwellr) ||
 
|-
 
|-
| November-26-2018 || Miguel Lavalle (mlavalle)
+
| February-3-2020 || Swaminathan Vasudevan (Swami) ||
 +
|-
 +
| February-10-2020 || Akihiro Motoki (amotoki)  ||
 +
|-
 +
| February-17-2020 || Nate Johnston (njohnston) ||
 +
|-
 +
| Fabruary-24-2020 || Miguel Lavalle (mlavalle) ||
 +
|-
 +
| 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
  
=== Ryu support ===
+
=== Neutron performance subteam (Monday meetings) ===
  
# Get approval  from TC to create a Ryu project underneath OpenStack
+
=== Networking OVN and ML2+OVS+DVR Convergence (Tuesday meetings) ===
# Fork and create the project under OpenStack
+
 
# 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 123: Line 156:
 
=== 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.
+
Releasing new version after merging:
 
+
* https://review.opendev.org/#/c/695205/
'''DO NOT TOP POST - ADD PATCHES TO THE BOTTOM OF THE LIST'''
+
* https://review.opendev.org/#/c/692580/
 +
* https://review.opendev.org/#/c/696308/
 +
* https://review.opendev.org/#/c/696070/ - merged
  
* 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 142: Line 177:
  
 
* Topic for the meeting (keep this template, please):
 
* Topic for the meeting (keep this template, please):
 +
** (your nickname): brief description.
 +
*** More details
  
 
== 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/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]

Latest revision as of 12:03, 3 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

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

Releasing new version after merging:

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