From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] dns entries for talos server & server maintenance
Date: Fri, 22 May 2020 23:54:49 +0100
Message-ID: <CAPweEDxxSdP8c7gDdWUidkwvH8diP1jYhqX==R5O7kG74N7CNw@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD6+fOdpdaNJBL9O_TkMVMyQ8SrnqzJWbUMTMx+Ct-O=ew@mail.gmail.com>
On Fri, May 22, 2020 at 10:21 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> to make it easier to connect to without having to remember the IP
> address, I think we should add a dns entry for the talos server, I'd
> suggest talos1.libre-soc.org. As a reminder, the IP address is
> 23.155.224.75
good idea.
> Also, someone forgot to enable automatic updates,
no, it was not "forgotten" - the absolute last thing we need is
"automatically introduced problems", particularly if - especially as -
the setup is using debian/testing.
debian/stable and "production" servers with carefully pre-planned
setups, or "toys" where nobody else is relying on it, or "your own
personal machine" is absolutely fine to enable potentially-damaging
"automatic updates".
> so I updated the
> software manually. Sorry if that broke something.
yes please don't do that without consulting everyone, first.
to give you some idea: the notification schedule that servers used to
be on at Imperial College was 90 days advance warning of softtware
updates, and one year for a reboot.
> The server needs to be rebooted to use the new kernel that got
> installed,
which is precisely why you don't "upgrade" a server, especially
without notice or discussion. we are now critically dependent on that
machine having 100% uninterrupted power.
if there is a power-outage in the data centre that causes an
unscheduled reboot, resulting in that machine going down, and we are
critically reliant on it for testing at the time, someone has to drop
everything they're doing, scramble to look up the procedure for
logging in to the virtual console, and then work out how to recover
the machine.
> so, Luke, I'll let you do that since you have stuff running
> on it.
no, i'm not going to reboot it, because if it doesn't come back up
someone has to spend the time recovering it.
lesson learned: never "upgrade" servers without consulting people, ok?
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 21:21 Jacob Lifshay
2020-05-22 22:54 ` Luke Kenneth Casson Leighton [this message]
2020-05-22 23:01 ` Luke Kenneth Casson Leighton
2020-05-22 23:06 ` Luke Kenneth Casson Leighton
2020-05-23 1:08 ` Jacob Lifshay
2020-05-23 2:46 ` Luke Kenneth Casson Leighton
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPweEDxxSdP8c7gDdWUidkwvH8diP1jYhqX==R5O7kG74N7CNw@mail.gmail.com' \
--to=lkcl@lkcl.net \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git