Network/Meetings
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
- Release countdown for week R-0 - http://lists.openstack.org/pipermail/openstack-dev/2016-September/104809.html
- Design summit planning - http://lists.openstack.org/pipermail/openstack-dev/2016-September/104668.html
- Newton Postmortem - https://review.openstack.org/#/c/360207/
- Release liaison position open
Blueprints
Current milestone: https://launchpad.net/neutron/+milestone/ocata-1
Bugs and Gate failures
Approximate stats for the current cycle:
- From the beginning of Ocata (Sept-16-2016):
- Total reports: 87
- Fix released: 25
- Unassigned: 30
- New: 6
- Incomplete: 7
- Confirmed: 8
- Triaged: 0
- Total reports: 87
- Confirmed gate failures
- Bugs that need attention
- All bug reports associated to deprecation issues
- Bugs Sheet
- Grafana dashboards
Bug deputy
Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.
Previous deputies in order per week: iharchys, regXboi, markmcclain, armax, mestery, mangelajo, garyk, rosella_s, dougwig, HenryG, carl_baldwin, amotoki, kevinbenton, amuller, Zzelle, mlavalle, njohnston, mhickey, rosella_s, dasm, scheuran, HenryG, Amotoki, reedip, blogan, dougwig, armax, regXboi, haleyb, hichihara, carl_baldwin
Next weeks:
Date | who |
---|---|
May-30-2016 | kevinbenton |
Jun-6-2016 | mangelajo |
Jun-13-2016 | dasm |
Jun-20-2016 | john-davidge |
Jun-27-2016 | rossella_s |
Jul-4-2016 | johndperkins |
Jul-11-2016 | blogan |
Jul-18-2016 | mlavalle |
Jul-25-2016 | jlibosva |
Aug-01-2016 | electrocucaracha |
Aug-08-2016 | njohnston |
Aug-15-2016 | armax |
Aug-30-2016 | haleyb |
Sep-04-2016 | jschwarz |
Sep-12-2016 | hichihara |
Sep-19-2016 | ihrachys |
Sep-26-2016 | ihrachys |
Oct-3-2016 | dougwig |
Docs
- The future of OpenStack documentation - http://lists.openstack.org/pipermail/openstack-dev/2016-July/099012.html
Transition to OSC
Status of changes to deliver OSC
Neutron-lib
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:
- Feature Classification Framework/Matrix
- ankur-gupta-f: The feature classification matrix will provide information about plugins and the features they support.
- RFE has been approved. Need to improve Neutron documentation about various backends and the feature they support: https://review.openstack.org/#/c/318192/ https://review.openstack.org/#/c/324048/
- ihrachys: adding stable deputy role to arrange sustain proactive backports process:
- a new process to handle stable backports proposed: http://lists.openstack.org/pipermail/openstack-dev/2016-June/098552.html
- ankur-gupta-f: The feature classification matrix will provide information about plugins and the features they support.
- Let operator update subnet.cidr:
- yottatsa: as an operator I want to expand or shrink Public network without re-allocating all Floating IPs.
- Although I don't see any reason to abandon it, there are many roadblocks like "unexpected side effects on plugins that do not handle well the CIDR update" on the way. RFE https://bugs.launchpad.net/neutron/+bug/1605343
- yottatsa: as an operator I want to expand or shrink Public network without re-allocating all Floating IPs.
- Transaction guards on *_port methods, and l3 service plugins.
- oanson: create_port, update_port, and delete_port have a transaction guard which breaks existing l3 service plugins. There is a workaround (GUARD_TRANSACTION=false), but what is the long-term solution?
- I understand that GUARD_TRANSACTION=false is a workaround. What would be the correct solution to continue using port modification functions on the core plugin in case of transactions in the service plugin code, or how to correct the client code? I ran into this in Dragonflow, but I have seen it in Midonet as well. Neutron change: https://review.openstack.org/#/c/275110/ , Dragonflow change: https://review.openstack.org/#/c/355736/ .
- oanson: create_port, update_port, and delete_port have a transaction guard which breaks existing l3 service plugins. There is a workaround (GUARD_TRANSACTION=false), but what is the long-term solution?
- Distributed gateway for optimized local SNAT
- ishafran: There is a blueprint describing new feature: https://blueprints.launchpad.net/neutron/+spec/neutron-local-snat
- I would like to understand the reasons the blueprint marked obsolete. Is there a developed / in development patch that solves the subject ?
- ishafran: There is a blueprint describing new feature: https://blueprints.launchpad.net/neutron/+spec/neutron-local-snat
- Recompiling a Cirros fork at the gate
- jschwarz: Basically, getting Cirros to support stuff that we need to test is going no where, so instead we propose forking Cirros and adding support for what we need on our own.
- https://etherpad.openstack.org/p/cirros-respin . This has gotten support from at least 2 cores already (ajo, kevinbenton)
- jschwarz: Basically, getting Cirros to support stuff that we need to test is going no where, so instead we propose forking Cirros and adding support for what we need on our own.
- 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.