Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Announcements / Reminders)
(New engine facade)
 
(534 intermediate revisions by 20 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Next milestone, Rocky-1, April 16 - 20
+
* According to the Victoria cycle calendar https://releases.openstack.org/victoria/schedule.html
* Rocky release schedule: https://releases.openstack.org/rocky/schedule.html
+
** We reached feature freeze for Victoria release - only bug fixes allowed from now until we will cut stable/victoria branch - please be aware while reviewing patches,
* Rocky PTG summary: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128183.html
+
** RC1 is in week of 21st September
 +
* Virtual PTG in October (26-30): http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016424.html
 +
** booked slots on every day, see for details http://lists.openstack.org/pipermail/openstack-discuss/2020-September/017077.html
 +
** etherpad: https://etherpad.opendev.org/p/neutron-wallaby-ptg - please add ideas of the topics there, it is still empty
 +
* Wallaby release schedule is live: https://releases.openstack.org/wallaby/schedule.html
 +
* Forum brainstorming: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016581.html
 +
* Virtual PTG summary http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015368.html,
  
 
=== Blueprints ===
 
=== Blueprints ===
  
mlavalle will update Launchpad this week with dashboard to track blueprint implementation during Rocky
+
Blueprints which we should include in Victoria milestones:
 +
* Blueprints for Victoria-3: https://launchpad.net/neutron/+milestone/victoria-3
 +
** https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch
 +
*** Patches: https://review.opendev.org/#/q/status:open+topic:bp/enginefacade-switch
 +
*** slowly continue this,
 +
** https://blueprints.launchpad.net/neutron/+spec/metadata-over-ipv6
 +
*** Patches https://review.opendev.org/#/q/topic:metadata-ipv6+(status:open+OR+status:merged)
 +
*** moved to rc1 but just to add some scenario tests, all code is merged already
 +
** https://bugs.launchpad.net/neutron/+bug/1882804 - allow replacing the QoS policy of bound port
 +
*** Patches: https://review.opendev.org/#/q/topic:bug/1882804+(status:open+OR+status:merged)
 +
*** do we still want to finish that in this cycle? If so we need FFE request for that,
 +
** 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
 +
*** we can continue this one as it's just testing thing,
 +
** https://blueprints.launchpad.net/neutron/+spec/local-ip-prefix-in-metering-rules
 +
*** Patches: https://review.opendev.org/#/q/topic:bug/1889431+(status:open+OR+status:merged)
 +
*** We already deprecated old parameter so we should merge this one in this cycle probably, but we now need FFE request if we want to continue this in current cycle
  
==== OVO/no API downtime ====
+
* Moved to neutron-next:
 
+
** https://blueprints.launchpad.net/neutron/+spec/evacuate-agent-resources
List here patches/topics that need core reviewer attention.
+
** https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes
 
+
** https://blueprints.launchpad.net/neutron/+spec/sg-sharing-as-readonly
* add your patch here
+
** https://blueprints.launchpad.net/neutron/+spec/handle-deadlocks-in-oslo-way
 +
** 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/address-groups-in-sg-rules
 +
*** Patches https://review.opendev.org/#/q/topic:bp/address-groups-in-sg-rules
  
 
=== Community Goals ===
 
=== Community Goals ===
Line 23: Line 50:
 
https://governance.openstack.org/tc/goals/index.html#release-cycles
 
https://governance.openstack.org/tc/goals/index.html#release-cycles
  
* policy-in-code (Queens)
+
* Migrate CI/CD jobs to new Ubuntu LTS Focal
* wsgi support (Pike)
+
** Goal description https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal.html
* Enable mutable configuration (Rocky) https://governance.openstack.org/tc/goals/rocky/enable-mutable-configuration.html
+
** Current plan: http://lists.openstack.org/pipermail/openstack-discuss/2020-September/017060.html
* mox3 removal (Rocky) https://bugs.launchpad.net/python-neutronclient/+bug/1753504
+
** Devstack patch https://review.opendev.org/731207
 +
** neutron functional and fullstack jobs switch https://review.opendev.org/#/c/734304/
 +
*** it should be ok with https://review.opendev.org/#/c/744500/
 +
** neutron-tempest-dvr-ha-multinode-full job switch https://review.opendev.org/737370
 +
*** this one seems ok
 +
** neutron-tempest-plugin jobs: https://review.opendev.org/#/c/748367/ - almost ok,
  
* Split Tempest Plugins into Separate Repos/Projects (Queens) : Completed (we can drop it from the next meeting)
+
* Zuul v3 migration
** https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html#neutron
+
** based on last email from tosky http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016058.html we are not done with this yet,
 +
** etherpad: https://etherpad.opendev.org/p/goal-victoria-native-zuulv3-migration
  
=== Starter Approved RFEs ===
+
* Support IPv6-Only Deployments (slaweq)
 +
** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
 +
** 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,
  
This section is for advertising approved RFEs that the Neutron Drivers team have deemed suitable for new contributors:
+
=== Bugs and Gate issues ===
 
 
* Network router:external field not exported: https://bugs.launchpad.net/neutron/+bug/1653932
 
  
=== Bugs and Gate issues ===
+
my report from two weeks ago: http://lists.openstack.org/pipermail/openstack-discuss/2020-September/017254.html
  
Bug deputy report for week of February 26th: http://lists.openstack.org/pipermail/openstack-dev/2018-March/127925.html
+
Bugs which needs attention:
 +
* https://bugs.launchpad.net/neutron/+bug/1894864 and related https://bugs.launchpad.net/neutron/+bug/1895196
 +
* https://bugs.launchpad.net/neutron/+bug/1894913 - not assigned but I asked what could change in the failed job that it caused such issue,
 +
* https://bugs.launchpad.net/neutron/+bug/1894843 - I didn't had time to reproduce the issue yet, sounds like bug for L3 subteam,
  
A full hour is dedicated to this topic, and more during the following meeting:
+
More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI
  
* https://wiki.openstack.org/wiki/Meetings/NeutronCI
 
 
* [https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.tag=gate-failure Confirmed gate failures]
 
* [https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.tag=gate-failure Confirmed gate failures]
 
* [https://bugs.launchpad.net/neutron/+bugs?field.tag=needs-attention Bugs that need attention]
 
* [https://bugs.launchpad.net/neutron/+bugs?field.tag=needs-attention Bugs that need attention]
Line 54: Line 93:
 
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
|-
 
| January-8-2018 || Hirofumi Ichihara (hichihara)
 
|-
 
| January-15-2018 || Gary Kotton (garyk)
 
|-
 
| January-22-2018 || Akihiro Motoki (amotoki)
 
|-
 
| January-29-2018 || Jakub Libosvar (jlibosva)
 
 
|-
 
|-
| February-5-2018 || Boden Russel (boden)
+
| Aug-31-2020 || Bernard Cafarelli (bcafarel) ||
 
|-
 
|-
| February-12-2018 || James Anziano (janzian)
+
| Sep-7-2020 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| February-19-2018 || Ihar Hrachyshka (ihrachys)
+
| Sep-14-2020 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| February-26-2018 || Slawek Kaplonski (slaweq)
+
| Sep-21-2020 || Brian Haley (haleyb) ||
 
|-
 
|-
| March-5-2018 || Brian Haley (haleyb)
+
| Sep-28-2020 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| March-12-2018 || Zhao Bo(bzhao)
+
| Oct-5-2020 || Nate Johnston (njohnston) ||
 
|-
 
|-
| March-19-2018 || Armando Migliaccio (armax)
+
| Oct-12-2020 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| March-26-2018 || Swaminathan Vasudevan (Swami)
+
| Oct-19-2020 || Miguel Lavalle (mlavalle) ||
 
|-
 
|-
| April-2-2018 || Lujin Luo(lujinluo)
+
| Oct-26-2020 || Bence Romsics (rubasov) ||
 
|-
 
|-
| April-9-2018 || YAMAMOTO Takashi (yamamoto)
+
| Nov-2-2020 || Rodolfo Alonso Hernandez (ralonsoh) ||
 
|-
 
|-
| April-16-2018 || Miguel Lavalle (mlavalle)
+
| Nov-9-2020 || Lucas Alvares Gomes (lucasgomes) ||
 
|-
 
|-
| April-23-2018 || Pawel Suder (pasuder)
+
| Nov-16-2020 || Jakub Libosvar (jlibosva) ||
 
|-
 
|-
| April-30-2018 || Hongbin Lu (hongbin)
 
 
|}
 
|}
  
 
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/
 +
* Now I'm stucked with the patch https://review.opendev.org/#/c/715315/ - maybe someone wants to take a look and help with this :)
 +
* Stadium projects' required changes: TBD
  
 
=== Docs ===
 
=== Docs ===
Line 103: Line 141:
  
 
=== CLI/SDK ===
 
=== CLI/SDK ===
Status of changes to deliver OSC
+
 
 +
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)
 
