Open Stack

Hi Dmitriy,

those are great news! I agree with it being installer agnostic, I even think this was discussed at some earlier PTGs. The problem with the migration tool is that it does have no CI so the patches are manually tested, best effort. That said, would be awesome to have CI with openstack-ansible :)

Let me know if you need any help understanding the concept, we can schedule some call if you want to go over the code base too if you’d be insterested.

Best regards
Kuba



> On Apr 14, 2023, at 11:10 PM, Dmitriy Rabotyagov <noonedeadpunk at gmail.com> wrote:
> 
> Hi, Jakub,
> 
> I'm interested to keep OVN migration alive. At the same time I'm not interested in maintaining TripleO bits.
> 
> I can check the code deeper during the next week and see what I can do and return back to you.
> 
> Ideally I think the code should be tool-agnostic, but at worst case scenario I will be able to work on adding OpenStack-Ansible support for the migration.
> 
> пт, 14 апр. 2023 г., 23:05 Jakub Libosvar <jlibosva at redhat.com>:
> Hello Neutrinos and others,
> 
> as this has been brought up several times through some conversation channels with no consensus, I wanted to start a discussion and possibly find a consensus about the code for migrating an OpenStack from OVS mechanism driver to OVN [1].
> 
> The code leverages TripleO to install and to configure OVN services, however the TripleO project is no longer maintained after Zed release [2].
> This brings up the question what to do with the migration tooling that relies on TripleO. Shall we remove the code completely or is there anybody who would be interested in maintaining that code and implement support for other installers?
> 
> Thanks
> 
> Kuba
> 
> [1] https://opendev.org/openstack/neutron/src/branch/master/tools/ovn_migration/tripleo_environment
> [2] https://review.opendev.org/c/openstack/governance/+/878799
> 
>