From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Planned maintenance - Friday, July 14th, 2020 - 1 pm UTC
Date: Fri, 17 Jul 2020 11:00:05 +0100 [thread overview]
Message-ID: <2B5AD9B1-A796-450B-8BD9-E5CDB308E52E@ipfire.org> (raw)
In-Reply-To: <8BE46EF2-20FA-4CB3-A2A9-429E23CCE160@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
As Arne pointed out to me today, the date was utterly wrong. Thank you.
It was meant to be Friday, the 17th. Today.
-Michael
> On 14 Jul 2020, at 14:50, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>
> This Friday, from around 1 pm UTC, we will conduct some server maintenance in our primary data centre in Hanover, Germany.
>
> Since our servers in that data centre are at a certain age now, we are replacing them both one after the others. All virtual machines will have to run on the remaining node while we replace the first server this Friday and the second server will be replaced at a later date.
>
> Since the old servers run on harddrives, there will be degraded performance from now on until we have moved machines back across both nodes. Therefore, from Wednesday, I will start shutting down some servers that are not urgently needed - those include the builders for the nightly builds as well as personal build services.
>
> On Friday afternoon, there will also be a complete downtime of all services since we have to perform some physical work on the primary firewall. Hopefully this won’t be longer than 30 minutes.
>
> I apologise for the inconvenience.
>
> Best,
> -Michael
prev parent reply other threads:[~2020-07-17 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 13:50 Michael Tremer
2020-07-17 10:00 ` Michael Tremer [this message]
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=2B5AD9B1-A796-450B-8BD9-E5CDB308E52E@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox