Difference between revisions of "Network/Meetings"

Revision as of 21:09, 16 September 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

• Shanghai PTG planning etherpad
  • https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
• Shanghai PTG brainstorming etherpad
  • https://etherpad.openstack.org/p/Shanghai-Neutron-Planning
• Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html

Blueprints

Train-3 blueprints: https://launchpad.net/neutron/+milestone/train-rc1

Patches up for review:

• 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 - should this be targeted to rc-1?
• https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - spec is here: https://review.opendev.org/#/c/657170 and still not merged, this should be probably moved to Ussuri now,
• https://blueprints.launchpad.net/neutron/+spec/subnets-different-pools-same-net - Implemented :),
• 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/ - should we move it to Ussuri?
• https://blueprints.launchpad.net/neutron/+spec/improve-extraroute-api - patches https://review.opendev.org/#/q/topic:extraroute+(status:open+OR+status:merged) - looks for me that we are only missing https://review.opendev.org/#/c/670851/ in neutron, can we target it to RC-1 than?

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

• Run under Python 3 by default (njohnston)
  • https://governance.openstack.org/tc/goals/stein/python3-first.html
  • https://storyboard.openstack.org/#!/story/2003242
  • Etherpad https://etherpad.openstack.org/p/neutron_stadium_python3_status
    • According to etherpad we are still missing some small bits in networking-bagpipe and networking-odl and also networking-midonet is not transitioned,

• 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)
  • we are good on Neutron's side. Still some patches for stadium projects are needed:
    • https://review.opendev.org/#/c/673488/ - networking-ovn
    • https://review.opendev.org/#/c/673501/ - networking-odl
  • According to my email http://lists.openstack.org/pipermail/openstack-discuss/2019-July/008084.html we should also have similar jobs proposed for:
    • neutron-dynamic-routing - to confirm with tidwelr
    • networking-bagpipe - someone who knows bagpipe better should take a look, I will try to ask tmorin about that,
    • networking-midonet

• Enabling PDF generation support for project documentation (amotoki)
  • https://governance.openstack.org/tc/goals/train/pdf-doc-generation.html
  • https://storyboard.openstack.org/#!/story/2006099
  • Reviews: https://review.opendev.org/#/q/topic:build-pdf-docs+(status:open+OR+status:merged)+(project:%255Eopenstack/neutron.*+OR+project:%255Eopenstack/networking-.*)

Bugs and Gate issues

Bugs report for week of September 9th: http://lists.openstack.org/pipermail/openstack-discuss/2019-September/009361.html

More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI

• Confirmed gate failures
• Bugs that need attention
• All bug reports associated to deprecation issues
• Bugs Sheet
• 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

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:

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

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

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

• Released last week 1.29.1: https://review.opendev.org/#/c/679986/ - this is version for Train, and patch to use it in Neutron is https://review.opendev.org/#/c/680980/

HOUSE KEEPING

• Neutron-lib work items and volunteers are being tracked via etherpad: https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-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

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
• Updating projects for Zuul v3: https://review.openstack.org/#/q/status:open+topic:neutronlib-zuulv3

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
  • Topic proposals for the Shanghai forum (mlavalle)
    • Ideas under consideration:
      • Operator feedback
      • Feedback on the convergence with OVN
    • Etherpad: https://etherpad.openstack.org/p/neutron-shanghai-forum-brainstorming

Previous meeting logs

• Previous meetings, with their notes and logs, can be found here.
  • networking-2019
  • networking-2018
  • networking-2017
  • networking-2016
  • networking-2015
  • networking-2014
  • networking-2013
  • quantum-2013
  • quantum-2012