Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Announcements / Reminders)
 
(370 intermediate revisions by 10 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Next milestone is T-3, week of September 9
+
* Wallaby cycle calendar https://releases.openstack.org/wallaby/schedule.html
** https://releases.openstack.org/train/schedule.html
+
** This week is W-2 milestone, next milestone will be in March 8th
* ralonsoh nominated to Neutron core: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008225.html
+
*** should we also do new releases for stable branches?
* Shanghai PTG planning etherpad
+
** stein EM, now we have stein-last tag in neutron-tempest-plugin also: https://review.opendev.org/c/openstack/releases/+/768553
** https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
+
** Please focus on reviewing opened specs related to the approved rfes:
** If you are planning to attend, please enter your name at the top of the pad no later than August 4th
+
*** https://review.opendev.org/c/openstack/neutron-specs/+/729532
** Please also free to propose topics. We don't have deadline for this other than the PTG itself
+
*** https://review.opendev.org/c/openstack/neutron-specs/+/658451
* Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html
+
*** https://review.opendev.org/c/openstack/neutron-specs/+/728628
 +
*** https://review.opendev.org/c/openstack/neutron-specs/+/739549 - merged
 +
** I started work on SDK/OSC patches to allow "unknown parameters" there, please check https://review.opendev.org/c/openstack/openstacksdk/+/768208 and https://review.opendev.org/c/openstack/python-openstackclient/+/768210 and tell me if that makes sense for You so I will continue that work,
 +
* Virtual PTG summary http://kaplonski.pl/blog/virtual_ptg_october_2020_summary/
 +
week
  
 
=== Blueprints ===
 
=== Blueprints ===
  
Train-3 blueprints: https://launchpad.net/neutron/+milestone/train-3
+
Blueprints which we should include in Wallaby milestones:
  
Patches up for review:
+
* Wallaby-2 https://bugs.launchpad.net/neutron/+milestone/wallaby-2
* 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/enginefacade-switch
* https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - spec is here: https://review.opendev.org/#/c/657170 - please review it,
+
*** Patches: https://review.opendev.org/#/q/status:open+topic:bp/enginefacade-switch
* https://blueprints.launchpad.net/neutron/+spec/subnets-different-pools-same-net - patch https://review.opendev.org/#/c/667511/ - looks that is in good shape now, please review,
+
*** all neutron changes done,
* 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)
+
*** stadium project changes:
* https://blueprints.launchpad.net/neutron/+spec/improve-extraroute-api - patches https://review.opendev.org/#/q/topic:extraroute+(status:open+OR+status:merged) - there is good progress on that one IMO, many patches are waiting for review now
+
**** networking-midonet: https://review.opendev.org/c/openstack/networking-midonet/+/770797
 +
**** neutron-vpnaas: https://review.opendev.org/c/openstack/neutron-vpnaas/+/770800
 +
*** neutron documentation changes: https://review.opendev.org/c/openstack/neutron/+/770826
 +
** https://blueprints.launchpad.net/neutron/+spec/secure-bac-roles
 +
*** patches https://review.opendev.org/q/topic:%2522secure-rbac%2522+(status:open+OR+status:merged)+project:openstack/neutron,
 +
*** we only merged https://review.opendev.org/c/openstack/neutron/+/770118 and migrated segments api to new rbac last week,
 +
** https://blueprints.launchpad.net/neutron/+spec/address-groups-in-sg-rules
 +
*** Patches https://review.opendev.org/#/q/topic:bp/address-groups-in-sg-rules
 +
** https://blueprints.launchpad.net/neutron/+spec/default-dns-zone-per-tenant
 +
*** Neutron patch https://review.opendev.org/#/c/686343/
 +
*** neutron-tempest-plugin test https://review.opendev.org/#/c/733994/
 +
** https://blueprints.launchpad.net/neutron/+spec/nftables-migration
 +
** https://bugs.launchpad.net/neutron/+bug/1882804 - allow replacing the QoS policy of bound port
 +
