Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Announcements / Reminders)
(Announcements / Reminders)
 
(541 intermediate revisions by 13 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Next milestone is T-3, week of September 9
+
* Yoga cycle calendar https://releases.openstack.org/yoga/schedule.html
** https://releases.openstack.org/train/schedule.html
+
* October PTG:
* ralonsoh nominated to Neutron core: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008225.html
+
** announcement http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023370.html
* Shanghai PTG planning etherpad
+
** etherpad https://etherpad.opendev.org/p/neutron-yoga-ptg
** https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
+
** for now I booked 3h slots every day, 1300-1600 UTC except Monday when there is 2h 1300 - 1500 UTC
** If you are planning to attend, please enter your name at the top of the pad no later than August 4th
+
*** there will be also TC & PTLs session in Monday 1500-1700 UTC
** Please also free to propose topics. We don't have deadline for this other than the PTG itself
+
** Operators pain points: http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024487.html
* Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html
+
* OpenInfra Live event - https://openinfra.dev/live/#all-episodes - there are some interesting presentations there, maybe You would be interested in some of them,
 +
** PTG summary at http://lists.openstack.org/pipermail/openstack-discuss/2021-April/022044.html and also at http://kaplonski.pl/blog/virtual_ptg_april_2021_summary/
  
 
=== Blueprints ===
 
=== Blueprints ===
  
Train-3 blueprints: https://launchpad.net/neutron/+milestone/train-3
+
Blueprints which we should include in Xena milestones:
  
Patches up for review:
+
* Neutron Xena-RC2 https://bugs.launchpad.net/neutron/+milestone/xena-rc2
* https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/
+
* Moved to neutron-next:
* https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - spec is here: https://review.opendev.org/#/c/657170 - please review it,
+
** https://blueprints.launchpad.net/neutron/+spec/sg-sharing-as-readonly
* 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,
+
** https://blueprints.launchpad.net/neutron/+spec/bfd-support-for-neutron
* 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)
+
** https://blueprints.launchpad.net/neutron/+spec/explicit-management-of-default-routes
* 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
+
** https://blueprints.launchpad.net/neutron/+spec/multiple-external-gateways
 +
** https://blueprints.launchpad.net/neutron/+spec/bgp-enhancement
 +
** https://blueprints.launchpad.net/neutron/+spec/evacuate-agent-resources
 +
** https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes
 +
** 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/bugs/1931100
  
 
=== Community Goals ===
 
=== Community Goals ===
Line 29: Line 36:
 
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)
+
=== Bugs and Gate issues ===
** https://governance.openstack.org/tc/goals/stein/python3-first.html
 
 
 
* Support IPv6-Only Deployments (slaweq)
 
** 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
 
  
* Enabling PDF generation support for project documentation (amotoki)
+
ralonsoh was bug deputy last week: http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025267.html
** https://governance.openstack.org/tc/goals/train/pdf-doc-generation.html
 
  
=== Bugs and Gate issues ===
+
This week lucasgomes is the deputy, and next week jlibosva will be.
  
Bugs report for week of July 29th: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008258.html
+
Unassigned bugs:
 +
* https://bugs.launchpad.net/neutron/+bug/1946456 [OVN] Scheduling of HA Chassis Group for external port does not work when no chassis has 'enable-chassis-as-gw' option set
 +
* https://bugs.launchpad.net/neutron/+bug/1946187 HA routers not going to be "primary" at all
  
 
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 58:
 
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 64:
 
! Date !! who !! note
 
! Date !! who !! note
 
|-
 
|-
| July-1-2019 || Bernard Cafarelli (bcafarel) ||
+
| Aug-9-2021 || Bernard Cafarelli (bcafarel) || switch with Miguel Lavalle (mlavalle)
|-
 
| July-8-2019 || Slawek Kaplonski (slaweq) ||
 
 
|-
 
|-
| July-15-2019 || Hongbin Lu (hongbin) ||
+
| Aug-16-2021 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| July-22-2019 || Boden Russel (boden) ||
+
| Aug-23-2021 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| July-29-2019 || Brian Haley (haleyb)  ||
+
| Aug-30-2021 || Brian Haley (haleyb)  ||
 
