Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Bugs and Gate issues)
(Bugs and Gate issues)
 
(140 intermediate revisions by 7 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
 +
* We released Ussuri version! Congrats everyone!
 +
** https://releases.openstack.org/ussuri/
 +
* we are now in the Victoria cycle already https://releases.openstack.org/victoria/schedule.html
 +
** Victoria-1 milestone is in the week of Jun 15th - in 4 weeks
 +
* Victoria PTG
 +
** In 2 weeks
 +
** planning etherpad: https://etherpad.openstack.org/p/neutron-victoria-ptg - next week I will start planning sessions so would be good to have list of topics more or less finalized,
 +
** Registration is live: http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014649.html
 +
** we will have nova-neutron session on Friday 13:00 UTC, we will also discuss some Cyborg related topics on this session,
 +
** More info http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014126.html
 +
* Virtual OpenDev http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014297.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)
 
* 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)
* Today I sent emails about "new daddies need" for
 
** neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html
 
** networking-bagpipe/bgpvpn: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010930.html
 
** neutron-vpnaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010931.html
 
* Removing of neutron-interconnection from stadium project is in progress: https://review.opendev.org/#/q/branch:master+topic:neutron-interconnection-retire
 
* CI jobs cleaning proposed plan: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010838.html
 
  
 
=== Blueprints ===
 
=== Blueprints ===
  
  
Blueprints which we should include in Ussuri milestones:
+
Blueprints which we should include in Victoria milestones:
* Blueprints for Ussuri-1: https://launchpad.net/neutron/+milestone/ussuri-1
+
* Blueprints for Victoria-1: https://launchpad.net/neutron/+milestone/victoria-1
* 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/dns-records-in-neutron - mlavalle, can You be approver of this one?
* https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes
+
*** spec is now proposed https://review.opendev.org/#/c/726904/ - we need to review it
* 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/sg-sharing-as-readonly - amotoki, can You be approver of this one?
* 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/
+
*** rm_work - can You be assigned to this one?
* https://bugs.launchpad.net/neutron/+bug/1460177 - [RFE] Support metadata service with IPv6-only tenant network
 
* https://bugs.launchpad.net/neutron/+bug/1815933 - [RFE] Allow bulk-tagging of resources
 
* https://bugs.launchpad.net/neutron/+bug/1825345 - [RFE] admin-state-down doesn't evacuate bindings in the dhcp_agent_id column - zigo is I think working on it now,
 
* https://bugs.launchpad.net/neutron/+bug/1841067 - [RFE] SR-IOV agent depends on mac addresses for getting bound ports
 
* https://bugs.launchpad.net/neutron/+bug/1850818 - [RFE][floatingip port_forwarding] Add description field
 
* https://bugs.launchpad.net/neutron/+bug/1843218 - [RFE] allow to create record on default zone from tenants
 
  
 
=== Community Goals ===
 
=== Community Goals ===
Line 32: Line 31:
 
This slot is to used to track the progress of the 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
 
https://governance.openstack.org/tc/goals/index.html#release-cycles
 +
 +
* Migrate to zuulv3
 +
** Etherpad: https://etherpad.openstack.org/p/neutron-train-zuulv3-py27drop
  
 
* Support IPv6-Only Deployments (slaweq)
 
* Support IPv6-Only Deployments (slaweq)
Line 38: Line 40:
 
** Patches for stadium projects are needed:
 
** 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-.*)
 
*** 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,
+
*** there are some patches for networking-bagpipe/bgpvpn and networking-odl there - maintainers of those projects, please take a look at them :)
 
+
*** I just rebased neutron-tempest-plugin patch https://review.opendev.org/686043 and will try to continue work on it,
* Community goals for Ussuri
 
** Proposals: https://etherpad.openstack.org/p/PVG-u-series-goals
 
 
 
* Drop Python 2.7 Support
 
** https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
 
 
 
Other goals not accepted yet
 
  
 
=== Bugs and Gate issues ===
 
=== Bugs and Gate issues ===
  
Bugs report for week of October 28th: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010521.html
+
rubasov was bug deputy; Report http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014913.html
Bugs report for week of November 4th: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010676.html
 
