Difference between revisions of "Network/Meetings"
(→Announcements / Reminders) |
Katonalala (talk | contribs) (→On Demand Agenda) |
||
| (30 intermediate revisions by 3 users not shown) | |||
| Line 6: | Line 6: | ||
* Still looking for "new daddies" for | * Still looking for "new daddies" for | ||
** neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html | ** neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html | ||
| − | ** | + | *** I just sent LAST CALL reminder as we talked last week: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012099.html |
| − | + | * We are getting close to Ussuri-2, it will be in the week of February 10: https://releases.openstack.org/ussuri/schedule.html | |
| − | + | * I forgot about it last week, next release will be Victoria: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011947.html :) | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | * I | ||
* Shanghai PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010702.html and also on http://kaplonski.pl/blog/shanghai_ptg_summary/ (with photos from team dinner) | * Shanghai PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010702.html and also on http://kaplonski.pl/blog/shanghai_ptg_summary/ (with photos from team dinner) | ||
| Line 20: | Line 15: | ||
Blueprints which we should include in Ussuri milestones: | Blueprints which we should include in Ussuri milestones: | ||
| − | * Blueprints for Ussuri- | + | * Blueprints for Ussuri-2: https://launchpad.net/neutron/+milestone/ussuri-2 |
* https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/ | * https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/ | ||
* https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes | * https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes | ||
| Line 43: | Line 38: | ||
** Patches for stadium projects are needed: | ** Patches for stadium projects are needed: | ||
*** https://review.opendev.org/#/q/topic:ipv6-only-deployment-and-testing+(status:open+OR+status:merged)+(project:%255Eopenstack/neutron.*+OR+project:%255Eopenstack/networking-.*) | *** https://review.opendev.org/#/q/topic:ipv6-only-deployment-and-testing+(status:open+OR+status:merged)+(project:%255Eopenstack/neutron.*+OR+project:%255Eopenstack/networking-.*) | ||
| − | |||
* Drop Python 2.7 Support (njohnston) | * Drop Python 2.7 Support (njohnston) | ||
** https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html | ** https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html | ||
| + | ** Etherpad: https://etherpad.openstack.org/p/neutron-train-zuulv3-py27drop | ||
* Project Specific PTL and Contributor Documentation | * Project Specific PTL and Contributor Documentation | ||
| − | ** | + | ** https://governance.openstack.org/tc/goals/proposed/project-ptl-and-contrib-docs.html |
=== Bugs and Gate issues === | === Bugs and Gate issues === | ||
| − | + | haleyb was on bug deputy: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012094.html | |
| + | |||
| + | I propose to add new official tag "ovn" to launchpad and our docs. What do You think? | ||
More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI | More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI | ||
| Line 67: | Line 64: | ||
You can find more information about what the role is here: https://docs.openstack.org/neutron/latest/contributor/policies/bugs.html#neutron-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 | + | During the Denver PTG we made the decision to institute a fixed rotation for the the bugs deputy role. The currently scheduled rotation is the following: |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
{| class="wikitable" style="text-align: center;" | {| class="wikitable" style="text-align: center;" | ||
|- | |- | ||
! Date !! who !! note | ! Date !! who !! note | ||
|- | |- | ||
| − | | December-23-2019 || Bernard Cafarelli (bcafarel) || | + | | December-23-2019 || Bernard Cafarelli (bcafarel) || switched with Miguel Lavalle (mlavalle) |
|- | |- | ||
| December-30-2019 || Slawek Kaplonski (slaweq) || | | December-30-2019 || Slawek Kaplonski (slaweq) || | ||
| Line 121: | Line 88: | ||
| February-17-2020 || Nate Johnston (njohnston) || | | February-17-2020 || Nate Johnston (njohnston) || | ||
|- | |- | ||
| − | | Fabruary-24-2020 || Miguel Lavalle (mlavalle) || | + | | Fabruary-24-2020 || Miguel Lavalle (mlavalle) || switched with Bernard Cafarelli (bcafarel) |
|- | |- | ||
| March-2-2020 || YAMAMOTO Takashi (yamamoto) || | | March-2-2020 || YAMAMOTO Takashi (yamamoto) || | ||
| Line 133: | Line 100: | ||
=== Networking OVN and ML2+OVS+DVR Convergence (Tuesday meetings) === | === Networking OVN and ML2+OVS+DVR Convergence (Tuesday meetings) === | ||
| + | |||
| + | Merge OVN into Neutron tree: | ||
| + | * Blueprint: https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge | ||
| + | * Proposed rehome plan: https://ethercalc.openstack.org/networking-ovn-migration | ||
| + | * Planning Etherpad https://etherpad.openstack.org/p/neutron-networking-ovn-merge | ||
| + | * Spec: https://review.opendev.org/#/c/658414/ | ||
=== Docs === | === Docs === | ||
| Line 149: | Line 122: | ||
=== Neutron-lib, planned refactoring and other impacts === | === Neutron-lib, planned refactoring and other impacts === | ||
| + | |||
| + | We just released neutron-lib 2.0.0 - with dropped support for python 2.7 and fix for bug introduced accidentally in 1.31.0 | ||
HOUSE KEEPING | HOUSE KEEPING | ||
| Line 164: | Line 139: | ||
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: | 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: | ||
| + | * standardize on zuul v3 syntax: | ||
| + | ** Do we need to change job definitions on stable branches as well? | ||
| + | *** The question come up for bagpipe job conversions. The old legacy job definitions are here: https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/zuul-legacy-jobs.yaml#L367-L377. | ||
| + | If we do the conversion for master only, the legacy job definitions will remain in openstack-zuul-jobs repo, but if we remove them we have to backport the new job template to stable branches ase well. | ||
* Topic for the meeting (keep this template, please): | * Topic for the meeting (keep this template, please): | ||
** (your nickname): brief description. | ** (your nickname): brief description. | ||
| Line 170: | Line 149: | ||
== Previous meeting logs == | == Previous meeting logs == | ||
* Previous meetings, with their notes and logs, can be found [http://eavesdrop.openstack.org/meetings/networking/ here]. | * Previous meetings, with their notes and logs, can be found [http://eavesdrop.openstack.org/meetings/networking/ here]. | ||
| + | ** [http://eavesdrop.openstack.org/meetings/networking/2020/?C=M;O=D networking-2020] | ||
** [http://eavesdrop.openstack.org/meetings/networking/2019/?C=M;O=D networking-2019] | ** [http://eavesdrop.openstack.org/meetings/networking/2019/?C=M;O=D networking-2019] | ||
** [http://eavesdrop.openstack.org/meetings/networking/2018/?C=M;O=D networking-2018] | ** [http://eavesdrop.openstack.org/meetings/networking/2018/?C=M;O=D networking-2018] | ||
Revision as of 13:44, 24 January 2020
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
- 1 Announcements / Reminders
- 2 Blueprints
- 3 Community Goals
- 4 Bugs and Gate issues
- 5 Neutron performance subteam (Monday meetings)
- 6 Networking OVN and ML2+OVS+DVR Convergence (Tuesday meetings)
- 7 Docs
- 8 CLI/SDK
- 9 Neutron-lib, planned refactoring and other impacts
- 10 On Demand Agenda
- 11 Previous meeting logs
Announcements / Reminders
- Still looking for "new daddies" for
- neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html
- I just sent LAST CALL reminder as we talked last week: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012099.html
- neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html
- We are getting close to Ussuri-2, it will be in the week of February 10: https://releases.openstack.org/ussuri/schedule.html
- I forgot about it last week, next release will be Victoria: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011947.html :)
- Shanghai PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010702.html and also on http://kaplonski.pl/blog/shanghai_ptg_summary/ (with photos from team dinner)
Blueprints
Blueprints which we should include in Ussuri milestones:
- Blueprints for Ussuri-2: https://launchpad.net/neutron/+milestone/ussuri-2
- https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/
- https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes
- https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge - Convergence of ML2+OVS+DVR and OVN
- https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - spec is here: https://review.opendev.org/#/c/657170
- https://blueprints.launchpad.net/neutron/+spec/neutron-classifier-neutron-qos - there is series of patches in https://review.opendev.org/#/q/topic:qos-classifier+(status:open+OR+status:merged) - spec still not done https://review.opendev.org/#/c/678865/
- https://blueprints.launchpad.net/neutron/+spec/metadata-over-ipv6
- https://blueprints.launchpad.net/neutron/+spec/tagging-on-post
- https://blueprints.launchpad.net/neutron/+spec/evacuate-agent-resources
- https://bugs.launchpad.net/neutron/+bug/1841067 - [RFE] SR-IOV agent depends on mac addresses for getting bound ports
- https://blueprints.launchpad.net/neutron/+spec/fip-pf-description
- https://blueprints.launchpad.net/neutron/+spec/default-dns-zone-per-tenant
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
- Support IPv6-Only Deployments (slaweq)
- https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
- https://storyboard.openstack.org/#!/story/2005477 (This seems to be used to track gmann's job changes)
- Patches for stadium projects are needed:
- Drop Python 2.7 Support (njohnston)
- Project Specific PTL and Contributor Documentation
Bugs and Gate issues
haleyb was on bug deputy: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012094.html
I propose to add new official tag "ovn" to launchpad and our docs. What do You think?
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 currently scheduled rotation is the following:
| Date | who | note |
|---|---|---|
| December-23-2019 | Bernard Cafarelli (bcafarel) | switched with Miguel Lavalle (mlavalle) |
| December-30-2019 | Slawek Kaplonski (slaweq) | |
| January-6-2020 | Hongbin Lu (hongbin) | |
| Januaryu-13-2020 | Brian Haley (haleyb) | |
| January-20-2020 | Lajos Katona (lajoskatona) | |
| January-27-2020 | Ryan Tidwell (tidwellr) | |
| February-3-2020 | Swaminathan Vasudevan (Swami) | |
| February-10-2020 | Akihiro Motoki (amotoki) | |
| February-17-2020 | Nate Johnston (njohnston) | |
| Fabruary-24-2020 | Miguel Lavalle (mlavalle) | switched with Bernard Cafarelli (bcafarel) |
| March-2-2020 | YAMAMOTO Takashi (yamamoto) | |
| March-9-2020 | 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
Neutron performance subteam (Monday meetings)
Networking OVN and ML2+OVS+DVR Convergence (Tuesday meetings)
Merge OVN into Neutron tree:
- Blueprint: https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge
- Proposed rehome plan: https://ethercalc.openstack.org/networking-ovn-migration
- Planning Etherpad https://etherpad.openstack.org/p/neutron-networking-ovn-merge
- Spec: https://review.opendev.org/#/c/658414/
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
We just released neutron-lib 2.0.0 - with dropped support for python 2.7 and fix for bug introduced accidentally in 1.31.0
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:
- standardize on zuul v3 syntax:
- Do we need to change job definitions on stable branches as well?
- The question come up for bagpipe job conversions. The old legacy job definitions are here: https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/zuul-legacy-jobs.yaml#L367-L377.
- Do we need to change job definitions on stable branches as well?
If we do the conversion for master only, the legacy job definitions will remain in openstack-zuul-jobs repo, but if we remove them we have to backport the new job template to stable branches ase well.
- 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.