|-
 
|-
| August-5-2019 || Lajos Katona (lajoskatona) || replaced by amotoki for Aug 5
+
| Sep-6-2021 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| August-12-2019 || Ryan Tidwell (tidwellr) ||
+
| Sep-13-2021 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| August-19-2019 || Swaminathan Vasudevan (Swami) ||
+
| Sep-20-2021 || Miguel Lavalle (mlavalle) || switch with Bernard Cafarelli (bcafarel)
 
|-
 
|-
| August-26-2019 || Akihiro Motoki (amotoki) || replaced by lajoskatona for Aug 26
+
| Sep-27-2021 || Bence Romsics (rubasov) ||
 
|-
 
|-
| September-2-2019 || Nate Johnston (njohnston) ||
+
| Oct-4-2021 || Rodolfo Alonso Hernandez (ralonsoh) ||
 
|-
 
|-
| September-9-2019 || Miguel Lavalle (mlavalle) ||
+
| Oct-11-2021 || Lucas Alvares Gomes (lucasgomes) ||
 
|-
 
|-
| September-16-2019 || YAMAMOTO Takashi (yamamoto) ||
+
| Oct-18-2021 || Jakub Libosvar (jlibosva) ||
 
|-
 
|-
| September-23-2019 || Bence Romsics (rubasov) ||
+
| Oct-27-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
 
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
 +
 +
=== L3 subteam ===
 +
 +
=== ryu os-ken ===
 +
 +
https://etherpad.opendev.org/p/make_os-ken_and_ryu_sync
 +
 +
=== Neutron performance subteam ===
 +
 +
obondarev is doing a lot of great work in that area recently. His patches https://review.opendev.org/q/owner:oleg.bondarev%2540huawei.com+project:openstack/neutron+status:open
  
 
=== Docs ===
 
=== Docs ===
Line 94: Line 105:
 
* The future of OpenStack documentation - http://lists.openstack.org/pipermail/openstack-dev/2016-July/099012.html
 
* The future of OpenStack documentation - http://lists.openstack.org/pipermail/openstack-dev/2016-July/099012.html
 
* Documentation bugs - https://bugs.launchpad.net/neutron/+bugs?field.tag=doc
 
* Documentation bugs - https://bugs.launchpad.net/neutron/+bugs?field.tag=doc
 
=== 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)
 
* https://etherpad.openstack.org/p/osc-transition-priorities
 
* http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html
 
  
 
=== 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 116:
 
* 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 122:
  
 
* Topic for the meeting (keep this template, please):
 
* Topic for the meeting (keep this template, please):
** (your nickname): brief description.
+
** (nick): topic
*** More details
+
**
 
 
 
 
* 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:57, 12 October 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

Blueprints

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

ralonsoh was bug deputy last week: http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025267.html

This week lucasgomes is the deputy, and next week jlibosva will be.

Unassigned bugs:

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
Aug-9-2021 Bernard Cafarelli (bcafarel) switch with Miguel Lavalle (mlavalle)
Aug-16-2021 Slawek Kaplonski (slaweq)
Aug-23-2021 Hongbin Lu (hongbin)
Aug-30-2021 Brian Haley (haleyb)
Sep-6-2021 Lajos Katona (lajoskatona)
Sep-13-2021 Akihiro Motoki (amotoki)
Sep-20-2021 Miguel Lavalle (mlavalle) switch with Bernard Cafarelli (bcafarel)
Sep-27-2021 Bence Romsics (rubasov)
Oct-4-2021 Rodolfo Alonso Hernandez (ralonsoh)
Oct-11-2021 Lucas Alvares Gomes (lucasgomes)
Oct-18-2021 Jakub Libosvar (jlibosva)
Oct-27-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

L3 subteam

ryu os-ken

https://etherpad.opendev.org/p/make_os-ken_and_ryu_sync

Neutron performance subteam

obondarev is doing a lot of great work in that area recently. His patches https://review.opendev.org/q/owner:oleg.bondarev%2540huawei.com+project:openstack/neutron+status:open

Docs

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

Previous meeting logs