Re: [Libravatar-fans] libravatar system upgrade
Congrats and thank you clime :) Le 11/02/2022 à 15:29, clime a écrit : So it didn't go completely smoothly (python3.9 -> python3.10 upgrade broke libravatar virtualenv, postgresql required postgresql-setup --upgrade, pg_hba.conf recreation needed afterwards, temporal django downgrade needed to version 3) but we made it work eventually. Next time, preparation of the image in advance probably combined with switching to more LTS-based distro might be a good way to go. Best regards clime On Thu, 10 Feb 2022 at 17:10, clime wrote: Hello, There will be a bit of late system upgrade (f33->f35) tomorrow around 13:00 UTC. We don't currently have an optimal way to do it. Normally one would upload a pretested VM image and a switch would be done by changing the DNS address to a newly spawned image while the other is put into read-only mode. We will do the upgrade online this time while some folks (mobrien) from Fedora with access to the AWS console will be watching if anything goes wrong and there is e.g. no ssh access. There will probably therefore be some down-time (a couple of minutes?) with this method. Perhaps we can figure out a better method for future updates. Hopefully everything goes smoothly tomorrow... Best regards clime ___ Mailing list: https://launchpad.net/~libravatar-fans Post to : libravatar-fans@lists.launchpad.net Unsubscribe : https://launchpad.net/~libravatar-fans More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~libravatar-fans Post to : libravatar-fans@lists.launchpad.net Unsubscribe : https://launchpad.net/~libravatar-fans More help : https://help.launchpad.net/ListHelp
Re: [Libravatar-fans] libravatar system upgrade
Again, kudos to you clime++ for running the upgrade / aligning with Fedora ppl to make sure we have some "remote hands" available should it be necessary. Oliver On Fri, Feb 11, 2022 at 3:29 PM clime wrote: > So it didn't go completely smoothly (python3.9 -> python3.10 upgrade > broke libravatar virtualenv, postgresql required postgresql-setup > --upgrade, pg_hba.conf recreation needed afterwards, temporal django > downgrade needed to version 3) but we made it work eventually. > > Next time, preparation of the image in advance probably combined with > switching to more LTS-based distro might be a good way to go. > > Best regards > clime > > On Thu, 10 Feb 2022 at 17:10, clime wrote: > > > > Hello, > > > > There will be a bit of late system upgrade (f33->f35) tomorrow around > > 13:00 UTC. We don't currently have an optimal way to do it. Normally > > one would upload a pretested VM image and a switch would be done by > > changing the DNS address to a newly spawned image while the other is > > put into read-only mode. We will do the upgrade online this time while > > some folks (mobrien) from Fedora with access to the AWS console will > > be watching if anything goes wrong and there is e.g. no ssh access. > > There will probably therefore be some down-time (a couple of minutes?) > > with this method. > > > > Perhaps we can figure out a better method for future updates. > > > > Hopefully everything goes smoothly tomorrow... > > > > Best regards > > clime > > ___ > Mailing list: https://launchpad.net/~libravatar-fans > Post to : libravatar-fans@lists.launchpad.net > Unsubscribe : https://launchpad.net/~libravatar-fans > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~libravatar-fans Post to : libravatar-fans@lists.launchpad.net Unsubscribe : https://launchpad.net/~libravatar-fans More help : https://help.launchpad.net/ListHelp
Re: [Libravatar-fans] libravatar system upgrade
So it didn't go completely smoothly (python3.9 -> python3.10 upgrade broke libravatar virtualenv, postgresql required postgresql-setup --upgrade, pg_hba.conf recreation needed afterwards, temporal django downgrade needed to version 3) but we made it work eventually. Next time, preparation of the image in advance probably combined with switching to more LTS-based distro might be a good way to go. Best regards clime On Thu, 10 Feb 2022 at 17:10, clime wrote: > > Hello, > > There will be a bit of late system upgrade (f33->f35) tomorrow around > 13:00 UTC. We don't currently have an optimal way to do it. Normally > one would upload a pretested VM image and a switch would be done by > changing the DNS address to a newly spawned image while the other is > put into read-only mode. We will do the upgrade online this time while > some folks (mobrien) from Fedora with access to the AWS console will > be watching if anything goes wrong and there is e.g. no ssh access. > There will probably therefore be some down-time (a couple of minutes?) > with this method. > > Perhaps we can figure out a better method for future updates. > > Hopefully everything goes smoothly tomorrow... > > Best regards > clime ___ Mailing list: https://launchpad.net/~libravatar-fans Post to : libravatar-fans@lists.launchpad.net Unsubscribe : https://launchpad.net/~libravatar-fans More help : https://help.launchpad.net/ListHelp
[Libravatar-fans] libravatar system upgrade
Hello, There will be a bit of late system upgrade (f33->f35) tomorrow around 13:00 UTC. We don't currently have an optimal way to do it. Normally one would upload a pretested VM image and a switch would be done by changing the DNS address to a newly spawned image while the other is put into read-only mode. We will do the upgrade online this time while some folks (mobrien) from Fedora with access to the AWS console will be watching if anything goes wrong and there is e.g. no ssh access. There will probably therefore be some down-time (a couple of minutes?) with this method. Perhaps we can figure out a better method for future updates. Hopefully everything goes smoothly tomorrow... Best regards clime ___ Mailing list: https://launchpad.net/~libravatar-fans Post to : libravatar-fans@lists.launchpad.net Unsubscribe : https://launchpad.net/~libravatar-fans More help : https://help.launchpad.net/ListHelp