*** Tempest test https://review.opendev.org/#/c/743695/
 +
** https://bugs.launchpad.net/neutron/+bug/1863113 - George framework
 +
*** patches https://review.opendev.org/#/q/topic:george+(status:open+OR+status:merged) - all ready for review now
 +
** https://bugs.launchpad.net/neutron/+bug/1580927
 +
 
 +
* Moved to neutron-next:
 +
** https://blueprints.launchpad.net/neutron/+spec/evacuate-agent-resources
 +
** https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes
 +
** https://blueprints.launchpad.net/neutron/+spec/sg-sharing-as-readonly
  
 
=== Community Goals ===
 
=== Community Goals ===
Line 29: Line 54:
 
https://governance.openstack.org/tc/goals/index.html#release-cycles
 
https://governance.openstack.org/tc/goals/index.html#release-cycles
  
* Run under Python 3 by default (njohnston)
+
* Migrate from oslo.rootwrap to oslo.privsep (ralonsoh)
** https://governance.openstack.org/tc/goals/stein/python3-first.html
+
** https://governance.openstack.org/tc/goals/selected/wallaby/migrate-to-privsep.html
 +
** tracking progress: https://etherpad.opendev.org/p/neutron-migration-to-privsep
 +
 
 +
* Migrate RBAC Policy Format from JSON to YAML (amotoki)
 +
** gmann's email http://lists.openstack.org/pipermail/openstack-discuss/2020-November/019079.html
 +
** https://review.opendev.org/c/openstack/neutron/+/764401
 +
** https://review.opendev.org/c/openstack/neutron-lib/+/764416 - merged
  
 
* Support IPv6-Only Deployments (slaweq)
 
* Support IPv6-Only Deployments (slaweq)
 
** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
 
** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
** gmann started pushing some patches to various projects. He asked for neutron stadium projects and I did some list here http://lists.openstack.org/pipermail/openstack-discuss/2019-July/008084.html - please check it
+
** 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-.*)
 +
*** 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,
 +
 
 +
=== Bugs and Gate issues ===
  
* Enabling PDF generation support for project documentation (amotoki)
+
mlavalle was bug deputy, report: http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019878.html
** https://governance.openstack.org/tc/goals/train/pdf-doc-generation.html
 
  
=== Bugs and Gate issues ===
+
Bugs which needs attention:
  
Bugs report for week of July 29th: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008258.html
 
  
 
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 55: Line 90:
 
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 61: Line 96:
 
! Date !! who !! note
 
! Date !! who !! note
 
|-
 
|-
| July-1-2019 || Bernard Cafarelli (bcafarel) ||
+
| Nov-30-2020 || Bernard Cafarelli (bcafarel) ||
 
|-
 
|-
| July-8-2019 || Slawek Kaplonski (slaweq) ||
+
| Dec-7-2020 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| July-15-2019 || Hongbin Lu (hongbin) ||
+
| Dec-14-2020 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| July-22-2019 || Boden Russel (boden) ||
+
| Dec-21-2020 || Brian Haley (haleyb) ||
 
|-
 
|-
| July-29-2019 || Brian Haley (haleyb) ||
+
| Dec-28-2020 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| August-5-2019 || Lajos Katona (lajoskatona) || replaced by amotoki for Aug 5
+
| Jan-4-2021 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| August-12-2019 || Ryan Tidwell (tidwellr)  ||
+
| Jan-11-2021 || Miguel Lavalle (mlavalle)  ||
 
|-
 
|-
| August-19-2019 || Swaminathan Vasudevan (Swami) ||
+
| Jan-18-2021 || Bence Romsics (rubasov) ||
 
|-
 
|-
| August-26-2019 || Akihiro Motoki (amotoki) || replaced by lajoskatona for Aug 26
+
| Jan-25-2021 || Rodolfo Alonso Hernandez (ralonsoh) ||
 
|-
 
|-
| September-2-2019 || Nate Johnston (njohnston) ||
+
| Feb-1-2021 || Lucas Alvares Gomes (lucasgomes) ||
 
