Difference between revisions of "Network/Meetings"
(→Bug deputy) |
(→Bug deputy) |
||
Line 83: | Line 83: | ||
|- | |- | ||
| January-8-2018 || Akihiro Motoki (amotoki) | | January-8-2018 || Akihiro Motoki (amotoki) | ||
+ | |- | ||
+ | | January-15-2018 || Hirofumi Ichihara (hichihara) | ||
|} | |} | ||
Revision as of 22:09, 2 October 2017
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
- PTG Summary Email - http://lists.openstack.org/pipermail/openstack-dev/2017-February/113032.html
- Pike specs open - https://review.openstack.org/#/c/429855/
- Stadium Ocata Post mortem - https://review.openstack.org/#/c/425990/
- Ocata postmortem - https://review.openstack.org/#/c/425990/
- <add announcement here>
Blueprints
Current milestone: https://launchpad.net/neutron/+milestone/pike-1
OVO/no API downtime
List here patches/topics that need core reviewer attention.
- add your patch here
Bugs and Gate issues
A full hour is dedicated to this topic, and more during the following meeting:
Approximate stats for the current cycle:
- From the beginning of Ocata (Sept-16-2016):
- Total reports: 415
- Fix released: 135
- Unassigned: 135
- New: 27
- Incomplete: 15
- Confirmed: 24
- Triaged: 4
- Total reports: 415
- 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 |
---|---|
October-2-2017 | Miguel Lavalle (mlavalle) |
October-9-2017 | Jakub Libosvar (jlibosva) |
October-16-2017 | Boden Russel (boden) |
October-23-2017 | James Anziano (janzian) |
October-30-2017 | Ihar Hrachyshka (ihrachys) |
November-6-2017 | Slawek Kaplonski (slaweq) |
November-13-2017 | Brian Haley (haleyb) |
November-20-2017 | Zhao Bo(bzhao) |
November-27-2017 | Armando Migliaccio (armax) |
December-4-2017 | Swaminathan Vasudevan (Swami) |
December-11-2017 | David Shaughnessy (davidsha) |
December-18-2017 | Rodolfo Alonso (ralonsoh) |
December-25-2017 | Lujin Luo(lujinluo) |
January-1-2018 | YAMAMOTO Takashi (yamamoto) |
January-8-2018 | Akihiro Motoki (amotoki) |
January-15-2018 | Hirofumi Ichihara (hichihara) |
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
Transition to OSC
Status of changes to deliver OSC
- 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
List here any planned potential disruption that may be caused by a new neutron-lib release and adoption of its latest features.
FRIENDLY REMINDER: Neutron/driver cores please try to make a pass through the curated neutron rehoming patches.
DO NOT TOP POST - ADD PATCHES TO THE BOTTOM OF THE LIST
- 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
- Open issues: https://review.openstack.org/#/q/status:open+message:%22NeutronLibImpact%22
- Past issues: https://review.openstack.org/#/q/status:merged+message:%22NeutronLibImpact%22
- <Highlight patch(es) here for discussion>
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
- (your nickname): brief description.
Previous meeting logs
- Previous meetings, with their notes and logs, can be found here.
- Older meeting notes are here: ../MeetingLogs.