Difference between revisions of "Meetings/NeutronDrivers"

Latest revision as of 08:03, 31 May 2024

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, obondarev, tobias-urdin, lajoskatona, amotoki, haleyb, ralonsoh

Agenda

Ongoing discussions:
To be vetted for discussion:
- Confirmed RFE's
To be screened:
- RFE's to be screened
Approved RFE's:
Other RFE's:
On Demand agenda (keep this template, please):
- (Christian Rohmann): [RFE] BGP Dynamic Routing for IPv4 AND IPv6 routes not possible with just one dragent (really make use of MP-BGP or support multiple BGP speakers / sessions per dragent) (https://bugs.launchpad.net/neutron/+bug/2064120)
  - https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/ZRDT2W53GWSB5DPCDGW6CJWFULSGKU6Z/
- (lajoskatona): Recent finding with coverage jobs andthe suggestion to change lazy=subquery to lazy=selectin
  - Thread: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/EHLQQXNG3NLLZYPDGG2ES3DINIJ7YT3N/
  - SQLAlchemy doc page: https://docs.sqlalchemy.org/en/20/orm/queryguide/relationships.html
- (slaweq) APIs for resources which don't have project_id still requires it in the API definition - bug APIs for resources which don't have project_id still requires it in the API definition
  - I was trying to explain it in details in the comment https://bugs.launchpad.net/neutron/+bug/2022043/comments/5
  - question: do we want to care about this small IMO confusion for users about project_id attribute in the API of some resources which don't really have project_id associated?
- (irc nick): topic

Previous meeting logs

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

@@ Line 1: / Line 1: @@
 The Neutron Drivers Team ([[Neutron Drivers]]) holds public meetings as advertised on [http://eavesdrop.openstack.org/#Neutron_drivers_Meeting OpenStack IRC Meetings Calendar]. If you are unable to attend, please check the most recent [http://eavesdrop.openstack.org/meetings/neutron_drivers/ logs.]
-'''Ping list''': ykarel, mlavalle, mtomaska, slawek, obondarev, sahid, tobias-urdin, lajoskatona, amotoki
+'''Ping list''': ykarel, mlavalle, mtomaska, slaweq, obondarev, tobias-urdin, lajoskatona, amotoki, haleyb, ralonsoh
 == Agenda ==
@@ Line 19: / Line 19: @@
 ** [https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=EXPIRED&field.tag=rfe-approved Expired/Approved RFE's]
 * On Demand agenda (keep this template, please):
-** (haleyb, rubasov): migrate to a better ipv6 isolated metadata involving a new ipv6 metadata address: https://review.opendev.org/c/openstack/neutron/+/876903
+** (Christian Rohmann): [RFE] BGP Dynamic Routing for IPv4 AND IPv6 routes not possible with just one dragent (really make use of MP-BGP or support multiple BGP speakers / sessions per dragent) (https://bugs.launchpad.net/neutron/+bug/2064120)
-** (ihrachys, slaweq): make metadata / RA / NA work for stateless SGs by default (in context of OVN): https://review.opendev.org/q/topic:bug%252F2009053 https://review.opendev.org/q/topic:bug%252F2006949 https://review.opendev.org/q/topic:issue%252FOSP-20968
+*** https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/ZRDT2W53GWSB5DPCDGW6CJWFULSGKU6Z/
-*** Decisions to be made:
+** (lajoskatona): Recent finding with coverage jobs andthe suggestion to change lazy=subquery to lazy=selectin
-**** 1) whether these services should work by default at all;
+*** Thread: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/EHLQQXNG3NLLZYPDGG2ES3DINIJ7YT3N/
-**** 2) if so, whether we want to have SG rules allowing them exposed in neutron API, or handled by backend.
+*** SQLAlchemy doc page: https://docs.sqlalchemy.org/en/20/orm/queryguide/relationships.html
-** Example (nick): topic
+** (slaweq) APIs for resources which don't have project_id still requires it in the API definition - bug  APIs for resources which don't have project_id still requires it in the API definition
+*** I was trying to explain it in details in the comment https://bugs.launchpad.net/neutron/+bug/2022043/comments/5
+*** question: do we want to care about this small IMO confusion for users about project_id attribute in the API of some resources which don't really have project_id associated?
+** (irc nick): topic
 == Previous meeting logs ==
 * Previous meetings, with their notes and logs, can be found [http://eavesdrop.openstack.org/meetings/neutron_drivers/ here].
+** [http://eavesdrop.openstack.org/meetings/neutron_drivers/2024/?C=M;O=D neutron_drivers-2024]
+** [http://eavesdrop.openstack.org/meetings/neutron_drivers/2023/?C=M;O=D neutron_drivers-2023]
+** [http://eavesdrop.openstack.org/meetings/neutron_drivers/2022/?C=M;O=D neutron_drivers-2022]
+** [http://eavesdrop.openstack.org/meetings/neutron_drivers/2021/?C=M;O=D neutron_drivers-2021]
+** [http://eavesdrop.openstack.org/meetings/neutron_drivers/2020/?C=M;O=D neutron_drivers-2020]
+** [http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/?C=M;O=D neutron_drivers-2019]
+** [http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/?C=M;O=D neutron_drivers-2018]
+** [http://eavesdrop.openstack.org/meetings/neutron_drivers/2017/?C=M;O=D neutron_drivers-2017]
+** [http://eavesdrop.openstack.org/meetings/neutron_drivers/2016/?C=M;O=D neutron_drivers-2016]
+** [http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/?C=M;O=D neutron_drivers-2015]
+** [http://eavesdrop.openstack.org/meetings/neutron_drivers/2014/?C=M;O=D neutron_drivers-2014]