Difference between revisions of "Network/Meetings"
(→Announcements / Reminders) |
(→On Demand Agenda) |
||
Line 126: | Line 126: | ||
* Topic for the meeting (keep this template, please): | * Topic for the meeting (keep this template, please): | ||
+ | ** (njohnston): Cleaning old OVO compatibility code. | ||
+ | *** In [https://review.opendev.org/658155 change 658155], ralonsoh proposed removing old OVO compatibility code for QOS objects. The OVO compatibility code is meant to facilitate rolling upgrades so that a server can communicate with an agent when the version difference is 1-off. Therefore there should not be any need to keep code beyond 2 cycles after the object version change; all of the changes ralonsoh proposed changing were >1 year old. I think this is useful housecleaning and I wanted to suggest to the community that we undertake such cleaning more broadly. See the discussion [https://review.opendev.org/#/c/658155/2/neutron/objects/qos/policy.py here]. | ||
** (your nickname): brief description. | ** (your nickname): brief description. | ||
*** More details | *** More details |
Revision as of 16:25, 17 May 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.
Contents
Announcements / Reminders
- Next milestone is Train-1
- Open Infrastructure Summit CFP Open - Deadline: July 2
- Photos from recent Denver PTG:
- Stein PTG summary: http://lists.openstack.org/pipermail/openstack-dev/2018-September/135032.html
Blueprints
Train-1 blueprints: https://launchpad.net/neutron/+milestone/train-1
Patches up for review:
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)
Starter Approved RFEs
This section is for advertising approved RFEs that the Neutron Drivers team have deemed suitable for new contributors:
- Create a vlan transparent network in mixed driver environment: https://bugs.launchpad.net/neutron/+bug/1745192
- [RFE] subnet pool can not delete prefixes https://bugs.launchpad.net/neutron/+bug/1792901
Bugs and Gate issues
Bug deputy report for week of may 6th: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006176.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:
Date | who |
---|---|
April-1-2019 | Bernard Cafarelli (bcafarel) |
April-8-2019 | Slawek Kaplonski (slaweq) |
April-15-2019 | Hongbin Lu (hongbin) |
April-22-2019 | Boden Russel (boden) |
April-29-2019 | Nate Johnston (njohnston) |
May-6-2019 | Lajos Katona (lajoskatona) |
May-13-2019 | Ryan Tidwell (tidwellr) |
May-20-2019 | Swaminathan Vasudevan (Swami) |
May-27-2019 | Akihiro Motoki (amotoki) |
June-3-2019 | Brian Haley (haleyb) |
June-10-2019 | Manjeet Bhatia (manjeets) |
June-17-2019 | YAMAMOTO Takashi (yamamoto) |
June-24-2019 | Miguel Lavalle (mlavalle) |
July-1-2019 | Bence Romsics (rubasov) |
July-8-2019 | Vikram Choudhary (vikram) |
July-15-2019 | Gabriele Cerami (panda) (tentative) |
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
os-ken
- Progress report for week of October 29th: http://lists.openstack.org/pipermail/openstack-dev/2018-November/136329.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
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):
- (njohnston): Cleaning old OVO compatibility code.
- In change 658155, ralonsoh proposed removing old OVO compatibility code for QOS objects. The OVO compatibility code is meant to facilitate rolling upgrades so that a server can communicate with an agent when the version difference is 1-off. Therefore there should not be any need to keep code beyond 2 cycles after the object version change; all of the changes ralonsoh proposed changing were >1 year old. I think this is useful housecleaning and I wanted to suggest to the community that we undertake such cleaning more broadly. See the discussion here.
- (your nickname): brief description.
- More details
- (njohnston): Cleaning old OVO compatibility code.
Previous meeting logs
- Previous meetings, with their notes and logs, can be found here.