Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(On Demand Agenda)
(Bugs and Gate issues)
 
(395 intermediate revisions by 17 users not shown)
Line 4: Line 4:
 
=== Announcements / Reminders ===
 
=== Announcements / Reminders ===
  
* Released Rocky-2 last week:
+
* We released Ussuri version! Congrats everyone!
** Neutron: https://review.openstack.org/#/c/572666/
+
** https://releases.openstack.org/ussuri/
** python-neutronclient: https://review.openstack.org/#/c/573681/
+
* we are now in the Victoria cycle already https://releases.openstack.org/victoria/schedule.html
** neutron-lib: https://review.openstack.org/#/c/573826/
+
** Victoria-1 milestone is in the week of Jun 15th - in 4 weeks
* Next milestone is Rocky-3, July 23 - 27
+
* Victoria PTG
** Rocky release schedule: https://releases.openstack.org/rocky/schedule.html
+
** In 2 weeks
* Rocky PTG summary: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128183.html
+
** 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)
  
 
=== Blueprints ===
 
=== Blueprints ===
  
Rocky-2 blueprints: https://launchpad.net/neutron/+milestone/rocky-2
 
  
==== OVO/no downtime API ====
+
Blueprints which we should include in Victoria milestones:
 
+
* Blueprints for Victoria-1: https://launchpad.net/neutron/+milestone/victoria-1
* OVO backlog control spreadsheet: https://docs.google.com/spreadsheets/d/1Mz7V40GSdcUH_aBoNWjsFaNRp4wf-duz1GFWligiNXc/edit#gid=1051788848
+
** https://blueprints.launchpad.net/neutron/+spec/dns-records-in-neutron - mlavalle, can You be approver of this one?
* Weekly meeting on Thursday at 1400UTC: http://eavesdrop.openstack.org/#Neutron_Upgrades_Meeting
+
*** spec is now proposed https://review.opendev.org/#/c/726904/ - we need to review it
 +
** https://blueprints.launchpad.net/neutron/+spec/sg-sharing-as-readonly - amotoki, can You be approver of this one?
 +
*** rm_work - can You be assigned to this one?
  
 
=== Community Goals ===
 
=== Community Goals ===
Line 26: Line 32:
 
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
+
* Migrate to zuulv3
* wsgi support (Pike) -- annp
+
** Etherpad: https://etherpad.openstack.org/p/neutron-train-zuulv3-py27drop
* <s>Enable mutable configuration (Rocky) https://governance.openstack.org/tc/goals/rocky/enable-mutable-configuration.html</s> -- slaweq
 
* <s>mox3 removal (Rocky) https://bugs.launchpad.net/python-neutronclient/+bug/1753504</s> -- hongbin (neutronclient), amotoki (fwaas/vpnaas-dashboard), (perhaps) yamamoto (networking-midonet)
 
* python3.5 fully support https://etherpad.openstack.org/p/py3-neutron-pike
 
** Thread on overall community plan to move to a Python 3 only world: http://lists.openstack.org/pipermail/openstack-dev/2018-April/129866.html
 
  
=== 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 ===
  
* Create a vlan transparent network in mixed driver environment: https://bugs.launchpad.net/neutron/+bug/1745192
+
rubasov was bug deputy; Report http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014913.html
  
=== Bugs and Gate issues ===
+
Some bugs needs volunteers:
 +
* https://bugs.launchpad.net/neutron/+bug/1877977 - do we really need veth interconnection still?
 +
* https://bugs.launchpad.net/neutron/+bug/1878299 - needs L3 subteam attention probably,
  
Bug deputy report for week of June 4th: http://lists.openstack.org/pipermail/openstack-dev/2018-June/131372.html
+
More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI
  
A full hour is dedicated to this topic, and more during the following meeting:
 
 
* 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 56: 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;"
 
|-
 
|-
! Date !! who  
+
! Date !! who !! note
 
|-
 
|-
| April-16-2018 || Pawel Suder (pasuder)
+
| March-9-2020 || Bernard Cafarelli (bcafarel) ||
 
|-
 
|-
| April-23-2018 || Hongbin Lu (hongbin)
+
| March-16-2020 || Slawek Kaplonski (slaweq) ||
 
|-
 
|-
| April-30-2018 || Hirofumi Ichihara (hichihara)
+
| March-23-2020 || Hongbin Lu (hongbin) ||
 
|-
 
|-
| May-7-2018 || Gary Kotton (garyk)
+
| March-30-2020 || Brian Haley (haleyb) ||
 
|-
 
|-
| May-14-2018 || Akihiro Motoki (amotoki)
+
| April-6-2020 || Lajos Katona (lajoskatona) ||
 
|-
 
|-
| May-21-2018 || Boden Russel (boden)
+
| April-13-2020 || Ryan Tidwell (tidwellr) ||
 
|-
 
|-
| May-28-2018 || James Anziano (janzian)
+
| April-20-2020 || Nate Johnston (njohnston) ||
 
|-
 
|-
| June-4-2018 || Manjeet  Bhatia (manjeets)
+
| April-27-2020 || Akihiro Motoki (amotoki) ||
 
|-
 
|-
| June-11-2018 || Slawek Kaplonski (slaweq)
+
| May-4-2020 || Miguel Lavalle (mlavalle) ||
 
|-
 
|-
| June-18-2018 || Brian Haley (haleyb)
+
| May-11-2020 || Bence Romsics (rubasov) ||
 
|-
 
|-
| June-25-2018 || Armando Migliaccio (armax)
+
| May-18-2020 || Maciej Jozefczyk (maciejjozefczyk) ||
 
|-
 
|-
| July-2-2018 || Zhao Bo(bzhao)
+
| May-25-2020 || Rodolfo Alonso Hernandez (ralonsoh) ||
 
|-
 
|-
| July-9-2018 || Swaminathan Vasudevan (Swami)
+
| June-1-2020 || Lucas Alvares Gomes (lucasgomes) ||
 
|-
 
|-
| July-16-2018 || Lujin Luo(lujinluo)
+
| June-8-2020 || Jakub Libosvar (jlibosva) ||
|-
 
| July-23-2018 || YAMAMOTO Takashi (yamamoto)
 
|-
 
| July-30-2018 || Miguel Lavalle (mlavalle)
 
 
|}
 
|}
  
 
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 113: Line 118:
 
=== 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 132: Line 132:
  
 
* Topic for the meeting (keep this template, please):
 
* Topic for the meeting (keep this template, please):
 +
** (nick): Topic
 +
*** More details
 +
** 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/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 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