Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(On Demand Agenda)
(Neutron-lib, planned refactoring and other impacts)
 
(802 intermediate revisions by 60 users not shown)
Line 1: Line 1:
  
{{:Network/Header}}
+
The OpenStack Networking Team ([[Neutron]]) holds public meetings as advertised on [http://eavesdrop.openstack.org/#Neutron_Team_Meeting OpenStack IRC Meetings Calendar]. If you are unable to attend, please check the most recent [http://eavesdrop.openstack.org/meetings/networking/ logs.]
'''Meeting time: The OpenStack Networking Team ([[Neutron]]) holds public meetings alternating between Mondays at 2100 UTC (#openstack-meeting) and Tuesdays at 1400 UTC (#openstack-meeting). Everyone is encouraged to attend.'''
 
  
== Apologies for Absence ==
+
=== Announcements / Reminders ===
 +
 
 +
* Still looking for "new daddies" for
 +
** neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html
 +
** neutron-vpnaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010931.html
 +
* Removing of neutron-interconnection from stadium project is almost done: https://review.opendev.org/#/q/branch:master+topic:neutron-interconnection-retire,
 +
** We are waiting for last patch https://review.opendev.org/#/c/694480/ to be merged,
 +
* We started process of moving networking-ovn code into neutron tree
 +
** BP: https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge
 +
** Patches: https://review.opendev.org/#/q/topic:bp/neutron-ovn-merge
 +
* Next week is Ussuri-1 milestone: https://releases.openstack.org/ussuri/schedule.html
 +
* I proposed patch to add review priority also to stadium projects: https://review.opendev.org/#/c/696628/
 +
* 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 which we should include in Ussuri milestones:
 +
* Blueprints for Ussuri-1: https://launchpad.net/neutron/+milestone/ussuri-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/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes
 +
* https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge - Convergence of ML2+OVS+DVR and OVN
 +
* 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/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/
 +
* https://blueprints.launchpad.net/neutron/+spec/metadata-over-ipv6
 +
* https://blueprints.launchpad.net/neutron/+spec/tagging-on-post
 +
* https://blueprints.launchpad.net/neutron/+spec/evacuate-agent-resources
 +
* https://bugs.launchpad.net/neutron/+bug/1841067 - [RFE] SR-IOV agent depends on mac addresses for getting bound ports
 +
* https://blueprints.launchpad.net/neutron/+spec/fip-pf-description
 +
* https://blueprints.launchpad.net/neutron/+spec/default-dns-zone-per-tenant
 +
 
 +
=== 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
 +
 
 +
* 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-.*)
 +
*** 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,
 +
 
 +
* Drop Python 2.7 Support (njohnston)
 +
** https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
 +
 
 +
* Project Specific PTL and Contributor Documentation
 +
** Proposal not merged yet: https://review.opendev.org/#/c/691737/
 +
 
 +
=== Bugs and Gate issues ===
 +
 
 +
njohnston was bug deputy last week. I don't see any report from him yet.
 +
 
 +
More discussion on this topic takes place during the Neutron CI 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.tag=needs-attention Bugs that need attention]
 +
