| noonedeadpunk | well, endpoints should be updated with today's module at very least | 07:21 |
|---|---|---|
| noonedeadpunk | you'd need to run setup-openstack.yml --tags common-service for that though | 07:21 |
| noonedeadpunk | about let's encrypt - you might want to wipe out /etc/letsencrypt to remove renewal hooks for old domain before adding the new one. | 07:22 |
| noonedeadpunk | though I personally never had such scenario, but in theory it should not be very quirky | 07:23 |
| f0o | I guess I know what I'll do today :D | 07:50 |
| f0o | I'm still on tag 2023.2 - with today's module you mean 2024.1 ? | 07:50 |
| noonedeadpunk | 2023.2 should work ok as well | 07:51 |
| noonedeadpunk | just in case you're on train or something, lol | 07:51 |
| f0o | technically I should also explore how to upgrade between tags sooner or later... I guess it might be as simple as updating my tag and just rerun all books? | 07:52 |
| f0o | oh hey there's a ./scripts/run-upgrade.sh - that's probably what I want :D | 07:56 |
| f0o | should I path from 2023.2 -> 2024.1 -> 2024.2 or is it safe to jump directly to latest? | 07:57 |
| f0o | basically, can I postpone upgrade until the release hits EOL and then jump to whatever is current at that point or should I upgrade to the closest release as soon as possible | 07:58 |
| noonedeadpunk | so run_upgrade has supported upgrade paths. But basically you can jump only between nearest releases or nearest SLURP releases | 08:23 |
| noonedeadpunk | meaining you can do 2023.1 (SLURP) -> 2024.1 (SLURP) or 2023.1(SLURP) -> 2023.2 -> 2024.1 (SLURP) | 08:23 |
| noonedeadpunk | so if you;d want to jump through releases, I'd suggest to upgrade to 2024.1, and then you will be able to do direct upgrade to 2025.1 | 08:24 |
| noonedeadpunk | also there's a doc for upgrade: https://docs.openstack.org/openstack-ansible/latest/admin/upgrades/major-upgrades.html | 08:24 |
| noonedeadpunk | just ensure you have selected correct target release for the doc | 08:25 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-plugins master: Combine vars files for debian/ubuntu and ensure setuptools is present https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/924692 | 08:28 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-openstack_hosts master: Ensure python3-packaging is installed for distros https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/924994 | 08:35 |
| frickler | noonedeadpunk: this is my list of branches now that I'd tag eol and delete once you confirm them https://etherpad.opendev.org/p/osa-branch-cleanup | 08:48 |
| frickler | noonedeadpunk: you're also still free to add permissions in gerrit for you or some other volunteer to do this yourselves, but given that (at least I hope so) this is a one-off action, this way should be the easiest | 08:49 |
| noonedeadpunk | frickler: yep, the list looks quite fair to me! | 08:55 |
| opendevreview | Merged openstack/openstack-ansible-repo_server master: Replace Nginx with Apache2 https://review.opendev.org/c/openstack/openstack-ansible-repo_server/+/924162 | 09:20 |
| deflated | Hi people, trying to deploy tls for the backend, how do i deploy official certs and not self signed ones? is there a tag i can pass ..multinoide certificates or use the same cert as for internal? Can't seem to figure it out without seeing some kind of error regarding ssl in the attempted deployment | 10:08 |
| frickler | noonedeadpunk: done, let me know if there are any issues or other missing cleanups | 10:45 |
| f0o | ty noonedeadpunk ! | 11:18 |
| noonedeadpunk | frickler: sure, thanks a ton! | 11:29 |
| mgariepy | rabbitmq pkg are such a mess. | 17:21 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!