Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Announcements / Reminders)
(Blueprints)
Line 17: Line 17:
 
* Blueprints for Ussuri-3: https://launchpad.net/neutron/+milestone/ussuri-3
 
* Blueprints for Ussuri-3: https://launchpad.net/neutron/+milestone/ussuri-3
 
** https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge - Convergence of ML2+OVS+DVR and OVN
 
** https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge - Convergence of ML2+OVS+DVR and OVN
 +
*** what we are still missing to consider it as done?
 
** https://blueprints.launchpad.net/neutron/+spec/tagging-on-post - almost done, only SDK/OSC part is todo
 
** https://blueprints.launchpad.net/neutron/+spec/tagging-on-post - almost done, only SDK/OSC part is todo
 +
*** mlavalle - will You take care of SDK/OSC part?
 
** https://bugs.launchpad.net/neutron/+bug/1841067 - [RFE] SR-IOV agent depends on mac addresses for getting bound ports
 
** https://bugs.launchpad.net/neutron/+bug/1841067 - [RFE] SR-IOV agent depends on mac addresses for getting bound ports
 +
*** according to last comment, it will not be done in this cycle
 
** https://blueprints.launchpad.net/neutron/+spec/fip-pf-description - almost done, only SDK and OSC part left todo
 
** https://blueprints.launchpad.net/neutron/+spec/fip-pf-description - almost done, only SDK and OSC part left todo
 +
*** I recently found some issues with that, see https://bugs.launchpad.net/neutron/+bug/1866560
 
** https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes
 
** https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes
 +
*** is there maybe help with that one needed?
 
** 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/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/
 +
*** I think that we need some new volunteers to work on this
 
** https://blueprints.launchpad.net/neutron/+spec/metadata-over-ipv6
 
** https://blueprints.launchpad.net/neutron/+spec/metadata-over-ipv6
** https://blueprints.launchpad.net/neutron/+spec/rbac-address-scope-and-subnet-pools - we need approver for that one
+
*** I asked recently haleyb about his opinion about this and it seems that we should go with this on our own now, mlavalle, rubasov - do You have any plan for it?
 +
** https://blueprints.launchpad.net/neutron/+spec/rbac-address-scope-and-subnet-pools
 +
*** waiting for new neutron-lib release now
 
* Removed target milestone:
 
* Removed target milestone:
 
** https://blueprints.launchpad.net/neutron/+spec/evacuate-agent-resources
 
** https://blueprints.launchpad.net/neutron/+spec/evacuate-agent-resources

Revision as of 10:19, 10 March 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 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

Yamamoto was on bug deputy. Summary http://lists.openstack.org/pipermail/openstack-discuss/2020-March/012926.html

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
December-23-2019 Bernard Cafarelli (bcafarel) switched with Miguel Lavalle (mlavalle)
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 Nate Johnston (njohnston)
February-10-2020 Akihiro Motoki (amotoki)
Fabruary-17-2020 Miguel Lavalle (mlavalle) switched with Bernard Cafarelli (bcafarel)
February-24-2020 YAMAMOTO Takashi (yamamoto)
March-2-2020 Bence Romsics (rubasov)

New round schedule

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 YAMAMOTO Takashi (yamamoto)
May-18-2020 Bence Romsics (rubasov)
May-25-2020 Maciej Jozefczyk (maciejjozefczyk)
June-1-2020 Rodolfo Alonso Hernandez (ralonsoh)
June-8-2020 Lucas Alvares Gomes (lucasgomes)
June-15-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)

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

I want to release new version when https://review.opendev.org/#/c/705998/ will be merged to allow work on neutron's side using this api extension. Any other patches which You want to include in this new release?

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:

Previous meeting logs