* [https://bugs.launchpad.net/neutron/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=OPINION&field.status%3Alist=INVALID&field.status%3Alist=WONTFIX&field.status%3Alist=EXPIRED&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.tag=deprecation All bug reports associated to deprecation issues]
 +
* [https://goo.gl/KtEwbL Bugs Sheet]
 +
* [http://grafana.openstack.org/dashboard/db/neutron-failure-rate Grafana dashboards]
 +
 
 +
==== 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
  
== Agenda for Next Neutron Team Meeting ==
+
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:
'''Monday (8/17/2015) at 2100 UTC on #openstack-meeting'''
 
  
=== Announcements / Reminders ===
+
{| class="wikitable" style="text-align: center;"
* Liberty-3
+
|-
** 2 weeks out
+
! Date !! who !! note
** https://wiki.openstack.org/wiki/Liberty_Release_Schedule
+
|-
** FF is also that week
+
| September-30-2019 || Bernard Cafarelli (bcafarel) ||
* Liberty Release Notes
+
|-
** https://wiki.openstack.org/wiki/ReleaseNotes/Liberty#OpenStack_Liberty_Release_Notes
+
| October-7-2019 || Slawek Kaplonski (slaweq) ||
* Neutron Policies are documented here:
+
|-
** http://git.openstack.org/cgit/openstack/neutron/tree/doc/source/policies
+
| October-14-2019 || Hongbin Lu (hongbin) ||
 +
|-
 +
| October-21-2019 || Brian Haley (haleyb)  ||
 +
|-
 +
| October-28-2019 || Lajos Katona (lajoskatona) ||
 +
|-
 +
| November-4-2019 || Ryan Tidwell (tidwellr)  ||
 +
|-
 +
| November-11-2019 || Swaminathan Vasudevan (Swami) ||
 +
|-
 +
| November-18-2019 || Akihiro Motoki (amotoki)  || switched with Miguel Lavalle (mlavalle)
 +
|-
 +
| November-25-2019 || Nate Johnston (njohnston) ||
 +
|-
 +
| December-2-2019 || Miguel Lavalle (mlavalle) || switched with Akihiro Motoki (amotoki)
 +
|-
 +
| December-9-2019 || YAMAMOTO Takashi (yamamoto) ||
 +
|-
 +
| December-16-2019 || Bence Romsics (rubasov) ||
 +
|}
 +
 
 +
Next bug deputy round
 +
{| class="wikitable" style="text-align: center;"
 +
|-
 +
! Date !! who !! note
 +
|-
 +
| December-23-2019 || Bernard Cafarelli (bcafarel) ||
 +
|-
 +
| December-30-2019 || Slawek Kaplonski (slaweq) ||
 +
|-
 +
| January-6-2020 || Hongbin Lu (hongbin) ||
 +
|-
 +
| Januaryu-13-2020 || Brian Haley (haleyb)  ||
 +
|-
 +
| January-20-2020 || Lajos Katona (lajoskatona) ||
 +
|-
 +
| January-27-2020 || Ryan Tidwell (tidwellr)  ||
 +
|-
 +
| February-3-2020 || Swaminathan Vasudevan (Swami) ||
 +
|-
 +
| February-10-2020 || Akihiro Motoki (amotoki)  ||
 +
|-
 +
| February-17-2020 || Nate Johnston (njohnston) ||
 +
|-
 +
| Fabruary-24-2020 || Miguel Lavalle (mlavalle) ||
 +
|-
 +
| March-2-2020 || YAMAMOTO Takashi (yamamoto) ||
 +
|-
 +
| March-9-2020 || 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
 +
 
 +
=== Neutron performance subteam (Monday meetings) ===
 +
 
 +
=== Networking OVN and ML2+OVS+DVR Convergence (Tuesday meetings) ===
 +
 
 +
Merge OVN into Neutron tree:
 +
* Blueprint: https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge
 +
* Proposed rehome plan: https://ethercalc.openstack.org/networking-ovn-migration
 +
* Planning Etherpad https://etherpad.openstack.org/p/neutron-networking-ovn-merge
 +
* Spec: https://review.opendev.org/#/c/658414/
 +
 
 +
=== Docs ===
 +
 
 +
* 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
  
=== Bugs ===
+
=== CLI/SDK ===
  
<br>
+
SDK migration of neutronclient python bindings
Important bugs:
+
https://etherpad.openstack.org/p/neutron-openstacksdk-migration
** [https://bugs.launchpad.net/neutron/+bug/1404743] sporadic test failures due to VMs not getting a DHCP lease
 
** [https://bugs.launchpad.net/neutron/+bug/1477192] neutron test_multi_prefix_slaac failing in the gate with ping failures starting around 7/22
 
** [https://bugs.launchpad.net/neutron/+bug/1461172] neutron.tests.functional.agent.test_l3_agent.MetadataL3AgentTestCase.test_access_to_metadata_proxy times out intermittently
 
** [https://bugs.launchpad.net/neutron/+bug/1439696] Referencing a lb-healthmonitor ID for the first time from Heat would fail
 
** [https://bugs.launchpad.net/neutron/+bug/1378732] migrate_to_ml2 script doesn't work for Juno release
 
** [https://bugs.launchpad.net/neutron/+bug/1163569] security groups don't work with vip and ovs plugin
 
  
* Two bugs are hurting the functional job in the gate:
+
Status of changes to deliver OSC (this needs to be revisit)
** [https://bugs.launchpad.net/neutron/+bug/1461172] agent.test_l3_agent.MetadataL3AgentTestCase.test_access_to_metadata_proxy times out intermittently
+
* https://etherpad.openstack.org/p/osc-transition-priorities
** [https://bugs.launchpad.net/neutron/+bug/1466663] radvd exits -1 intermittently in test_ha_router_process_ipv6_subnets_to_existing_port
+
* http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html
  
* Linuxbridge Gate Parity Bugs
+
=== Neutron-lib, planned refactoring and other impacts ===
** [https://bugs.launchpad.net/neutron/+bug/1312016] nova libvirtError: Unable to add bridge brqxxx-xx port tapxxx-xx: Device or resource busy
 
<br/>
 
  
=== Docs (emagana)===
+
Releasing new version after merging:
 +
* https://review.opendev.org/#/c/695205/
 +
* https://review.opendev.org/#/c/692580/
 +
* https://review.opendev.org/#/c/696308/
 +
* https://review.opendev.org/#/c/696070/ - merged
  
==== Open Items for Liberty: (reviews needed) ====
+
HOUSE KEEPING
* L3 Ha - Clean up: https://review.openstack.org/#/c/196890/
+
* Neutron-lib work items and volunteers are being tracked via etherpad: https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list
* IPv6: https://review.openstack.org/#/c/181049/
+
* For a list of "current" consumers who receive neutron-lib updates and consumption patches, see: http://codesearch.openstack.org/?q=neutron-lib-current
* IPv6 Prefix: https://review.openstack.org/#/c/178739
+
* For a complete list of neutron-lib consumption patches that may impact consumers see: https://review.openstack.org/#/q/message:%22NeutronLibImpact%22
* OVS Update: https://review.openstack.org/#/c/196856/  (merged)
 
* Namespaces: https://review.openstack.org/#/c/196541/ (needs discussion)
 
* Debugging Section: https://review.openstack.org/#/c/178000/ (merged)
 
* https://review.openstack.org/#/q/status:open+project:openstack/openstack-manuals,n,z
 
  
==== Networking Guide ====
+
PATCHES THAT NEED REVIEWS
* Etherpad: https://etherpad.openstack.org/p/networking-guide
+
* Decouple DB workstream/blueprint: https://review.openstack.org/#/q/status:open+topic:bp/neutronlib-decouple-db+label:Workflow%253D0
* ToC: https://wiki.openstack.org/wiki/NetworkingGuide/TOC
+
* Callback payload workstream: https://review.openstack.org/#/q/status:open+topic:use-callback-payloads+label:Workflow%253D0
* Gerrit: https://github.com/openstack/openstack-manuals/tree/master/doc/networking-guide
+
* Updating projects for Zuul v3: https://review.openstack.org/#/q/status:open+topic:neutronlib-zuulv3
  
 
=== On Demand Agenda ===
 
=== On Demand Agenda ===
* Vendor decomposition
+
 
** Which vendors have not started final decomposition?
+
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:
*** Should we maintain a list of stragglers in devref until they are all done?
+
 
*** Send an email notice about decomposition to -dev: what should it say?
+
* Topic for the meeting (keep this template, please):
** Does anything need to be left in the tree for packaging?
+
** (your nickname): brief description.
*** Currently requirements.txt is left in the vendor dir with the name of the vendor package, but no one seems to know if it is needed.
+
*** More details
* Stable branches for networking subproject
 
** Discussion on this happened in July, decision which wasn't clear was here:
 
*** http://lists.openstack.org/pipermail/openstack-dev/2015-July/068785.html
 
** Currently, gerrit ACLs allow only neutron-stable-maint to merge stable patches here
 
** Stable has meaning, and we have to follow rules of stable backports
 
** Question: What does the team want here?
 
* Neutron interactions with infra
 
** Coordinate through dougwig and mestery
 
** We need to stop adding infra load into #openstack-infra
 
* 3rd party Ci systems: Can they vote -1?
 
** https://review.openstack.org/207198
 
* Liberty-3 BPs and reviews
 
** https://launchpad.net/neutron/+milestone/liberty-3
 
** Focus here for the remaining weeks
 
** Handy dandy gerrit dashboard link: https://goo.gl/x9bO7i
 
** We need to merge all of this for Liberty (or make our best shot)
 
** Email to openstack-dev ML on this topic: http://lists.openstack.org/pipermail/openstack-dev/2015-August/071786.html
 
* Concrete plan to merge back pecan and QoS work
 
** Need to do this very early after Liberty-2 is cut this week
 
* nova-network compatibility tasks
 
** Summit session(s) in Vancouver were very productive
 
** Tasks tracked here: https://etherpad.openstack.org/p/YVR-nova-network
 
** Need to find owners for a few of these
 
*** Rolling upgrades (mostly a grenade patch)
 
*** Distributed SNAT with DVR
 
*** "Get me a network (https://review.openstack.org/#/c/184857/) (kevinbenton to own this)
 
*** ARP Spoof patch series is stalled, need to make a decision on how to proceed. (kevinbenton will do this after beating requirements out of markmcclain)
 
* macvtap ml2 driver and agent - will land in neutron tree. Question is how to procede with agent code (scheuran)
 
** 1) Copy (duplicate) required agent code like in the past.
 
** 2) Extract a common base class for macvtap, linuxbridge and sriov-nic (impls are close to each other). Purpose: Sharing base agent code. Starting with macvtap only in liberty. Moving others to common base class in Mitaka. New agent base class cannot be used for OVS, as it already diverged too much from others.
 
*** Liberty: only methods that are obious common and only differ in details that can be abstracted (_setup_rpc, _report_state, _device_info_has_changes, _process_network_devices)
 
*** Mitaka: Methods that have a lot of common code, but require fruther thinking (treat_devices_added_updated, scan_devices, daemon_loop)
 
*** N: Having a common agent with interface drivers?
 
** Modular l2 agent (spec not in a good shape) and agent extension (is just for extending existing agents) is is not an option
 
  
 
== 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/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/2016/?C=M;O=D networking-2016]
 
** [http://eavesdrop.openstack.org/meetings/networking/2015/?C=M;O=D networking-2015]
 
** [http://eavesdrop.openstack.org/meetings/networking/2015/?C=M;O=D networking-2015]
 
** [http://eavesdrop.openstack.org/meetings/networking/2014/?C=M;O=D networking-2014]
 
** [http://eavesdrop.openstack.org/meetings/networking/2014/?C=M;O=D networking-2014]
Line 102: Line 191:
 
** [http://eavesdrop.openstack.org/meetings/quantum/2013/?C=M;O=D quantum-2013]
 
** [http://eavesdrop.openstack.org/meetings/quantum/2013/?C=M;O=D quantum-2013]
 
** [http://eavesdrop.openstack.org/meetings/quantum/2012/?C=M;O=D quantum-2012]
 
** [http://eavesdrop.openstack.org/meetings/quantum/2012/?C=M;O=D quantum-2012]
* Older meeting notes are here:  ../MeetingLogs.
 

Latest revision as of 12:03, 3 December 2019

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 Ussuri 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

njohnston was bug deputy last week. I don't see any report from him yet.

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 current scheduled rotation is the following:

Date who note
September-30-2019 Bernard Cafarelli (bcafarel)
October-7-2019 Slawek Kaplonski (slaweq)
October-14-2019 Hongbin Lu (hongbin)
October-21-2019 Brian Haley (haleyb)
October-28-2019 Lajos Katona (lajoskatona)
November-4-2019 Ryan Tidwell (tidwellr)
November-11-2019 Swaminathan Vasudevan (Swami)
November-18-2019 Akihiro Motoki (amotoki) switched with Miguel Lavalle (mlavalle)
November-25-2019 Nate Johnston (njohnston)
December-2-2019 Miguel Lavalle (mlavalle) switched with Akihiro Motoki (amotoki)
December-9-2019 YAMAMOTO Takashi (yamamoto)
December-16-2019 Bence Romsics (rubasov)

Next bug deputy round

Date who note
December-23-2019 Bernard Cafarelli (bcafarel)
December-30-2019 Slawek Kaplonski (slaweq)
January-6-2020 Hongbin Lu (hongbin)
Januaryu-13-2020 Brian Haley (haleyb)
January-20-2020 Lajos Katona (lajoskatona)
January-27-2020 Ryan Tidwell (tidwellr)
February-3-2020 Swaminathan Vasudevan (Swami)
February-10-2020 Akihiro Motoki (amotoki)
February-17-2020 Nate Johnston (njohnston)
Fabruary-24-2020 Miguel Lavalle (mlavalle)
March-2-2020 YAMAMOTO Takashi (yamamoto)
March-9-2020 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

Neutron performance subteam (Monday meetings)

Networking OVN and ML2+OVS+DVR Convergence (Tuesday meetings)

Merge OVN into Neutron tree:

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

Releasing new version after merging:

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):
    • (your nickname): brief description.
      • More details

Previous meeting logs