Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EFB4C14F5F1 for ; Thu, 13 Jun 2024 01:27:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=staff-ietf-org.20230601.gappssmtp.com Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FqRaX5I2vl_W for ; Thu, 13 Jun 2024 01:27:54 -0700 (PDT) Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 581E3C14F5F3 for ; Thu, 13 Jun 2024 01:27:54 -0700 (PDT) Received: by mail-lj1-x231.google.com with SMTP id 38308e7fff4ca-2ebf5b259ffso16837391fa.1 for ; Thu, 13 Jun 2024 01:27:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1718267272; x=1718872072; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=IPWgOGhKrcHVEdz7gOGwkh61tVgy9IuuDnzB3tIZxpM=; b=FcGOaKc8cBvh1IV8FvXH15UsAvQ0yfVtLHsoXNiDYkg1FcWnJtMWCw7xr5L3joF1Yn uWgko6oyk9wV906zU75HgYNLC1J9vwXozpdgLoidby8hd7C6h3+VxWaRlnasFTicS4Ug TktFLeHq51E1XPeG6ql4HTbCgxCnfhqXuXVD0vk89xBRcH84Il2j/puGNWNk1Tjx/Wb5 Rh/YwcYZV0m/oHdEjcsJGuxOTawweut/xGlGwlAmTAUi0qru0pwC0xU15+bU6xV/VnQE 1EAzf9QklH3zTl260dNN5CVtUMXyif9OZ0npVsGGID9aBPPd/xP22JnHdCV3YGvHso39 HB7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718267272; x=1718872072; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=IPWgOGhKrcHVEdz7gOGwkh61tVgy9IuuDnzB3tIZxpM=; b=sMD8P6fp2KVHbhdqpnnlv0ZSNUl0QywZ/nAln9rEtj4qljQ6EypOBm8W4KwsaAN2W7 GwBcBk1MVo7MZYLwBz1cqUmWY27g4eomb1pD18A024LSVGVmh2ObJFboQJbHERLr9OK/ lu8lSYF/G6paw3wGt/ASOrRx4xr7ylMkKrMgRDk1JMM9JJMeovo1NOML25vnWmOwrg/S XF4kfvX7lnebx9091AnF7buQC1vMCwoK3UsPeT7yHCEp7IWfuva7JK/zqT2LFPhPLnms 1W2tEs5K5h/YIclqgaMTZwtDrePi4ejVEeRI9YpCCv668zqGLe+DW8w4giHwIh0kla25 p1/w== X-Gm-Message-State: AOJu0YwuEHT5NdADE3F2P8hQijXEiF3toRdtzptkFqYafCbQpbcUCmj/ zgnda9OzSC2Ch6jmYApZpEunDMe2miTdbA1UmEjHQ239wWHyE0v9QING+VRH3f5ag1dhVCHR06F EQiJ0vtEH4mDGjq6Xpt5bG/Lz7jLbU+M46mdSeVBj X-Google-Smtp-Source: AGHT+IE5l26fGUTilnbNUCIdjJecEnM2am2kPCtvjipsP1OCs8Q0oRMUR1X/gs3QN6K+OFSvKZanW4E0KGvBCKwL+Ts= X-Received: by 2002:a05:6512:461:b0:52c:9dcf:b1e0 with SMTP id 2adb3069b0e04-52ca02503b7mr513821e87.27.1718267272101; Thu, 13 Jun 2024 01:27:52 -0700 (PDT) MIME-Version: 1.0 References: <589f9aad-52fe-4063-ab67-304cbab570e8@nostrum.com> In-Reply-To: From: Nicolas Giard Date: Thu, 13 Jun 2024 04:27:41 -0400 Message-ID: To: Corinne Cath Content-Type: multipart/alternative; boundary="000000000000621f77061ac14630" Message-ID-Hash: WP4WDA3CZP7GQXSLNQTXDZJU7FVBNJUW X-Message-ID-Hash: WP4WDA3CZP7GQXSLNQTXDZJU7FVBNJUW X-MailFrom: nick@staff.ietf.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: tools-discuss , IETF discussion list X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5BTools-discuss=5D_Re=3A_Key_IETF_service_outages_during_transiti?= =?utf-8?q?on_to_new_infrastructure_on_20_June?= List-Id: IETF Tools Discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000621f77061ac14630 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Corinne, DigitalOcean and Microsoft Azure are the 2 main cloud providers (kubernetes/compute, databases, storage, etc). Networking / CDN services are Cloudflare. Mail services are on AWS. Nick On Thu, Jun 13, 2024 at 3:36=E2=80=AFAM Corinne Cath wrote: > Hi all=E2=80=94 > > I was looking for who the provider is of this new cloud infrastructure bu= t > could not find any details. > > However I=E2=80=99m well aware i might have missed earlier emails. > > If anyone could point me in the right direction, that would be much > appreciated. > > Kind regards, > > Dr. Corinne Cath > =E2=80=8BMinderoo Centre for Technology & Democracy, University of Cambri= dge =E2=80=8B > Web: www.mctd.ac.uk/team-members/corinne-cath/ & www.corinnecath.com > Twitter: @C__CS > Mastodon: @C__CS@someone.elses.computer > > > On Wed, Jun 12, 2024 at 17:04 Robert Sparks wrote: > >> As part of moving to a new cloud infrastructure, the IETF Datatracker an= d >> related services will be unavailable starting at 1800 UTC on Thursday 20 >> June. The outages are expected to last no more than 4 hours; updates wil= l >> be posted when availability resumes. >> >> The following services will transition to the new cloud infrastructure: >> >> =E2=80=A2 the IETF Datatracker, >> >> =E2=80=A2 the www.ietf.org website, >> >> =E2=80=A2 the IETF Mailarchive, and >> >> =E2=80=A2 the IMAP and rsync services. >> >> IMPORTANT: Please do not plan to rely on the IETF Datatracker or the >> affected systems during the 4-hour window starting at 1800 UTC on Thursd= ay >> 20 June. >> >> Any service that relies on IETF Datatracker also will be affected. The >> following services will not be available: >> >> =E2=80=A2 the IETF meeting registration system, and >> >> =E2=80=A2 any interim meeting sessions that use MeetEcho integrated w= ith the >> IETF Datatracker. >> >> The following services will be impaired, with any features requiring >> logging in unavailable: >> >> =E2=80=A2 the IETF Notes service (editing notes will not be possible) >> >> =E2=80=A2 IETF wikis, including wiki.ietf.org and chairs.ietf.org (ed= iting >> wiki pages will not be possible) >> >> =E2=80=A2 The IETF Zulip service (any new connection will not work) >> >> OF PARTICULAR NOTE: Posting Internet-Drafts (I-Ds) to the IETF repositor= y >> will be unavailable during the outage; this includes automated posting o= f >> I-Ds via the IETF Datatracker API, such as via Github actions in >> repositories used to develop I-Ds. >> >> Please see this blog post for more details: >> >> https://www.ietf.org/blog/it-infrastructure-outage-2024-06-20/ >> >> The blog post will be updated once this phase of the IT infrastructure >> transition is complete. >> >> RjS >> >> IETF Tools Project Manager >> > ----------------------------------------------- > Tools-discuss mailing list -- tools-discuss@ietf.org > To unsubscribe send an email to tools-discuss-leave@ietf.org > https://mailarchive.ietf.org/arch/browse/tools-discuss/ --000000000000621f77061ac14630 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Corinne,

