Le 11/03/2025 à 10:35:03+0100, Dmitriy Rabotyagov a écrit
through puppet, manually or ansible or what-ever) it's complicated or even impossible to revert.
Well, that's pretty much the reason why in OpenStack-Ansible (and actually Kolla) we don't go this route by default, but installing most of the services as Python packages inside virtual environments.
Ok. Good to known.
And repositories for supporting tools (like mariadb, rabbitmq, etc) are versioned. So if you have 3 control planes, 1 on Rocky Linux, 1 on Debian and 1 on Ubuntu - all of them will have same versions of mariadb/rabbitmq and OpenStack services, and they can work together.
However, your biggest issue with revert is change of database and/or RPC schema, which makes revert way more touch.
And I don't think there's anything which can solve the database schema issue during rollback without losing data which was created after upgrade.
Yes I know that. But that's is the case for anything relaying on database. But for that It can be done by creating a dump of the database and yes we loose the data create after but it's better that than nothing. Regards. -- Albert SHIH 🦫 🐸 Observatoire de Paris France Heure locale/Local time: ven. 14 mars 2025 08:54:09 CET