Lucas, can you please share the status on this ticket and update if development part is complete. Daniel: Can you please provide some idea on how important this capability is for Verizon OVN migration and if customers typically use this workflow for deployment?
(In reply to Gurpreet Singh from comment #1) > Lucas, can you please share the status on this ticket and update if > development part is complete. > > Daniel: Can you please provide some idea on how important this capability is > for Verizon OVN migration and if customers typically use this workflow for > deployment? Hi, So this feature is scheduled for 17.1 but, I backported the Neutron patches to 17.0 (already merged) and asked Mark from the core OVN team if it was possible to backport the required OVN change to OVN 22.03 [0] so that we could start the tests earlier. For 17.1 [1], everything should be in-place already. Assuming that we are going to use OVN 22.06 for that release. So, overall everything looks good. We should have all bits in place but, this is a 17.1 feature. The backport to 17.0 is just an attempt to accelerate the process of getting it tested. [0] https://patchwork.ozlabs.org/project/ovn/patch/20220822194532.1547270-1-mmichels@redhat.com/ [1] https://bugzilla.redhat.com/show_bug.cgi?id=2118688 Cheers, Lucas
Thanks for the clarification Lucas.
According to our records, this should be resolved by openstack-neutron-18.4.1-0.20221128170741.5258354.el9ost. This build is available now.
Support has ended on 22 September 2023.