[openstack][kolla-ansible]about upgrading openstack
Hello. I read this doc about upgrading openstack https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html But I would like to know if We install a new kolla-ansible(version to upgrade) on the new deployment host, apply changes with password.yml, global.yml and multinode and keep old /etc/kolla/config. Finally, we use kolla-ansible deploy instead of kolla-ansible upgrade. Are these steps ok? Pls correct me if I am wrong. Thank you. Regards Nguyen Huu Khoi
To upgrade, we do this: * upgrade kolla-ansible on the deployment host (pip install "kolla-ansible==11.*") * get the new version's copy of etc_examples/globals.yml * apply settings from our own globals.yml to it * generate and merge passwords * take a backup of the databases with mysqldump for convenience * kolla-ansible -i /etc/ansible/hosts upgrade --limit control We also have a couple of postdeploy scripts we run to ensure our logos are installed and other minor things. We're a little behind the times though - I've just done that today ussuri to victoria. Now continuing with '... upgrade --limit compute-r1' etc to do compute nodes one rack at a time for safety. I wonder how much has changed between victoria and now, and I intend to experience it over the next few months! HTH, Greg. On 13/5/24 22:22, Nguyễn Hữu Khôi wrote:
Hello.
I read this doc about upgrading openstack
https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html>
But I would like to know if
We install a new kolla-ansible(version to upgrade) on the new deployment host, apply changes with password.yml, global.yml and multinode and keep old /etc/kolla/config. Finally, we use kolla-ansible deploy instead of kolla-ansible upgrade.
Are these steps ok? Pls correct me if I am wrong.
Thank you. Regards
Nguyen Huu Khoi
-- Gregory Orange System Administrator, Scientific Platforms Team Pawsey Supercomputing Centre, CSIRO
Hello. I confuse with using deploy and upgrade option when do upgrade. Can you explain what are differences? TY Nguyen Huu Khoi On Tue, May 14, 2024 at 10:14 AM Gregory Orange < gregory.orange@pawsey.org.au> wrote:
To upgrade, we do this:
* upgrade kolla-ansible on the deployment host (pip install "kolla-ansible==11.*") * get the new version's copy of etc_examples/globals.yml * apply settings from our own globals.yml to it * generate and merge passwords * take a backup of the databases with mysqldump for convenience * kolla-ansible -i /etc/ansible/hosts upgrade --limit control
We also have a couple of postdeploy scripts we run to ensure our logos are installed and other minor things.
We're a little behind the times though - I've just done that today ussuri to victoria. Now continuing with '... upgrade --limit compute-r1' etc to do compute nodes one rack at a time for safety. I wonder how much has changed between victoria and now, and I intend to experience it over the next few months!
HTH, Greg.
On 13/5/24 22:22, Nguyễn Hữu Khôi wrote:
Hello.
I read this doc about upgrading openstack
https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html
But I would like to know if
We install a new kolla-ansible(version to upgrade) on the new deployment host, apply changes with password.yml, global.yml and multinode and keep old /etc/kolla/config. Finally, we use kolla-ansible deploy instead of kolla-ansible upgrade.
Are these steps ok? Pls correct me if I am wrong.
Thank you. Regards
Nguyen Huu Khoi
-- Gregory Orange
System Administrator, Scientific Platforms Team Pawsey Supercomputing Centre, CSIRO
I can't tell you in detail, but the 'kolla_action' is what you specify i.e. reconfigure, deploy, upgrade, and that translates to a playbook, called from tasks/main.yml. Each role has tasks/upgrade.yml tasks/deploy.yml etc which you can inspect for the differences. In my case this is in /usr/local/share/kolla-ansible/ansible/roles/ Also, running kolla-ansible by itself gives you a brief description: deploy Deploy and start all kolla containers reconfigure Reconfigure OpenStack service upgrade Upgrades existing OpenStack Environment Also you can look at links like https://docs.openstack.org/project-deploy-guide/kolla-ansible/latest/quickst... https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html On 14/5/24 11:25, Nguyễn Hữu Khôi wrote:
Hello.
I confuse with using deploy and upgrade option when do upgrade. Can you explain what are differences?
TY
Nguyen Huu Khoi
On Tue, May 14, 2024 at 10:14 AM Gregory Orange <gregory.orange@pawsey.org.au <mailto:gregory.orange@pawsey.org.au>> wrote:
To upgrade, we do this:
* upgrade kolla-ansible on the deployment host (pip install "kolla-ansible==11.*") * get the new version's copy of etc_examples/globals.yml * apply settings from our own globals.yml to it * generate and merge passwords * take a backup of the databases with mysqldump for convenience * kolla-ansible -i /etc/ansible/hosts upgrade --limit control
We also have a couple of postdeploy scripts we run to ensure our logos are installed and other minor things.
We're a little behind the times though - I've just done that today ussuri to victoria. Now continuing with '... upgrade --limit compute-r1' etc to do compute nodes one rack at a time for safety. I wonder how much has changed between victoria and now, and I intend to experience it over the next few months!
HTH, Greg.
On 13/5/24 22:22, Nguyễn Hữu Khôi wrote: > Hello. > > I read this doc about upgrading openstack > > https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html> <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html>> > > But I would like to know if > > We install a new kolla-ansible(version to upgrade) on the new deployment > host, apply changes with password.yml, global.yml and multinode and keep > old /etc/kolla/config. Finally, we use kolla-ansible deploy instead of > kolla-ansible upgrade. > > Are these steps ok? Pls correct me if I am wrong. > > Thank you. Regards > > Nguyen Huu Khoi
-- Gregory Orange
System Administrator, Scientific Platforms Team Pawsey Supercomputing Centre, CSIRO
-- Gregory Orange System Administrator, Scientific Platforms Team Pawsey Supercomputing Centre, CSIRO
Hello. Thank you for your response. I get it and I am testing. I have installed new kolla-ansible on a new deployment host and use kolla-ansible upgrade. It worked. If Kollers see my question. pls give me some comments, ty. Nguyen Huu Khoi On Tue, May 14, 2024 at 12:55 PM Gregory Orange < gregory.orange@pawsey.org.au> wrote:
I can't tell you in detail, but the 'kolla_action' is what you specify i.e. reconfigure, deploy, upgrade, and that translates to a playbook, called from tasks/main.yml. Each role has tasks/upgrade.yml tasks/deploy.yml etc which you can inspect for the differences. In my case this is in /usr/local/share/kolla-ansible/ansible/roles/
Also, running kolla-ansible by itself gives you a brief description: deploy Deploy and start all kolla containers reconfigure Reconfigure OpenStack service upgrade Upgrades existing OpenStack Environment
Also you can look at links like
https://docs.openstack.org/project-deploy-guide/kolla-ansible/latest/quickst... https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html
On 14/5/24 11:25, Nguyễn Hữu Khôi wrote:
Hello.
I confuse with using deploy and upgrade option when do upgrade. Can you explain what are differences?
TY
Nguyen Huu Khoi
On Tue, May 14, 2024 at 10:14 AM Gregory Orange <gregory.orange@pawsey.org.au <mailto:gregory.orange@pawsey.org.au>> wrote:
To upgrade, we do this:
* upgrade kolla-ansible on the deployment host (pip install "kolla-ansible==11.*") * get the new version's copy of etc_examples/globals.yml * apply settings from our own globals.yml to it * generate and merge passwords * take a backup of the databases with mysqldump for convenience * kolla-ansible -i /etc/ansible/hosts upgrade --limit control
We also have a couple of postdeploy scripts we run to ensure our logos are installed and other minor things.
We're a little behind the times though - I've just done that today ussuri to victoria. Now continuing with '... upgrade --limit compute-r1' etc to do compute nodes one rack at a time for safety. I wonder how much has changed between victoria and now, and I intend to experience it over the next few months!
HTH, Greg.
On 13/5/24 22:22, Nguyễn Hữu Khôi wrote: > Hello. > > I read this doc about upgrading openstack > >
https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html> <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html
> > But I would like to know if > > We install a new kolla-ansible(version to upgrade) on the new deployment > host, apply changes with password.yml, global.yml and multinode and keep > old /etc/kolla/config. Finally, we use kolla-ansible deploy instead of > kolla-ansible upgrade. > > Are these steps ok? Pls correct me if I am wrong. > > Thank you. Regards > > Nguyen Huu Khoi
-- Gregory Orange
System Administrator, Scientific Platforms Team Pawsey Supercomputing Centre, CSIRO
-- Gregory Orange
System Administrator, Scientific Platforms Team Pawsey Supercomputing Centre, CSIRO
Hi Gregory, I would recommend installing kolla-ansible from Git instead of using PyPI releases. For a release like Victoria which is EOL, you are missing all the bug fixes merged between victoria-em (last PyPI release 11.4.0) and victoria-eol. Best wishes, Pierre Riteau (priteau) On Tue, 14 May 2024 at 05:21, Gregory Orange <gregory.orange@pawsey.org.au> wrote:
To upgrade, we do this:
* upgrade kolla-ansible on the deployment host (pip install "kolla-ansible==11.*") * get the new version's copy of etc_examples/globals.yml * apply settings from our own globals.yml to it * generate and merge passwords * take a backup of the databases with mysqldump for convenience * kolla-ansible -i /etc/ansible/hosts upgrade --limit control
We also have a couple of postdeploy scripts we run to ensure our logos are installed and other minor things.
We're a little behind the times though - I've just done that today ussuri to victoria. Now continuing with '... upgrade --limit compute-r1' etc to do compute nodes one rack at a time for safety. I wonder how much has changed between victoria and now, and I intend to experience it over the next few months!
HTH, Greg.
On 13/5/24 22:22, Nguyễn Hữu Khôi wrote:
Hello.
I read this doc about upgrading openstack
https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html
But I would like to know if
We install a new kolla-ansible(version to upgrade) on the new deployment host, apply changes with password.yml, global.yml and multinode and keep old /etc/kolla/config. Finally, we use kolla-ansible deploy instead of kolla-ansible upgrade.
Are these steps ok? Pls correct me if I am wrong.
Thank you. Regards
Nguyen Huu Khoi
-- Gregory Orange
System Administrator, Scientific Platforms Team Pawsey Supercomputing Centre, CSIRO
Oh really, I hadn't considered that difference - thanks! We'll get to work on testing that. Upgrade to Victoria went flawlessly yesterday (except for one small mistake) for control plane and compute. Now we get to rebuild and upgrade nodes to Ubuntu Focal, and get ready for Wallaby. Now we've made the investment to get properly moved into Kolla Ansible[1], our upgrade sequence is far smoother than before. Regards, Greg. [1] One final hat tip to you Pierre for the excellent https://www.stackhpc.com/migrating-to-kolla.html we used to guide our process there. On 14/5/24 14:59, Pierre Riteau wrote:
Hi Gregory,
I would recommend installing kolla-ansible from Git instead of using PyPI releases. For a release like Victoria which is EOL, you are missing all the bug fixes merged between victoria-em (last PyPI release 11.4.0) and victoria-eol.
Best wishes, Pierre Riteau (priteau)
On Tue, 14 May 2024 at 05:21, Gregory Orange <gregory.orange@pawsey.org.au <mailto:gregory.orange@pawsey.org.au>> wrote:
To upgrade, we do this:
* upgrade kolla-ansible on the deployment host (pip install "kolla-ansible==11.*") * get the new version's copy of etc_examples/globals.yml * apply settings from our own globals.yml to it * generate and merge passwords * take a backup of the databases with mysqldump for convenience * kolla-ansible -i /etc/ansible/hosts upgrade --limit control
We also have a couple of postdeploy scripts we run to ensure our logos are installed and other minor things.
We're a little behind the times though - I've just done that today ussuri to victoria. Now continuing with '... upgrade --limit compute-r1' etc to do compute nodes one rack at a time for safety. I wonder how much has changed between victoria and now, and I intend to experience it over the next few months!
HTH, Greg.
On 13/5/24 22:22, Nguyễn Hữu Khôi wrote: > Hello. > > I read this doc about upgrading openstack > > https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html> <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html>> > > But I would like to know if > > We install a new kolla-ansible(version to upgrade) on the new deployment > host, apply changes with password.yml, global.yml and multinode and keep > old /etc/kolla/config. Finally, we use kolla-ansible deploy instead of > kolla-ansible upgrade. > > Are these steps ok? Pls correct me if I am wrong. > > Thank you. Regards > > Nguyen Huu Khoi
-- Gregory Orange
System Administrator, Scientific Platforms Team Pawsey Supercomputing Centre, CSIRO
-- Gregory Orange System Administrator, Scientific Platforms Team Pawsey Supercomputing Centre, CSIRO
Thanks, I am glad it is still useful 5 years later! On Wed, 15 May 2024 at 02:47, Gregory Orange <gregory.orange@pawsey.org.au> wrote:
Oh really, I hadn't considered that difference - thanks! We'll get to work on testing that. Upgrade to Victoria went flawlessly yesterday (except for one small mistake) for control plane and compute. Now we get to rebuild and upgrade nodes to Ubuntu Focal, and get ready for Wallaby. Now we've made the investment to get properly moved into Kolla Ansible[1], our upgrade sequence is far smoother than before.
Regards, Greg.
[1] One final hat tip to you Pierre for the excellent https://www.stackhpc.com/migrating-to-kolla.html we used to guide our process there.
On 14/5/24 14:59, Pierre Riteau wrote:
Hi Gregory,
I would recommend installing kolla-ansible from Git instead of using PyPI releases. For a release like Victoria which is EOL, you are missing all the bug fixes merged between victoria-em (last PyPI release 11.4.0) and victoria-eol.
Best wishes, Pierre Riteau (priteau)
On Tue, 14 May 2024 at 05:21, Gregory Orange <gregory.orange@pawsey.org.au <mailto:gregory.orange@pawsey.org.au>> wrote:
To upgrade, we do this:
* upgrade kolla-ansible on the deployment host (pip install "kolla-ansible==11.*") * get the new version's copy of etc_examples/globals.yml * apply settings from our own globals.yml to it * generate and merge passwords * take a backup of the databases with mysqldump for convenience * kolla-ansible -i /etc/ansible/hosts upgrade --limit control
We also have a couple of postdeploy scripts we run to ensure our logos are installed and other minor things.
We're a little behind the times though - I've just done that today ussuri to victoria. Now continuing with '... upgrade --limit compute-r1' etc to do compute nodes one rack at a time for safety. I wonder how much has changed between victoria and now, and I intend to experience it over the next few months!
HTH, Greg.
On 13/5/24 22:22, Nguyễn Hữu Khôi wrote: > Hello. > > I read this doc about upgrading openstack > >
https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html> <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html <https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html
> > But I would like to know if > > We install a new kolla-ansible(version to upgrade) on the new deployment > host, apply changes with password.yml, global.yml and multinode and keep > old /etc/kolla/config. Finally, we use kolla-ansible deploy instead of > kolla-ansible upgrade. > > Are these steps ok? Pls correct me if I am wrong. > > Thank you. Regards > > Nguyen Huu Khoi
-- Gregory Orange
System Administrator, Scientific Platforms Team Pawsey Supercomputing Centre, CSIRO
-- Gregory Orange
System Administrator, Scientific Platforms Team Pawsey Supercomputing Centre, CSIRO
I upgraded to openstack today. I just followed @Gregory Orange <gregory.orange@pawsey.org.au> and it worked. For my deployment node, I just install a new one kolla-ansible version then upgrade the cluster. Nguyen Huu Khoi On Wed, May 15, 2024 at 4:18 PM Pierre Riteau <pierre@stackhpc.com> wrote:
Thanks, I am glad it is still useful 5 years later!
On Wed, 15 May 2024 at 02:47, Gregory Orange <gregory.orange@pawsey.org.au> wrote:
Oh really, I hadn't considered that difference - thanks! We'll get to work on testing that. Upgrade to Victoria went flawlessly yesterday (except for one small mistake) for control plane and compute. Now we get to rebuild and upgrade nodes to Ubuntu Focal, and get ready for Wallaby. Now we've made the investment to get properly moved into Kolla Ansible[1], our upgrade sequence is far smoother than before.
Regards, Greg.
[1] One final hat tip to you Pierre for the excellent https://www.stackhpc.com/migrating-to-kolla.html we used to guide our process there.
On 14/5/24 14:59, Pierre Riteau wrote:
Hi Gregory,
I would recommend installing kolla-ansible from Git instead of using PyPI releases. For a release like Victoria which is EOL, you are missing all the bug fixes merged between victoria-em (last PyPI release 11.4.0) and victoria-eol.
Best wishes, Pierre Riteau (priteau)
On Tue, 14 May 2024 at 05:21, Gregory Orange <gregory.orange@pawsey.org.au <mailto:gregory.orange@pawsey.org.au>> wrote:
To upgrade, we do this:
* upgrade kolla-ansible on the deployment host (pip install "kolla-ansible==11.*") * get the new version's copy of etc_examples/globals.yml * apply settings from our own globals.yml to it * generate and merge passwords * take a backup of the databases with mysqldump for convenience * kolla-ansible -i /etc/ansible/hosts upgrade --limit control
We also have a couple of postdeploy scripts we run to ensure our logos are installed and other minor things.
We're a little behind the times though - I've just done that today ussuri to victoria. Now continuing with '... upgrade --limit compute-r1' etc to do compute nodes one rack at a time for safety. I wonder how much has changed between victoria and now, and I intend to experience it over the next few months!
HTH, Greg.
On 13/5/24 22:22, Nguyễn Hữu Khôi wrote: > Hello. > > I read this doc about upgrading openstack > >
https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html < https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html> < https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html < https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html
> > But I would like to know if > > We install a new kolla-ansible(version to upgrade) on the new deployment > host, apply changes with password.yml, global.yml and multinode and keep > old /etc/kolla/config. Finally, we use kolla-ansible deploy instead of > kolla-ansible upgrade. > > Are these steps ok? Pls correct me if I am wrong. > > Thank you. Regards > > Nguyen Huu Khoi
-- Gregory Orange
System Administrator, Scientific Platforms Team Pawsey Supercomputing Centre, CSIRO
-- Gregory Orange
System Administrator, Scientific Platforms Team Pawsey Supercomputing Centre, CSIRO
participants (3)
-
Gregory Orange
-
Nguyễn Hữu Khôi
-
Pierre Riteau