Hey, So I think this can be possible, but it was never tested. We always stay on current supported versions, so upgrades are more harmonized for us. I did run minor osa upgrades with os upgrades only, but I assume you can do the same with major ones as well. The potential problems with that I might see, is that you will be running clusters for rabbitmq and mariadb consisting of different versions for a while. Such upgrades are performed on osa upgrades, so when you do os upgrades for control plane versions of these are already aligned and will be consistent between operating systems. And actually the same is true for all software, as running new OpenStack against one controller will perform db migrations, so rest will not be able to run with new db schema. But potentially you can address that by disabling backbends on non-upgraded controllers once service is deployed on the new one. So the biggest challenge to address, is that os upgrades of controllers is assumed to be performed one-by-one, while for OpenStack upgrade you want to align service version between all controllers ASAP On Fri, 20 Dec 2024, 13:27 engineer2024, <engineerlinux2024@gmail.com> wrote:
Is it possible to upgrade openstack ansible from one major release to another, along with the os distribution upgrade all in one flow ? I mean, as of now we are doing the upgrade as two step process. first we are upgrading the os of the hosts and then the os of the lxc containers and then re running the existing openstack version playbooks. Next , we are upgrading to major release of OSA.
This two step process is doubling our effort and time to upgrade to a major version. Is it possible to download and run the major release playbooks soon after the os upgrades ? instead of rerunning the existing playbook again and then download and running next version playbooks ?