Difference between revisions of "Network/Meetings"

Revision as of 21:04, 8 July 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.

https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/ - it's still not good but there is progress with it every week,
https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - any updates?
https://blueprints.launchpad.net/neutron/+spec/subnets-different-pools-same-net
https://blueprints.launchpad.net/neutron/+spec/neutron-classifier-neutron-qos
https://blueprints.launchpad.net/neutron/+spec/improve-extraroute-api

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)
- https://governance.openstack.org/tc/goals/stein/python3-first.html

Support IPv6-Only Deployments (slaweq)
- https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html

Enabling PDF generation support for project documentation (amotoki)
- https://governance.openstack.org/tc/goals/train/pdf-doc-generation.html
- Docs team requesting Neutron volunteer to help with this goal: http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007301.html

Bugs and Gate issues

Bugs report for week of July 1st: http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007577.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 current scheduled rotation is the following:

Date	who
July-1-2019	Bernard Cafarelli (bcafarel)
July-8-2019	Slawek Kaplonski (slaweq)
July-15-2019	Hongbin Lu (hongbin)
July-22-2019	Boden Russel (boden)
July-29-2019	Brian Haley (haleyb)
August-5-2019	Lajos Katona (lajoskatona)
August-12-2019	Ryan Tidwell (tidwellr)
August-19-2019	Swaminathan Vasudevan (Swami)
August-26-2019	Akihiro Motoki (amotoki)
September-2-2019	Nate Johnston (njohnston)
September-9-2019	Miguel Lavalle (mlavalle)
September-16-2019	YAMAMOTO Takashi (yamamoto)
September-23-2019	Bence Romsics (rubasov)

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

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

proposed release of 1.28: https://review.opendev.org/#/c/666870/

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):
- (your nickname): brief description.
  - More details

Previous meeting logs

Previous meetings, with their notes and logs, can be found here.

@@ Line 4: / Line 4: @@
 === Announcements / Reminders ===
-* Final week for RCs
+*  Next milestone is T-2, week of July 22 - 26
-** https://releases.openstack.org/stein/schedule.html
+** https://releases.openstack.org/train/schedule.html
-* Message sent to ML with planning etherpad for Train PTG
+* Train PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html
-** http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003895.html
-** https://etherpad.openstack.org/p/openstack-networking-train-ptg
-* Stein PTG summary: http://lists.openstack.org/pipermail/openstack-dev/2018-September/135032.html
 === Blueprints ===
-Stein-3 blueprints: https://launchpad.net/neutron/+milestone/stein-rc1
+Train-2 blueprints: https://launchpad.net/neutron/+milestone/train-2
 Patches up for review:
+* https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/ - it's still not good but there is progress with it every week,
+* https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - any updates?
+* https://blueprints.launchpad.net/neutron/+spec/subnets-different-pools-same-net
+* https://blueprints.launchpad.net/neutron/+spec/neutron-classifier-neutron-qos
+* https://blueprints.launchpad.net/neutron/+spec/improve-extraroute-api
 === Community Goals ===
@@ Line 25: / Line 27: @@
 ** https://governance.openstack.org/tc/goals/stein/python3-first.html
-=== Starter Approved RFEs ===
+* Support IPv6-Only Deployments (slaweq)
+** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
-This section is for advertising approved RFEs that the Neutron Drivers team have deemed suitable for new contributors:
+* Enabling PDF generation support for project documentation (amotoki)
+** https://governance.openstack.org/tc/goals/train/pdf-doc-generation.html
-* Create a vlan transparent network in mixed driver environment: https://bugs.launchpad.net/neutron/+bug/1745192
+** Docs team requesting Neutron volunteer to help with this goal: http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007301.html
-* [RFE] subnet pool can not delete prefixes https://bugs.launchpad.net/neutron/+bug/1792901
 === Bugs and Gate issues ===
-Bug deputy report for week of April 1st: http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004696.html
+Bugs report for week of July 1st: http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007577.html
 More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI
@@ Line 55: / Line 56: @@
 ! Date !! who
 |-
-| April-1-2019 || Bernard Cafarelli (bcafarel)
+| July-1-2019 || Bernard Cafarelli (bcafarel)
-|-
-| April-8-2019 || Slawek Kaplonski (slaweq)
 |-
-| April-15-2019 || Hongbin Lu (hongbin)
+| July-8-2019 || Slawek Kaplonski (slaweq)
 |-
-| April-22-2019 || Boden Russel (boden)
+| July-15-2019 || Hongbin Lu (hongbin)
 |-
-| April-29-2019 || Nate Johnston (njohnston)
+| July-22-2019 || Boden Russel (boden)
 |-
-| May-6-2019 || Lajos Katona (lajoskatona)
+| July-29-2019 || Brian Haley (haleyb)
 |-
-| May-13-2019 || Ryan Tidwell (tidwellr)
+| August-5-2019 || Lajos Katona (lajoskatona)
 |-
-| May-20-2019 || Swaminathan Vasudevan (Swami)
+| August-12-2019 || Ryan Tidwell (tidwellr)
 |-
-| May-27-2019 || Akihiro Motoki (amotoki)
+| August-19-2019 || Swaminathan Vasudevan (Swami)
 |-
-| June-3-2019 || Brian Haley (haleyb)
+| August-26-2019 || Akihiro Motoki (amotoki)
 |-
-| June-10-2019 || Manjeet  Bhatia (manjeets)
+| September-2-2019 || Nate Johnston (njohnston)
 |-
-| June-17-2019 || YAMAMOTO Takashi (yamamoto)
+| September-9-2019 || Miguel Lavalle (mlavalle)
 |-
-| June-24-2019 || Miguel Lavalle (mlavalle)
+| September-16-2019 || YAMAMOTO Takashi (yamamoto)
 |-
-| July-1-2019 || Bence Romsics (rubasov)
+| September-23-2019 || Bence Romsics (rubasov)
 |}
 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 ===
@@ Line 105: / Line 100: @@
 === Neutron-lib, planned refactoring and other impacts ===
+* proposed release of 1.28: https://review.opendev.org/#/c/666870/
 HOUSE KEEPING
@@ Line 123: / Line 120: @@
 ** (your nickname): brief description.
 *** More details
-* (mlavalle) The meaning of stable branch extended maintenance
-** I had a conversation with the releases time in part triggered by http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001383.html
-** A stable branch enters extended maintenance after 18 months of initial release. It is not up to the project team to decide that
-** The stable branch can stay in extended maintenance for as long as the project team is willing / able to maintain it
-** After that, it can go for up to six months as unmaintained, after which it reaches EOL. But the team can decide before that to EOL it
-** Status of Pike branch: http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004594.html
-* (bcafarel) Old Launchpad bugs status
-** Going through low-hanging-fruit bugs, I noticed most were quite old/stale. Checking overall opened bugs, a lot is in the same situation
-** Launchpad counted ~890 currently open bugs last Friday
-** Many bugs have not been updated for >2 years, some have been fixed but not moved to "Fix released", some were still open on neutron-lbaas (v1 for a few)
-** I started cleaning/closing a few, but that's a lot of manual process. Thoughts to get the open bugs list back in a shinier state?
-** We could reinstate armax's script (180 days without activity => move to incomplete with message), check still open bugs where a relevant commit was merged in a release, …
 == Previous meeting logs ==