Difference between revisions of "Meetings/NeutronDrivers"
< Meetings
(→Agenda) |
Brian-haley (talk | contribs) |
||
| Line 12: | Line 12: | ||
*** keepalived notify scripts replacement: https://review.opendev.org/c/openstack/neutron/+/125384. Cause: two consecutive quick events (transitions) could report an incorrect state. | *** keepalived notify scripts replacement: https://review.opendev.org/c/openstack/neutron/+/125384. Cause: two consecutive quick events (transitions) could report an incorrect state. | ||
*** This issue was still present with this implementation and fixed (or at least highly mitigated) by https://review.opendev.org/q/I70037da9cdd0f8448e0af8dd96b4e3f5de5728ad | *** This issue was still present with this implementation and fixed (or at least highly mitigated) by https://review.opendev.org/q/I70037da9cdd0f8448e0af8dd96b4e3f5de5728ad | ||
| − | *** My proposal: to have a configurable state report method (python script, notify scripts) during some releases. Make the current one (python script) the default one but change it in the next release. If the new method (notify scripts) is reliable, remove the python script implementation. POC: https://review.opendev.org/c/openstack/neutron/+/965909 | + | *** My proposal: to have a configurable state report method (python script, notify scripts) during some releases. Make the current one (python script) the default one but change it in the next release. If the new method (notify scripts) is reliable, remove the python script implementation. |
| + | *** POC: https://review.opendev.org/c/openstack/neutron/+/965909 | ||
| + | *** NOTE: I need someone else to implement this feature, I won't have time for it. | ||
** (cardoe): physical VXLAN networks with Neutron | ** (cardoe): physical VXLAN networks with Neutron | ||
*** I'm happy do demonstrate the functionality of VXLAN in a physical data center. I'll show switches updating and traffic routing with Ironic nodes. | *** I'm happy do demonstrate the functionality of VXLAN in a physical data center. I'll show switches updating and traffic routing with Ironic nodes. | ||
| Line 18: | Line 20: | ||
*** https://review.opendev.org/c/openstack/neutron/+/965053 | *** https://review.opendev.org/c/openstack/neutron/+/965053 | ||
*** https://review.opendev.org/c/openstack/neutron-specs/+/952166 | *** https://review.opendev.org/c/openstack/neutron-specs/+/952166 | ||
| − | |||
* Ongoing discussions: | * Ongoing discussions: | ||
* To be vetted for discussion: | * To be vetted for discussion: | ||
Revision as of 22:26, 18 November 2025
The Neutron Drivers Team (Neutron Drivers) holds public meetings as advertised on OpenStack IRC Meetings Calendar. If you are unable to attend, please check the most recent logs.
Ping list: ykarel, mlavalle, mtomaska, slaweq, tobias-urdin, lajoskatona, haleyb, ralonsoh
Agenda
- On Demand agenda. Use this section to add your proposal to this meeting; do not use any other section (keep this template, please):
- (irc nick): topic
- (dsan): Set a local TXT record in the DHCP agent/dnsmasq
- https://bugs.launchpad.net/neutron/+bug/2123836
- Team asked for more info, will need to look at proposal again
- (ralonsoh 2025-11-21) Refactor neutron-keepalived-state-change (LP#1970944):
- keepalived notify scripts replacement: https://review.opendev.org/c/openstack/neutron/+/125384. Cause: two consecutive quick events (transitions) could report an incorrect state.
- This issue was still present with this implementation and fixed (or at least highly mitigated) by https://review.opendev.org/q/I70037da9cdd0f8448e0af8dd96b4e3f5de5728ad
- My proposal: to have a configurable state report method (python script, notify scripts) during some releases. Make the current one (python script) the default one but change it in the next release. If the new method (notify scripts) is reliable, remove the python script implementation.
- POC: https://review.opendev.org/c/openstack/neutron/+/965909
- NOTE: I need someone else to implement this feature, I won't have time for it.
- (cardoe): physical VXLAN networks with Neutron
- I'm happy do demonstrate the functionality of VXLAN in a physical data center. I'll show switches updating and traffic routing with Ironic nodes.
- https://review.opendev.org/c/openstack/neutron/+/965415 rendered: https://cardoe.com/neutron/evpn-vxlan-network/admin/data-center-networks.html
- https://review.opendev.org/c/openstack/neutron/+/965053
- https://review.opendev.org/c/openstack/neutron-specs/+/952166
- Ongoing discussions:
- To be vetted for discussion:
- To be screened:
- Ready for discussion:
- Approved RFE's:
- Approved RFE's
- Pending Specs - please review
- (amnik) Add spec for NFS-Ganesha extension in OVN Agent
- (s3rj1k) Add `Agent Startup State Tracking`
- (vprokofev) Add spec for random-fully per-FIP feature RFE
- Merged Specs
- Other RFE's:
Previous meeting logs
- Previous meetings, with their notes and logs, can be found here.
