[Neutron] Future of TripleO OVN migration in-tree code

Dmitriy Rabotyagov noonedeadpunk at gmail.com
Sat Apr 15 03:10:25 UTC 2023


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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230415/774eef48/attachment.htm>


More information about the openstack-discuss mailing list