|-
 
|-
| September-9-2019 || Miguel Lavalle (mlavalle) ||
+
| Feb-8-2021 || Jakub Libosvar (jlibosva) ||
 
|-
 
|-
| September-16-2019 || YAMAMOTO Takashi (yamamoto) ||
+
| Feb-15-2021 || Oleg Bondarev (obondarev) ||
|-
 
| September-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
  
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 ===
 +
 
 +
=== New engine facade ===
 +
* BP: https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch
 +
* Neutron "progress" patch: https://review.opendev.org/#/c/545501/
 +
* Patch https://review.opendev.org/#/c/715315/ should finish it in Neutron
 +
* Stadium projects' required changes: TBD
  
 
=== Docs ===
 
=== Docs ===
Line 96: Line 136:
  
 
=== CLI/SDK ===
 
=== CLI/SDK ===
 +
 +
Allow not defined arguments to be passed in OSC,
 +
Documentation of neutronclient https://docs.openstack.org/python-neutronclient/latest/cli/neutron.html#extra-arguments-for-create-update-operation
 +
OSC work: TBD
  
 
SDK migration of neutronclient python bindings
 
SDK migration of neutronclient python bindings
Line 105: Line 149:
  
 
=== Neutron-lib, planned refactoring and other impacts ===
 
=== Neutron-lib, planned refactoring and other impacts ===
 
* proposed release of 1.28: https://review.opendev.org/#/c/666870/
 
  
 
HOUSE KEEPING
 
HOUSE KEEPING
Line 116: Line 158:
 
* 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 123: Line 164:
  
 
* Topic for the meeting (keep this template, please):
 
* Topic for the meeting (keep this template, please):
** (your nickname): brief description.
+
** (irc nick): topic
*** More details
+
*** additional data
  
 +
** (erlon): Security Groups Rule API Bulk updates
 +
*** https://docs.openstack.org/api-ref/network/v2/index.html?expanded=update-security-group-detail,create-security-group-rule-detail#security-group-rules-security-group-rules
  
* neutron-lib backports/ neutron backports from neutron-lib
 
** (bcafarel): should we start doing neutron-lib backports (and point releases)? And if no, what to do with neutron backports (older branch) coming from a neutron-lib fix?
 
*** Current case: https://review.opendev.org/#/c/672166/ is a Rocky neutron backport of neutron-lib Stein https://review.opendev.org/#/c/672165/
 
*** question was asked in neutron-lib backport: should we start doing such backports and point releases?
 
*** rocky/queens backports are in neutron itself, but waiting for the newer stable version to get the fix (stein in that case for neutron-lib)
 
  
 
== 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/2021/?C=M;O=D networking-2021]
 +
** [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 13:48, 19 January 2021

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

week

Blueprints

Blueprints which we should include in Wallaby 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

mlavalle was bug deputy, report: http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019878.html

Bugs which needs attention:


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
Nov-30-2020 Bernard Cafarelli (bcafarel)
Dec-7-2020 Slawek Kaplonski (slaweq)
Dec-14-2020 Hongbin Lu (hongbin)
Dec-21-2020 Brian Haley (haleyb)
Dec-28-2020 Lajos Katona (lajoskatona)
Jan-4-2021 Akihiro Motoki (amotoki)
Jan-11-2021 Miguel Lavalle (mlavalle)
Jan-18-2021 Bence Romsics (rubasov)
Jan-25-2021 Rodolfo Alonso Hernandez (ralonsoh)
Feb-1-2021 Lucas Alvares Gomes (lucasgomes)
Feb-8-2021 Jakub Libosvar (jlibosva)
Feb-15-2021 Oleg Bondarev (obondarev)

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

New engine facade

Docs

CLI/SDK

Allow not defined arguments to be passed in OSC, Documentation of neutronclient https://docs.openstack.org/python-neutronclient/latest/cli/neutron.html#extra-arguments-for-create-update-operation OSC work: TBD

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):
    • (irc nick): topic
      • additional data


Previous meeting logs