Bugs report for week of November 11th: https://docs.google.com/spreadsheets/d/1DdWgFhMWrK67YJHBgzSbnOcFprQbOLFM16WQcPt0RS8/edit#gid=0
 
  
Bugs which needs some attention:
+
Some bugs needs volunteers:
* https://bugs.launchpad.net/neutron/+bug/1851659 - L3 subteam should take a look,
+
* https://bugs.launchpad.net/neutron/+bug/1877977 - do we really need veth interconnection still?
* https://bugs.launchpad.net/neutron/+bug/1851500 - CI failure in networking-sfc job,
+
* https://bugs.launchpad.net/neutron/+bug/1878299 - needs L3 subteam attention probably,
* https://bugs.launchpad.net/neutron/+bug/1851194 - fwaas bug, I'm not sure if we have anyone who can take a look into that now,
 
  
 
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 71: Line 63:
 
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;"
Line 77: Line 69:
 
! Date !! who !! note
 
! Date !! who !! note
 
|-
 
|-
| September-30-2019 || Bernard Cafarelli (bcafarel) ||
+
| March-9-2020 || Bernard Cafarelli (bcafarel) ||
 
|-
 
|-
| October-7-2019 || Slawek Kaplonski (slaweq) ||
+
| March-16-2020 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| October-14-2019 || Hongbin Lu (hongbin) ||
+
| March-23-2020 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| October-21-2019 || Brian Haley (haleyb)  ||
+
| March-30-2020 || Brian Haley (haleyb)  ||
 
|-
 
|-
| October-28-2019 || Lajos Katona (lajoskatona) ||
+
| April-6-2020 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| November-4-2019 || Ryan Tidwell (tidwellr)  ||
+
| April-13-2020 || Ryan Tidwell (tidwellr)  ||
 
|-
 
|-
| November-11-2019 || Swaminathan Vasudevan (Swami) ||
+
| April-20-2020 || Nate Johnston (njohnston) ||
 
|-
 
|-
| November-18-2019 || Akihiro Motoki (amotoki)  || switched with Miguel Lavalle (mlavalle)
+
| April-27-2020 || Akihiro Motoki (amotoki)  ||
 
|-
 
|-
| November-25-2019 || Nate Johnston (njohnston) ||
+
| May-4-2020 || Miguel Lavalle (mlavalle) ||
 
|-
 
|-
| December-2-2019 || Miguel Lavalle (mlavalle) || switched with Akihiro Motoki (amotoki)
+
| May-11-2020 || Bence Romsics (rubasov) ||
 
|-
 
|-
| December-9-2019 || YAMAMOTO Takashi (yamamoto) ||
+
| May-18-2020 || Maciej Jozefczyk (maciejjozefczyk) ||
 
|-
 
|-
| December-16-2019 || Bence Romsics (rubasov) ||
+
| May-25-2020 || Rodolfo Alonso Hernandez (ralonsoh) ||
 +
|-
 +
| June-1-2020 || Lucas Alvares Gomes (lucasgomes) ||
 +
|-
 +
| June-8-2020 || Jakub Libosvar (jlibosva) ||
 
|}
 
|}
  
 
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) ===
  
 
=== Docs ===
 
=== Docs ===
Line 128: Line 126:
 
* Decouple DB workstream/blueprint: https://review.openstack.org/#/q/status:open+topic:bp/neutronlib-decouple-db+label:Workflow%253D0
 
* 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
 
* 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 135: Line 132:
  
 
* Topic for the meeting (keep this template, please):
 
* Topic for the meeting (keep this template, please):
** (your nickname): brief description.
+
** (nick): Topic
 
*** More details
 
*** More details
** (slaweq) My availability next week
+
** Review https://review.opendev.org/#/c/665467
 +
*** please review this and provide feedback so it can be merged.
  
 
== 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/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]

Latest revision as of 11:35, 19 May 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 Victoria 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

rubasov was bug deputy; Report http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014913.html

Some bugs needs volunteers:

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
March-9-2020 Bernard Cafarelli (bcafarel)
March-16-2020 Slawek Kaplonski (slaweq)
March-23-2020 Hongbin Lu (hongbin)
March-30-2020 Brian Haley (haleyb)
April-6-2020 Lajos Katona (lajoskatona)
April-13-2020 Ryan Tidwell (tidwellr)
April-20-2020 Nate Johnston (njohnston)
April-27-2020 Akihiro Motoki (amotoki)
May-4-2020 Miguel Lavalle (mlavalle)
May-11-2020 Bence Romsics (rubasov)
May-18-2020 Maciej Jozefczyk (maciejjozefczyk)
May-25-2020 Rodolfo Alonso Hernandez (ralonsoh)
June-1-2020 Lucas Alvares Gomes (lucasgomes)
June-8-2020 Jakub Libosvar (jlibosva)

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)

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

Previous meeting logs