Difference between revisions of "Network/Meetings"
(→Announcements / Reminders) |
(→Announcements / Reminders) |
||
| Line 4: | Line 4: | ||
=== Announcements / Reminders === | === Announcements / Reminders === | ||
| − | * Next milestone is Rocky-3, | + | * Next milestone is Rocky-3, THIS WEEK. We will freeze this coming Wednesday night! |
** Rocky release schedule: https://releases.openstack.org/rocky/schedule.html | ** Rocky release schedule: https://releases.openstack.org/rocky/schedule.html | ||
| − | * | + | * Please reach out to your friendly PTL if you want / need a FFE |
| − | |||
* PTG in Denver on September 10 -14: | * PTG in Denver on September 10 -14: | ||
** https://www.openstack.org/ptg/ | ** https://www.openstack.org/ptg/ | ||
Revision as of 20:25, 23 July 2018
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 Rocky-3, THIS WEEK. We will freeze this coming Wednesday night!
- Rocky release schedule: https://releases.openstack.org/rocky/schedule.html
- Please reach out to your friendly PTL if you want / need a FFE
- PTG in Denver on September 10 -14:
- https://www.openstack.org/ptg/
- Tickets $399 through August 23rd. $599 afterwards
- Rocky PTG summary: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128183.html
Blueprints
Rocky-2 blueprints: https://launchpad.net/neutron/+milestone/rocky-3
OVO/no downtime API
- OVO backlog control spreadsheet: https://docs.google.com/spreadsheets/d/1Mz7V40GSdcUH_aBoNWjsFaNRp4wf-duz1GFWligiNXc/edit#gid=1051788848
- Weekly meeting on Thursday at 1400UTC: http://eavesdrop.openstack.org/#Neutron_Upgrades_Meeting
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
- policy-in-code (Queens) -- amotoki
- wsgi support (Pike) -- annp
-
Enable mutable configuration (Rocky) https://governance.openstack.org/tc/goals/rocky/enable-mutable-configuration.html-- slaweq -
mox3 removal (Rocky) https://bugs.launchpad.net/python-neutronclient/+bug/1753504-- hongbin (neutronclient), amotoki (fwaas/vpnaas-dashboard), (perhaps) yamamoto (networking-midonet) - python3.5 fully support https://etherpad.openstack.org/p/py3-neutron-pike
- Thread on overall community plan to move to a Python 3 only world: http://lists.openstack.org/pipermail/openstack-dev/2018-April/129866.html
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
Bugs and Gate issues
Bug deputy report for week of July 9th: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132274.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-16-2018 | Pawel Suder (pasuder) |
| April-23-2018 | Hongbin Lu (hongbin) |
| April-30-2018 | Hirofumi Ichihara (hichihara) |
| May-7-2018 | Gary Kotton (garyk) |
| May-14-2018 | Akihiro Motoki (amotoki) |
| May-21-2018 | Boden Russel (boden) |
| May-28-2018 | Nate Johnston (njohnston) |
| June-4-2018 | Swaminathan Vasudevan (Swami) |
| June-11-2018 | Slawek Kaplonski (slaweq) |
| June-18-2018 | Brian Haley (haleyb) |
| June-25-2018 | Armando Migliaccio (armax) |
| July-2-2018 | Zhao Bo(bzhao) |
| July-9-2018 | Manjeet Bhatia (manjeets) |
| July-16-2018 | Lujin Luo(lujinluo) |
| July-23-2018 | YAMAMOTO Takashi (yamamoto) |
| July-30-2018 | Miguel Lavalle (mlavalle) |
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
Ryu support
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
List here any planned potential disruption that may be caused by a new neutron-lib release and adoption of its latest features.
DO NOT TOP POST - ADD PATCHES TO THE BOTTOM OF THE LIST
- Open issues: https://review.openstack.org/#/q/status:open+message:%22NeutronLibImpact%22
- In most cases all consumers using neutron/neutron-lib stable branches are updated as part of consumption. For those who "pin" neutron/neutron-lib, they will have to address the consumption as they move their "pin" up.
- To see all consumption patches for a lib impact change, view the topic branch of the corresponding lib impact change (or search using the same subject).
- Patches that need high-level input from neutron cores: https://review.openstack.org/#/q/message:%22NeutronCoreInputNeeded%22
- Past issues: https://review.openstack.org/#/q/status:merged+message:%22NeutronLibImpact%22
- 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
- <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):
Previous meeting logs
- Previous meetings, with their notes and logs, can be found here.
