[kolla-ansible] partial upgrades / mixed releases in deployments
Hi, We are currently preparing to upgrade a kolla-ansible deployed OpenStack cluster and were wondering if it is possible to upgrade individual services independently of each other, for example to upgrade one service at a time to Ussuri while still using kolla-ansible to deploy and reconfigure the Train versions of the other services. Our idea was that either the Ussuri release of kolla-ansible is used to deploy Train and Ussuri services (with properly migrated configuration), or that two different releases and configurations are used for the two sets of services in the same deployment. Does anyone have experience if this is practical or even possible? Thank you in advance, Erik _____ Erik Panter Systementwickler | Infrastruktur Mittwald CM Service GmbH & Co. KG Königsberger Straße 4-6 32339 Espelkamp Tel.: 05772 / 293-900 Fax: 05772 / 293-333 Mobil: 0151 / 12345678 e.panter@mittwald.de https://www.mittwald.de Geschäftsführer: Robert Meyer, Florian Jürgens St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen Informationen zur Datenverarbeitung im Rahmen unserer Geschäftstätigkeit gemäß Art. 13-14 DSGVO sind unter www.mittwald.de/ds abrufbar.
On Thu, 4 Mar 2021 at 16:44, Erik Panter <E.Panter@mittwald.de> wrote:
Hi,
We are currently preparing to upgrade a kolla-ansible deployed OpenStack cluster and were wondering if it is possible to upgrade individual services independently of each other, for example to upgrade one service at a time to Ussuri while still using kolla-ansible to deploy and reconfigure the Train versions of the other services.
Our idea was that either the Ussuri release of kolla-ansible is used to deploy Train and Ussuri services (with properly migrated configuration), or that two different releases and configurations are used for the two sets of services in the same deployment.
Does anyone have experience if this is practical or even possible?
Hi Erik, In general, this might work, however it's not something we test or "support", so it cannot be guaranteed. Generally there are not too many changes in how services are deployed from release to release, but there are times when procedures change, configuration changes, or we may introduce incompatibilities between the container images and the Ansible deployment tooling. At runtime, there is also the operation of services in a mixed environment to consider, although stable components and APIs help here. All of that is to say that such a configuration would need testing, and ideally not be in place for a long period of time. One similar case we often have is upgrading a single service, often Magnum, to a newer release than the rest of the cloud. To achieve this we set the magnum_tag variable. Mark
Thank you in advance,
Erik
_____
Erik Panter Systementwickler | Infrastruktur
Mittwald CM Service GmbH & Co. KG Königsberger Straße 4-6 32339 Espelkamp
Tel.: 05772 / 293-900 Fax: 05772 / 293-333 Mobil: 0151 / 12345678
e.panter@mittwald.de https://www.mittwald.de
Geschäftsführer: Robert Meyer, Florian Jürgens
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
Informationen zur Datenverarbeitung im Rahmen unserer Geschäftstätigkeit gemäß Art. 13-14 DSGVO sind unter www.mittwald.de/ds abrufbar.
participants (2)
-
Erik Panter
-
Mark Goddard