[Tools-discuss] Re: Key IETF service outages during transition to new infrastructure on 20 June

Jay Daley <exec-director@ietf.org> Thu, 13 June 2024 09:30 UTC

Return-Path: <jay@staff.ietf.org>
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 A6FBAC14F5EF for <tools-discuss@ietfa.amsl.com>; Thu, 13 Jun 2024 02:30:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 AEytfPirVEI4 for <tools-discuss@ietfa.amsl.com>; Thu, 13 Jun 2024 02:30:06 -0700 (PDT)
Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (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 61EC4C14F5EB for <tools-discuss@ietf.org>; Thu, 13 Jun 2024 02:30:06 -0700 (PDT)
Received: by mail-wm1-x32a.google.com with SMTP id 5b1f17b1804b1-42179dafd6bso11904525e9.0 for <tools-discuss@ietf.org>; Thu, 13 Jun 2024 02:30:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1718271004; x=1718875804; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=wJoUjojZHcmwAdSolu8EoFpCe6uGg/dzindKU11oeJs=; b=M1jdseaSPTAKDCywxPa641d8s5JzdMsp7We9o7l6U6DbCeep6lBM5jG4YlLxSahBCS W5QU9VB6cfpjWG/9Lm2oxp8zRZfu7t/fgYkRgEpVIB4eYtAe5eDUB9rxAUbBhfMyNsdg ulmTJswUCWj12DXD8sNEZ35OhlK9K1bN5tHX+a5o7wT/BWlZqKegQMRQ9gcZNDwYRY3V fnaw5JOKjiu/Y7/qn2P8dNKIHoSqouuIeGrFmpepZqh4mDha4C+aVGS2ljeiDG8dC14E M79E/utaMRK/tXgqRbZsQ+bjKG4y77lsBH4RHD3WXiHRzmPT1xZXZnwDSXaanwMDCVzY 08fA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718271004; x=1718875804; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=wJoUjojZHcmwAdSolu8EoFpCe6uGg/dzindKU11oeJs=; b=uIHTV306HUn/wKY7Q/koFq+YxSHJ1Msm9CzrcuSzJQ4+tJwQsY+piJfGBfvifzHlnp joxS3sakCo5iiqL6QJpc6cx8XvL5kD/GhgnAUwkHlq4MGQ/CCUQYxcNq4k67eAIPvH5R 8HBQouWvauKTplLwpSsGE0ob8ZUixSLDF0CnBOy/hjvVb5cKKLM9LAGFQB72+7sn5c+l AaZQDYdmTytzNxd5u03NaYesZoqebiKaAjDllBsUmrH9YfnlKXDQJhpwg/NjnWi7ISYr CpdeBq/h/Xi5N3cE7eXD2ZjKFnixvM9pO9dogLijxBuZAL3fsa1Ua5KyIIuMlBQL97RU TZJg==
X-Gm-Message-State: AOJu0YxFH2Vh1AZY9QNKhbTXZ3C5cEpc5i6H3t4MMauQ3CDCb8IgeU4o E4goBVlkXoGwqQEWLu4kZhmeq5QrVD/kc3rQgG/lDLzF5XIP+qWNFFHORqFdSOFUkA==
X-Google-Smtp-Source: AGHT+IERwvybdtPPINBk8NqwHekHtzhcKuQ3R7sjZ2acbuvnk3cIo/lkPR6kedbHucr0nI18oKAPuA==
X-Received: by 2002:a05:600c:4506:b0:421:392b:7e13 with SMTP id 5b1f17b1804b1-422b6dc80c2mr22319545e9.4.1718271004181; Thu, 13 Jun 2024 02:30:04 -0700 (PDT)
Received: from smtpclient.apple (host-92-27-125-209.static.as13285.net. [92.27.125.209]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-3607509c8b7sm1132733f8f.26.2024.06.13.02.30.03 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Jun 2024 02:30:03 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <CAL_px1MQPxOREzW_m6HzGL3PpxRg60Zvywv9JpHm5JHAZ79=iw@mail.gmail.com>
Date: Thu, 13 Jun 2024 10:29:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F0F894E-D93B-42F4-A9A3-01989699CBD1@ietf.org>
References: <589f9aad-52fe-4063-ab67-304cbab570e8@nostrum.com> <CAD499eLXiZOsDN4rdwMNv2YeqF5w1MbLbayeXbjJ1e7WZd4WnA@mail.gmail.com> <CAL_px1MQPxOREzW_m6HzGL3PpxRg60Zvywv9JpHm5JHAZ79=iw@mail.gmail.com>
To: Corinne Cath <corinnecath@gmail.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Message-ID-Hash: LYDYLW5IEGH2PNCBQ6MDT2RK7RLCBINH
X-Message-ID-Hash: LYDYLW5IEGH2PNCBQ6MDT2RK7RLCBINH
X-MailFrom: jay@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 <tools-discuss@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Tools-discuss] Re: Key IETF service outages during transition to new infrastructure on 20 June
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/cgFDV9S-3ZR9qESXeL5ayFqjdAE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>

(Dropped ietf@)

HI Corinne 

To add to what Nick said - this level of detail is covered during the monthly community tools calls, the most recent of which was two days ago.  These meetings are announced to this list and have a detailed agenda, such as https://datatracker.ietf.org/group/tools/meetings/ for the last one.

Jay

> On 13 Jun 2024, at 09:27, Nicolas Giard <nick@staff.ietf.org> wrote:
> 
> 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 AM Corinne Cath <corinnecath@gmail.com> wrote:
> Hi all— 
> 
> I was looking for who the provider is of this new cloud infrastructure but could not find any details.
> 
> However I’m 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
> ​Minderoo Centre for Technology & Democracy, University of Cambridge ​
> 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 <rjsparks@nostrum.com> wrote:
> As part of moving to a new cloud infrastructure, the IETF Datatracker and 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 will be posted when availability resumes.
> 
> The following services will transition to the new cloud infrastructure:
> 
>    • the IETF Datatracker, 
>    • the www.ietf.org website,
>    • the IETF Mailarchive, and
>    • 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 Thursday 20 June.
> 
> Any service that relies on IETF Datatracker also will be affected. The following services will not be available:
> 
>    • the IETF meeting registration system, and
>    • any interim meeting sessions that use MeetEcho integrated with the IETF Datatracker.
> 
> The following services will be impaired, with any features requiring logging in unavailable:
> 
>    • the IETF Notes service (editing notes will not be possible)
>    • IETF wikis, including wiki.ietf.org and chairs.ietf.org (editing wiki pages will not be possible)
>    • The IETF Zulip service (any new connection will not work)
> 
> OF PARTICULAR NOTE: Posting Internet-Drafts (I-Ds) to the IETF repository will be unavailable during the outage; this includes automated posting of 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/

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org