Planned IETF Maintenance Outage, Friday August 5th

Glen <glen@amsl.com> Thu, 28 July 2016 22:22 UTC

Return-Path: <glen@amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7A1E12D953 for <ietf-announce@ietfa.amsl.com>; Thu, 28 Jul 2016 15:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.908
X-Spam-Level:
X-Spam-Status: No, score=-103.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yaZnTy1otL4g for <ietf-announce@ietfa.amsl.com>; Thu, 28 Jul 2016 15:22:27 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18AEC12D911 for <ietf-announce@ietf.org>; Thu, 28 Jul 2016 15:22:27 -0700 (PDT)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id 2FEF91E5D73 for <ietf-announce@ietf.org>; Thu, 28 Jul 2016 15:19:49 -0700 (PDT)
Received: from mail-qt0-f180.google.com (mail-qt0-f180.google.com [209.85.216.180]) by c8a.amsl.com (Postfix) with ESMTPSA id E20151E5D63 for <ietf-announce@ietf.org>; Thu, 28 Jul 2016 15:19:48 -0700 (PDT)
Received: by mail-qt0-f180.google.com with SMTP id x25so57036949qtx.2 for <ietf-announce@ietf.org>; Thu, 28 Jul 2016 15:22:26 -0700 (PDT)
X-Gm-Message-State: AEkoouuqA9dHWSvCtY12MMSyKsWvWDPxfKaHUOYovtLHaCUilgfML0XILycq6BfgOWNxM5vvPQCA3Y84Um/Ksw==
X-Received: by 10.237.45.135 with SMTP id i7mr62745678qtd.30.1469744545908; Thu, 28 Jul 2016 15:22:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.88.105 with HTTP; Thu, 28 Jul 2016 15:22:06 -0700 (PDT)
From: Glen <glen@amsl.com>
Date: Thu, 28 Jul 2016 15:22:06 -0700
X-Gmail-Original-Message-ID: <CABL0ig4jY6hnJyz7BEHUdRYiLck9PEkoJ-RPUzn6OwB26uDifQ@mail.gmail.com>
Message-ID: <CABL0ig4jY6hnJyz7BEHUdRYiLck9PEkoJ-RPUzn6OwB26uDifQ@mail.gmail.com>
Subject: Planned IETF Maintenance Outage, Friday August 5th
To: ietf-announce@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/AIBnCBk65KyM2gEzDq32DJqGW2Y>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org, glen@amsl.com
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2016 22:22:28 -0000

All -

I am planning a maintenance outage for Friday August 5th, in order to
perform physical hardware upgrades, and driver and BIOS updates, on
the IETF primary production server.

I plan to start the upgrade process at 1600 PDT / 1900 EDT / 2300 GMT
on that Friday evening.

During the outage, the IETF main websites, including the IAB and IRTF
sites, the IETF's primary systems and tools, including the Datatracker
and Mailman, and IETF/IAB/IRTF email aliases and lists will be offline
and unavailable.

The RFC-Editor, ISOC Lists, and other AMS-hosted services are
separate, and not a part of this outage.

The Tools servers hosted by Henrik Levkowetz are separate, and not a
part of this outage.

Based on the length of time it took to upgrade identical backup
servers, I expect that the outage will last about 90 minutes.

I will send an additional reminder out roughly 8 hours before starting
the upgrade process.

Thank you in advance for your patience during this process.  As
always, if you have any questions, please let me know.

Glen
Glen Barney
IT Director
AMS (IETF Secretariat)