* https://etherpad.openstack.org/p/osc-transition-priorities
 
* https://etherpad.openstack.org/p/osc-transition-priorities
 
* http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html
 
* http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html
Line 109: Line 155:
 
=== 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.
+
HOUSE KEEPING
 
+
* Neutron-lib work items and volunteers are being tracked via etherpad: https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list
'''DO NOT TOP POST - ADD PATCHES TO THE BOTTOM OF THE 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
 
** 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.
 
** 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).
 
* Patches that need high-level input from neutron cores: https://review.openstack.org/#/q/message:%22NeutronCoreInputNeeded%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
  
 
=== On Demand Agenda ===
 
=== On Demand Agenda ===
Line 128: Line 169:
  
 
* 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
* Typo fixing patches
 
** (jlibosva, slaweq) There has been some patches coming from a certain group of people that just fix one typo in either a comment in code or documentation. e.g. https://review.openstack.org/#/c/540225/ . There has been already a ML thread started about this behavior in our community: http://lists.openstack.org/pipermail/openstack-dev/2017-September/122472.html Although typo fixes bring some value, they bring a very tiny value being sent one by one as that triggers CI systems and require two cores to approve such patch. This topic is to kick off the discussion about what approach should Neutron cores take.
 
* Use of existing tools to aid backporting bugfixes etc. to stable branches
 
** (aspiers) I have written a Python module [https://github.com/aspiers/git-deps git-deps] which can [https://github.com/aspiers/git-deps#use-case-1-porting-between-branches predict the complexity of porting tasks]
 
*** This could be wrapped in a non-voting check pipeline job to warn when complexity is above a certain threshold, and recommend that the backport be done now while the fix is fresh in the developer's head (or that the fix could be reworked to avoid potential conflicts during backport). Mentioned to mlavalle who suggested raising here. Worth discussing in [https://wiki.openstack.org/wiki/Meetings/NeutronCI Neutron CI meeting] as well / instead?
 
** (aspiers) I have written another (as yet unpublished) tool git-explode which wraps git-deps and allows decomposition of logically related changes into separate git branches; this could potentially be used to accelerate backporting.
 
** (aspiers) [https://blog.adamspiers.org/2013/10/02/more-uses-for-git-notes/ Unfinished / unused tools from a long time ago to aid with more complex backporting] - worth resurrecting?
 
  
 
== 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/2017/?C=M;O=D networking-2017]
 
** [http://eavesdrop.openstack.org/meetings/networking/2017/?C=M;O=D networking-2017]
 
** [http://eavesdrop.openstack.org/meetings/networking/2016/?C=M;O=D networking-2016]
 
** [http://eavesdrop.openstack.org/meetings/networking/2016/?C=M;O=D networking-2016]

Latest revision as of 12:26, 15 September 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

my report from two weeks ago: http://lists.openstack.org/pipermail/openstack-discuss/2020-September/017254.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
Aug-31-2020 Bernard Cafarelli (bcafarel)
Sep-7-2020 Slawek Kaplonski (slaweq)
Sep-14-2020 Hongbin Lu (hongbin)
Sep-21-2020 Brian Haley (haleyb)
Sep-28-2020 Lajos Katona (lajoskatona)
Oct-5-2020 Nate Johnston (njohnston)
Oct-12-2020 Akihiro Motoki (amotoki)
Oct-19-2020 Miguel Lavalle (mlavalle)
Oct-26-2020 Bence Romsics (rubasov)
Nov-2-2020 Rodolfo Alonso Hernandez (ralonsoh)
Nov-9-2020 Lucas Alvares Gomes (lucasgomes)
Nov-16-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

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):
    • (nick): Topic
      • More details

Previous meeting logs