DigitalOcean and Micr= osoft Azure are the 2 main cloud providers (kubernetes/compute, databases, = storage, etc).
Networking / CDN services are Cloudflare.
Mail= services are on AWS.

Nick

On Thu, Jun 13, 20= 24 at 3:36=E2=80=AFAM Corinne Cath <corinnecath@gmail.com> wrote:
Hi all=E2=80=94=C2=A0

I was looking for who the provide= r is of this new cloud infrastructure but could not find any details.
=

However I=E2=80=99m well awar= e i might have missed earlier emails.

If anyone could point me in the right direction, that would b= e much appreciated.

Kind= regards,=C2=A0

Dr. Corinne Cath
=E2=80=8BMinderoo Centre for Technology = & Democracy, University of Cambridge =E2=80=8B
<= div style=3D"color:rgb(34,34,34)">Web:=C2=A0<= a href=3D"http://www.mctd.ac.uk/team-members/corinne-cath/" style=3D"font-f= amily:tahoma,sans-serif;color:rgb(17,85,204)" target=3D"_blank">www.mctd.ac= .uk/team-members/corinne-cath/=C2=A0&=C2=A0www.corinnecath.com
Twitter: @C__CS=C2=A0
Mastodon: @C__CS@someone.el= ses.computer=C2=A0

=
On Wed= , Jun 12, 2024 at 17:04 Robert Sparks <rjsparks@nostrum.com> wrote:
=20 =20 =20

As part of moving to a new cloud infrastructure, the IETF Datatr= acker and related services will be unavailable starting at 1800 UTC on Thur= sday 20 June. The outages are expected to last no more than 4 hours; update= s will be posted when availability resumes.


The following servic= es will transition to the new cloud infrastructure:


=C2=A0=C2=A0=C2=A0= =E2=80=A2 the IETF Datatracker,=C2=A0

=C2=A0=C2=A0=C2=A0= =E2=80=A2 the www.ietf.org website,

=C2=A0=C2=A0=C2=A0= =E2=80=A2 the IETF Mailarchive, and

=C2=A0=C2=A0=C2=A0= =E2=80=A2 the IMAP and rsync services.


IMPORTANT: Please do= not plan to rely on the IETF Datatracker or the affected systems during th= e 4-hour window starting at 1800 UTC on Thursday 20 June.


Any service that rel= ies on IETF Datatracker also will be affected. The following services will = not be available:


=C2=A0=C2=A0=C2=A0= =E2=80=A2 the IETF meeting registration system, and

=C2=A0=C2=A0=C2=A0= =E2=80=A2 any interim meeting sessions that use MeetEcho integrated with th= e IETF Datatracker.


The following servic= es will be impaired, with any features requiring logging in unavailable:


=C2=A0=C2=A0=C2=A0= =E2=80=A2 the IETF Notes service (editing notes will not be possible)

=C2=A0=C2=A0=C2=A0= =E2=80=A2 IETF wikis, including wiki.ietf.org and chairs.ietf.org (editing wiki pages will not be possible)

=C2=A0=C2=A0=C2=A0= =E2=80=A2 The IETF Zulip service (any new connection will not work)<= /p>

OF PARTICULAR NOTE: = Posting Internet-Drafts (I-Ds) to the IETF repository will be unavailable d= uring the outage; this includes automated posting of I-Ds via the IETF Data= tracker API, such as via Github actions in repositories used to develop I-D= s.


Please see this blog= post for more details:


https://www.ietf.org/blog/it-infrastr= ucture-outage-2024-06-20/=C2=A0


The blog post will b= e updated once this phase of the IT infrastructure transition is complete.<= /span>


RjS


IETF Tools P= roject Manager

-----------------------------------------------
Tools-discuss mailing list -- tools-discuss@ietf.org
To unsubscribe send an email to tools-discuss-leave@ietf.org
https://mailarchive.ietf.org/arch/browse/tool= s-discuss/ --000000000000621f77061ac14630--