[neutron] IPv6 DVR for OVN - Seeking feedback on patch review prospects
Hello, I'm reaching out about the IPv6 DVR feature for OVN (bug #1998609: https://bugs.launchpad.net/neutron/+bug/1998609) and the associated patch (https://review.opendev.org/c/openstack/neutron/+/867513). As noted in the bug comments, Roberto Bartzen Acosta maintained this patch across multiple release cycles, but it hasn't received reviews from core maintainers and is currently blocked by merge conflicts. Roberto mentioned that the feature hasn't been getting traction despite the work put in. This feature would enable distributed routing for IPv6 GUA addresses in OVN deployments, similar to how IPv4 FIPs work with DVR today. The spec was approved and merged (https://review.opendev.org/c/openstack/neutron-specs/+/867979), indicating community interest. Before I invest time rebasing the patch and resolving merge conflicts, I'd like to understand: 1. Are there technical or architectural concerns that have prevented review? 2. Is there a reason this hasn't been prioritized, or is it a matter of reviewer availability? 3. Would core maintainers be willing to review if the patch is rebased and updated? I'm happy to do the rebase work, but I'd prefer not to spend time on something that won't be merged. Any guidance on the status and viability of this feature would be appreciated. Thanks, Max
Hi Max, On 1/23/26 7:24 AM, Maximilian Stinsky-Damke wrote:
Hello,
I'm reaching out about the IPv6 DVR feature for OVN (bug #1998609: https://bugs.launchpad.net/neutron/+bug/1998609) and the associated patch (https://review.opendev.org/c/openstack/neutron/+/867513). As noted in the bug comments, Roberto Bartzen Acosta maintained this patch across multiple release cycles, but it hasn't received reviews from core maintainers and is currently blocked by merge conflicts. Roberto mentioned that the feature hasn't been getting traction despite the work put in.
Sorry, sometimes things fail to get reviewer traction for any number of reasons, thanks for making us aware of this one.
This feature would enable distributed routing for IPv6 GUA addresses in OVN deployments, similar to how IPv4 FIPs work with DVR today. The spec was approved and merged (https://review.opendev.org/c/ openstack/neutron-specs/+/867979), indicating community interest.
Before I invest time rebasing the patch and resolving merge conflicts, I'd like to understand: 1. Are there technical or architectural concerns that have prevented review? 2. Is there a reason this hasn't been prioritized, or is it a matter of reviewer availability? 3. Would core maintainers be willing to review if the patch is rebased and updated?
I'm happy to do the rebase work, but I'd prefer not to spend time on something that won't be merged. Any guidance on the status and viability of this feature would be appreciated.
I don't think there are any concerns with the team based on looking at the spec and comments. What I would recommend is to re-base and fix any merge conflicts, then set the "Review Priority +1" flag on the review, that way it will show up in our dashboard. Unfortunately every time you re-base you have to set the flag again as it's not sticky. Thanks, -Brian
Hi Brian, thanks for the answer. I will try to engage with Roberto if he wants to pick up the work again or if he wants me to move forward. Regarding the Review Priority, is this something anyone can do? At least I dont see a way to set it. Best Regards Max ________________________________ From: Brian Haley <haleyb.dev@gmail.com> Sent: 27 January 2026 01:16 To: Maximilian Stinsky-Damke <Maximilian.Stinsky-Damke@wiit.cloud>; openstack-discuss <openstack-discuss@lists.openstack.org> Subject: Re: [neutron] IPv6 DVR for OVN - Seeking feedback on patch review prospects Warning: This email is from an unusual correspondent. Warning: Make sure this is someone you trust. Hi Max, On 1/23/26 7:24 AM, Maximilian Stinsky-Damke wrote:
Hello,
I'm reaching out about the IPv6 DVR feature for OVN (bug #1998609: https://urlsand.esvalabs.com/?u=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1998609&e=50525cf7&h=c524c6f9&f=y&p=y ) and the associated patch ( https://urlsand.esvalabs.com/?u=https%3A%2F%2Freview.opendev.org%2Fc%2Fopenstack%2Fneutron%2F%2B%2F867513&e=50525cf7&h=986f6524&f=y&p=y ). As noted in the bug comments, Roberto Bartzen Acosta maintained this patch across multiple release cycles, but it hasn't received reviews from core maintainers and is currently blocked by merge conflicts. Roberto mentioned that the feature hasn't been getting traction despite the work put in.
Sorry, sometimes things fail to get reviewer traction for any number of reasons, thanks for making us aware of this one.
This feature would enable distributed routing for IPv6 GUA addresses in OVN deployments, similar to how IPv4 FIPs work with DVR today. The spec was approved and merged ( https://urlsand.esvalabs.com/?u=https%3A%2F%2Freview.opendev.org%2Fc%2F&e=50525cf7&h=05481b12&f=y&p=y openstack/neutron-specs/+/867979), indicating community interest.
Before I invest time rebasing the patch and resolving merge conflicts, I'd like to understand: 1. Are there technical or architectural concerns that have prevented review? 2. Is there a reason this hasn't been prioritized, or is it a matter of reviewer availability? 3. Would core maintainers be willing to review if the patch is rebased and updated?
I'm happy to do the rebase work, but I'd prefer not to spend time on something that won't be merged. Any guidance on the status and viability of this feature would be appreciated.
I don't think there are any concerns with the team based on looking at the spec and comments. What I would recommend is to re-base and fix any merge conflicts, then set the "Review Priority +1" flag on the review, that way it will show up in our dashboard. Unfortunately every time you re-base you have to set the flag again as it's not sticky. Thanks, -Brian -- This message has been checked by Libraesva ESG and is found to be clean. Follow this link to report as spam/bad: https://mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/report-as-bad Follow this link to blocklist sender: https://mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/blocklist
On 1/27/26 3:48 AM, Maximilian Stinsky-Damke wrote:
Hi Brian,
thanks for the answer. I will try to engage with Roberto if he wants to pick up the work again or if he wants me to move forward.
Regarding the Review Priority, is this something anyone can do? At least I dont see a way to set it.
Anyone should be able to set it. If you click on the Reply button on the review it should be one of the options, you might need to be logged-in. If not let me know. -Brian
------------------------------------------------------------------------ *From:* Brian Haley <haleyb.dev@gmail.com> *Sent:* 27 January 2026 01:16 *To:* Maximilian Stinsky-Damke <Maximilian.Stinsky-Damke@wiit.cloud>; openstack-discuss <openstack-discuss@lists.openstack.org> *Subject:* Re: [neutron] IPv6 DVR for OVN - Seeking feedback on patch review prospects Warning: This email is from an unusual correspondent. Warning: Make sure this is someone you trust.
Hi Max,
On 1/23/26 7:24 AM, Maximilian Stinsky-Damke wrote:
Hello,
I'm reaching out about the IPv6 DVR feature for OVN (bug #1998609: https://urlsand.esvalabs.com/? u=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1998609&e=50525cf7&h=c524c6f9&f=y&p=y <https://urlsand.esvalabs.com/?u=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1998609&e=50525cf7&h=c524c6f9&f=y&p=y> ) and the associated patch ( https://urlsand.esvalabs.com/? u=https%3A%2F%2Freview.opendev.org%2Fc%2Fopenstack%2Fneutron%2F%2B%2F867513&e=50525cf7&h=986f6524&f=y&p=y <https://urlsand.esvalabs.com/?u=https%3A%2F%2Freview.opendev.org%2Fc%2Fopenstack%2Fneutron%2F%2B%2F867513&e=50525cf7&h=986f6524&f=y&p=y> ). As noted in the bug comments, Roberto Bartzen Acosta maintained this patch across multiple release cycles, but it hasn't received reviews from core maintainers and is currently blocked by merge conflicts. Roberto mentioned that the feature hasn't been getting traction despite the work put in.
Sorry, sometimes things fail to get reviewer traction for any number of reasons, thanks for making us aware of this one.
This feature would enable distributed routing for IPv6 GUA addresses in OVN deployments, similar to how IPv4 FIPs work with DVR today. The spec was approved and merged ( https://urlsand.esvalabs.com/? u=https%3A%2F%2Freview.opendev.org%2Fc%2F&e=50525cf7&h=05481b12&f=y&p=y <https://urlsand.esvalabs.com/? u=https%3A%2F%2Freview.opendev.org%2Fc%2F&e=50525cf7&h=05481b12&f=y&p=y> openstack/neutron-specs/+/867979), indicating community interest.
Before I invest time rebasing the patch and resolving merge conflicts, I'd like to understand: 1. Are there technical or architectural concerns that have prevented review? 2. Is there a reason this hasn't been prioritized, or is it a matter of reviewer availability? 3. Would core maintainers be willing to review if the patch is rebased and updated?
I'm happy to do the rebase work, but I'd prefer not to spend time on something that won't be merged. Any guidance on the status and viability of this feature would be appreciated.
I don't think there are any concerns with the team based on looking at the spec and comments.
What I would recommend is to re-base and fix any merge conflicts, then set the "Review Priority +1" flag on the review, that way it will show up in our dashboard. Unfortunately every time you re-base you have to set the flag again as it's not sticky.
Thanks,
-Brian
-- This message has been checked by Libraesva ESG and is found to be clean. Follow this link to report as spam/bad: https://mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/report-as-bad <https:// mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/report-as-bad> Follow this link to blocklist sender: https://mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/blocklist <https:// mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/blocklist>
Hi Brian, Seems like I got the patch in a working state against master again. But I am unable to set any Review Priority on this patch, not sure why. Could you help with that? Thanks! Max ________________________________ From: Brian Haley <haleyb.dev@gmail.com> Sent: 28 January 2026 01:27 To: Maximilian Stinsky-Damke <Maximilian.Stinsky-Damke@wiit.cloud>; openstack-discuss <openstack-discuss@lists.openstack.org> Subject: Re: [neutron] IPv6 DVR for OVN - Seeking feedback on patch review prospects On 1/27/26 3:48 AM, Maximilian Stinsky-Damke wrote:
Hi Brian,
thanks for the answer. I will try to engage with Roberto if he wants to pick up the work again or if he wants me to move forward.
Regarding the Review Priority, is this something anyone can do? At least I dont see a way to set it.
Anyone should be able to set it. If you click on the Reply button on the review it should be one of the options, you might need to be logged-in. If not let me know. -Brian
------------------------------------------------------------------------ *From:* Brian Haley <haleyb.dev@gmail.com> *Sent:* 27 January 2026 01:16 *To:* Maximilian Stinsky-Damke <Maximilian.Stinsky-Damke@wiit.cloud>; openstack-discuss <openstack-discuss@lists.openstack.org> *Subject:* Re: [neutron] IPv6 DVR for OVN - Seeking feedback on patch review prospects Warning: This email is from an unusual correspondent. Warning: Make sure this is someone you trust.
Hi Max,
On 1/23/26 7:24 AM, Maximilian Stinsky-Damke wrote:
Hello,
I'm reaching out about the IPv6 DVR feature for OVN (bug #1998609: https://urlsand.esvalabs.com/? u=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1998609&e=50525cf7&h=c524c6f9&f=y&p=y <https://urlsand.esvalabs.com/?u=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1998609&e=50525cf7&h=c524c6f9&f=y&p=y> ) and the associated patch ( https://urlsand.esvalabs.com/? u=https%3A%2F%2Freview.opendev.org%2Fc%2Fopenstack%2Fneutron%2F%2B%2F867513&e=50525cf7&h=986f6524&f=y&p=y <https://urlsand.esvalabs.com/?u=https%3A%2F%2Freview.opendev.org%2Fc%2Fopenstack%2Fneutron%2F%2B%2F867513&e=50525cf7&h=986f6524&f=y&p=y> ). As noted in the bug comments, Roberto Bartzen Acosta maintained this patch across multiple release cycles, but it hasn't received reviews from core maintainers and is currently blocked by merge conflicts. Roberto mentioned that the feature hasn't been getting traction despite the work put in.
Sorry, sometimes things fail to get reviewer traction for any number of reasons, thanks for making us aware of this one.
This feature would enable distributed routing for IPv6 GUA addresses in OVN deployments, similar to how IPv4 FIPs work with DVR today. The spec was approved and merged ( https://urlsand.esvalabs.com/? u=https%3A%2F%2Freview.opendev.org%2Fc%2F&e=50525cf7&h=05481b12&f=y&p=y <https://urlsand.esvalabs.com/? u=https%3A%2F%2Freview.opendev.org%2Fc%2F&e=50525cf7&h=05481b12&f=y&p=y> openstack/neutron-specs/+/867979), indicating community interest.
Before I invest time rebasing the patch and resolving merge conflicts, I'd like to understand: 1. Are there technical or architectural concerns that have prevented review? 2. Is there a reason this hasn't been prioritized, or is it a matter of reviewer availability? 3. Would core maintainers be willing to review if the patch is rebased and updated?
I'm happy to do the rebase work, but I'd prefer not to spend time on something that won't be merged. Any guidance on the status and viability of this feature would be appreciated.
I don't think there are any concerns with the team based on looking at the spec and comments.
What I would recommend is to re-base and fix any merge conflicts, then set the "Review Priority +1" flag on the review, that way it will show up in our dashboard. Unfortunately every time you re-base you have to set the flag again as it's not sticky.
Thanks,
-Brian
-- This message has been checked by Libraesva ESG and is found to be clean. Follow this link to report as spam/bad: https://mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/report-as-bad <https:// mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/report-as-bad> Follow this link to blocklist sender: https://mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/blocklist <https:// mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/blocklist>
-- This message has been checked by Libraesva ESG and is found to be clean. Follow this link to report as spam/bad: https://mx10.wiit.cloud/action/4f134k09FCzTgR0/report-as-bad Follow this link to blocklist sender: https://mx10.wiit.cloud/action/4f134k09FCzTgR0/blocklist
Hi Max, I see someone beat me to it, this change has RP+1 set now. Thanks, -Brian On 1/31/26 2:12 AM, Maximilian Stinsky-Damke wrote:
Hi Brian,
Seems like I got the patch in a working state against master again. But I am unable to set any Review Priority on this patch, not sure why. Could you help with that?
Thanks! Max ------------------------------------------------------------------------ *From:* Brian Haley <haleyb.dev@gmail.com> *Sent:* 28 January 2026 01:27 *To:* Maximilian Stinsky-Damke <Maximilian.Stinsky-Damke@wiit.cloud>; openstack-discuss <openstack-discuss@lists.openstack.org> *Subject:* Re: [neutron] IPv6 DVR for OVN - Seeking feedback on patch review prospects On 1/27/26 3:48 AM, Maximilian Stinsky-Damke wrote:
Hi Brian,
thanks for the answer. I will try to engage with Roberto if he wants to pick up the work again or if he wants me to move forward.
Regarding the Review Priority, is this something anyone can do? At least I dont see a way to set it.
Anyone should be able to set it. If you click on the Reply button on the review it should be one of the options, you might need to be logged-in. If not let me know.
-Brian
------------------------------------------------------------------------ *From:* Brian Haley <haleyb.dev@gmail.com> *Sent:* 27 January 2026 01:16 *To:* Maximilian Stinsky-Damke <Maximilian.Stinsky-Damke@wiit.cloud>; openstack-discuss <openstack-discuss@lists.openstack.org> *Subject:* Re: [neutron] IPv6 DVR for OVN - Seeking feedback on patch review prospects Warning: This email is from an unusual correspondent. Warning: Make sure this is someone you trust.
Hi Max,
On 1/23/26 7:24 AM, Maximilian Stinsky-Damke wrote:
Hello,
I'm reaching out about the IPv6 DVR feature for OVN (bug #1998609: https://urlsand.esvalabs.com/? <https://urlsand.esvalabs.com/?> u=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1998609&e=50525cf7&h=c524c6f9&f=y&p=y <https://urlsand.esvalabs.com/? u=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1998609&e=50525cf7&h=c524c6f9&f=y&p=y <https://urlsand.esvalabs.com/?u=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1998609&e=50525cf7&h=c524c6f9&f=y&p=y>> ) and the associated patch ( https://urlsand.esvalabs.com/? <https://urlsand.esvalabs.com/?> u=https%3A%2F%2Freview.opendev.org%2Fc%2Fopenstack%2Fneutron%2F%2B%2F867513&e=50525cf7&h=986f6524&f=y&p=y <https://urlsand.esvalabs.com/? u=https%3A%2F%2Freview.opendev.org%2Fc%2Fopenstack%2Fneutron%2F%2B%2F867513&e=50525cf7&h=986f6524&f=y&p=y <https://urlsand.esvalabs.com/?u=https%3A%2F%2Freview.opendev.org%2Fc%2Fopenstack%2Fneutron%2F%2B%2F867513&e=50525cf7&h=986f6524&f=y&p=y>> ). As noted in the bug comments, Roberto Bartzen Acosta maintained this patch across multiple release cycles, but it hasn't received reviews from core maintainers and is currently blocked by merge conflicts. Roberto mentioned that the feature hasn't been getting traction despite the work put in.
Sorry, sometimes things fail to get reviewer traction for any number of reasons, thanks for making us aware of this one.
This feature would enable distributed routing for IPv6 GUA addresses in OVN deployments, similar to how IPv4 FIPs work with DVR today. The spec was approved and merged ( https://urlsand.esvalabs.com/? <https://urlsand.esvalabs.com/?> u=https%3A%2F%2Freview.opendev.org%2Fc%2F&e=50525cf7&h=05481b12&f=y&p=y <https://urlsand.esvalabs.com/? u=https%3A%2F%2Freview.opendev.org%2Fc%2F&e=50525cf7&h=05481b12&f=y&p=y> openstack/neutron-specs/+/867979), indicating community interest.
Before I invest time rebasing the patch and resolving merge conflicts, I'd like to understand: 1. Are there technical or architectural concerns that have prevented review? 2. Is there a reason this hasn't been prioritized, or is it a matter of reviewer availability? 3. Would core maintainers be willing to review if the patch is rebased and updated?
I'm happy to do the rebase work, but I'd prefer not to spend time on something that won't be merged. Any guidance on the status and viability of this feature would be appreciated.
I don't think there are any concerns with the team based on looking at the spec and comments.
What I would recommend is to re-base and fix any merge conflicts, then set the "Review Priority +1" flag on the review, that way it will show up in our dashboard. Unfortunately every time you re-base you have to set the flag again as it's not sticky.
Thanks,
-Brian
-- This message has been checked by Libraesva ESG and is found to be clean. Follow this link to report as spam/bad: https://mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/report-as-bad <https:// mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/report-as-bad> <https:// mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/report-as-bad> Follow this link to blocklist sender: https://mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/blocklist <https:// mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/blocklist> <https:// mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/blocklist>
-- This message has been checked by Libraesva ESG and is found to be clean. Follow this link to report as spam/bad: https://mx10.wiit.cloud/action/4f134k09FCzTgR0/report-as-bad <https:// mx10.wiit.cloud/action/4f134k09FCzTgR0/report-as-bad> Follow this link to blocklist sender: https://mx10.wiit.cloud/action/4f134k09FCzTgR0/blocklist <https:// mx10.wiit.cloud/action/4f134k09FCzTgR0/blocklist>
participants (2)
-
Brian Haley
-
Maximilian Stinsky-Damke