From: raingloom@riseup.net
To: Guix Devel <guix-devel@gnu.org>
Subject: watchdog triggered auto-rollback
Date: Fri, 24 May 2024 12:50:47 +0000 [thread overview]
Message-ID: <5521e876c1944cf001dd4cac4553f738@riseup.net> (raw)
Since I've been experimenting with a foolproof unikernel based static
website deployment lately, I realized I should write down this idea I've
been chewing for a while:
It would be very nice to have automatic system rollbacks when certain
things break.
One example is broken SSH config that makes a machine unreachable.
Local testing is useful, but like in the SSH example, some issues only
become apparent when you are deploying to the production environment.
Would others find this useful? Where in the stack would this be solved?
Could we, for example, catch an issue in the init system and still
perform a rollback? Or if not a full rollback, then at least a reboot
into the previous config? (And if that is also broken, then the one
before, etc, etc)
Obviously there are a lot of edge cases and potential bugs in this
mechanism as well. Sticking with the SSH example, rolling back to a
version that was kept around where the authorized keys are different
would also make the machine unreachable via SSH.
next reply other threads:[~2024-05-24 12:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 12:50 raingloom [this message]
2024-05-25 16:58 ` watchdog triggered auto-rollback Richard Sent
-- strict thread matches above, loose matches on Subject: below --
2024-05-28 0:52 Nathan Dehnel
2024-05-28 1:46 ` Richard Sent
2024-05-28 10:10 ` Attila Lendvai
2024-05-29 13:45 ` Richard Sent
2024-05-29 20:41 ` Attila Lendvai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5521e876c1944cf001dd4cac4553f738@riseup.net \
--to=raingloom@riseup.net \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).