From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: "kernelci@lists.linux.dev" <kernelci@lists.linux.dev>
Cc: "kernelci-sysadmin@groups.io" <kernelci-sysadmin@groups.io>
Subject: Re: Scheduled maintenance this week and next week
Date: Tue, 6 Jun 2023 23:17:16 +0200 [thread overview]
Message-ID: <554e1510-4c48-5074-4e6b-faecec6a4364@collabora.com> (raw)
In-Reply-To: <607da614-ecda-a47f-94e3-0fad2e951f00@collabora.com>
On 02/06/2023 19:08, Guillaume Tucker wrote:
> On 02/06/2023 09:53, Guillaume Tucker wrote:
>>>> Once the staging move is complete, all the production services
>>>> are scheduled to be moved next week:
>>>>
>>>> * https://kernelci.org (static website)
>>>> * https://linux.kernelci.org (web dashboard, backend, Jenkins etc.)
>>> Also:
>>>
>>> * https://chromeos.kernelci.org (ChromeOS KernelCI instance)
>>>
>>>> There may be some longer downtime next Monday compared with usual
>>>> weekly production deployments. We'll also be sending regular
>>>> updates as things evolve.
>>>>
>>>> Please let us know if this downtime is causing any critical
>>>> disruption and we'll see which measures we can take to mitigate
>>>> the impact.
>> We've now started transferring VMs for the production move. It's
>> still scheduled to happen on Monday as per the usual production
>> updates, except this time we won't be updating any of the code to
>> focus solely on the infrastructure. If things to well, the
>> downtime shouldn't last more than a couple of hours. We'll soon
>> confirm the exact time window for the downtime and provide
>> regular updates.
>
> There is now a scheduled maintenance window on Tuesday 6th June
> from 18:00 UTC to 22:00 UTC when the kernelci.org production
> services will be down as part of the move to the new Azure
> subscription. If things go well, the downtime may be shorter.
> There should be no downtime on Monday.
The planned maintenance window is meant to end within 1h, however
we've experienced some complications and it looks like it will
take longer to get all the services back online. As it's nearing
completion we've opted for extending the maintenance window in
the hope that it gets resolved within the next couple of hours or
so. We'll send an update once things have settled down.
Thank you for your understanding.
Best wishes,
Guillaume
next prev parent reply other threads:[~2023-06-06 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 8:12 Scheduled maintenance this week and next week Guillaume Tucker
2023-06-01 12:21 ` Guillaume Tucker
2023-06-02 7:53 ` Guillaume Tucker
2023-06-02 17:08 ` Guillaume Tucker
2023-06-06 21:17 ` Guillaume Tucker [this message]
2023-06-07 1:00 ` [kernelci-sysadmin] " Vince Hillier
2023-06-11 7:42 ` Vince Hillier
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=554e1510-4c48-5074-4e6b-faecec6a4364@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=kernelci-sysadmin@groups.io \
--cc=kernelci@lists.linux.dev \
/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