Meetings/NeutronDrivers

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
Ready for discussion:
- RFE's ready for discussion
Approved RFE's:
Other RFE's:
On Demand agenda (keep this template, please):
- (irc nick): topic
- (lajoskatona): Opinions for Distributed Metadata feature:
  - https://review.opendev.org/q/topic:%22distributed_metadata_data_path%22
  - The feature is bassed on a haproxy running on the compute: https://opendev.org/openstack/neutron/src/branch/master/neutron/agent/l2/extensions/metadata/host_metadata_proxy.py#L47
  - It uses port 80, so when you run curl http://169.254.169.254/openstack you have your answer back.
  - But in devstack an apache service can sit on port 80 easily, and that makes the whole feature hard to test in devstack.
  - I would like to discuss it with you and see what I am missing.
- (haleyb): [RFE] control random-fully behavior on a per-FIP base - https://bugs.launchpad.net/neutron/+bug/2083214
- (ralonsoh): https://bugs.launchpad.net/neutron/+bug/2083527. There are two topics to discuss here
  - 1) To be able to nest two external networks, as explained in the LP bug
  - 2) For a single router configuration, if the GW network is tunnelled: the fix https://review.opendev.org/c/openstack/neutron/+/931495 that is solving the issue of the FIPs as long as the LRPs are not bound to a chassis but the router (see https://review.opendev.org/q/topic:%22bug/2052821%22, in particular https://review.opendev.org/c/openstack/neutron/+/909194).

Previous meeting logs

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