![](https://seccdn.libravatar.org/avatar/fff0f38e92656c8a636916213eb952c4.jpg?s=120&d=mm&r=g)
Hello Lars, On Wed, 18 Mar 2020, Lars Vogdt wrote:
While... on the other hand... now that we have a prove of concept that we can upgrade tumbleweed machines... If you don't mind, I want to put this machine on a list of "run zypper dup once a month". If we check right afterward that everything still works as expected (=> Monitoring: just tell me what we should check) we should be ready to go. Worst thing would be that we might loose a few hours, if we notice early enough that something is broken and we need to revert to a former snapshot state.
The two important "services" on that would be a simple HTTPS check on some random URL, let's say https://gcc.opensuse.org/ (better would be https://gcc.opensuse.org/gcc-old/SPEC/CINT/sb-czerny-head-64-2006/recent.htm... but the 'gcc-old' part at least changed once over the last 15 years, so it's only semi-stable), and a check that would verify rsync via ssh access (that is what got broken, the webserver continued to work), from inside the SUSE network. I don't know if you have the capability to do such checking. (I could add a ssh key for that purpose). Ciao, Michael. -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org