On 6/1/23 13:19, Dmitriy Rabotyagov wrote:
You can set `rabbitmq_install_method: distro` in user_variables and rabbitmq will get installed from distro-provided repositories rather then external ones: https://opendev.org/openstack/openstack-ansible-rabbitmq_server/src/branch/m... But yes, default behaviour is to use external repos.
You're slightly wrong about reasons behind why this behaviour is default though. It's not about having "latest" versions, it's about having consistent/same versions across all distributions. First of all, then related bugs and security vulnerabilities are the same for all distros, so it's kinda easier to keep track on that. But then most important part is cross-distro installations. So let's assume an individual is running Ubuntu (or CentOS, doesn't matter), and they want to migrate to Debian. Having different rabbitmq versions installed by these distributions will totally be a blocker for such resilient migration. At the same time, when exactly the same versions of rabbit/erlang/galera are installed - they can just re-setup control planes one by one to another distro without any pain and the cluster will remain functional.
Hi Dmitriy, Thanks for the explanation. It makes more sense now (even though I don't think there's many people willing to switch distro in an existing deployment). Cheers, Thomas Goirand (zigo)