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: Fri, 2 Jun 2023 09:53:13 +0200 [thread overview]
Message-ID: <202534aa-a40a-5ac7-3fba-32c30cfc4a04@collabora.com> (raw)
In-Reply-To: <e89a3f40-e719-c3c2-6c7e-ffb1706ad380@collabora.com>
On 01/06/2023 14:21, Guillaume Tucker wrote:
> On 30/05/2023 10:12, Guillaume Tucker wrote:
>> We're now in the process of moving all the KernelCI Azure
>> services to a new subscription. The domain names, port numbers
>> etc. should remain unchanged, there will only be new IP addresses
>> for the new VMs and DNS records should be updated in a timely
>> fashion.
>>
>> As such, the staging VM is being shut down today. We'll be
>> sharing updates as things on staging come back online by the end
>> of this week at the latest. Services impacted by this downtime
>> are:
>>
>> * https://staging.kernelci.org (web dashboard, backend, Jenkins etc.)
>> * https://staging.kernelci.org:9000 (new API & Pipeline)
>> * https://kcidb.kernelci.org (KCIDB Grafana web dashboard)
>> * https://chromeos.kernelci.org (ChromeOS KernelCI instance)
>
> We've made some good progress with transferring the staging VMs
> and services are coming back online now. In principle all of
> staging should be back to normal by tomorrow.
All the staging services are now back online and jobs are running
as expected, both the old Jenkins and the new pipeline.
>> 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.
Thanks,
Guillaume
next prev parent reply other threads:[~2023-06-02 7:52 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 [this message]
2023-06-02 17:08 ` Guillaume Tucker
2023-06-06 21:17 ` Guillaume Tucker
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=202534aa-a40a-5ac7-3fba-32c30cfc4a04@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