Re: Major upgrade to the IETF Datatracker

IETF Chair <chair@ietf.org> Sat, 25 February 2012 18:21 UTC

Return-Path: <chair@ietf.org>
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 A9E8821F85C6; Sat, 25 Feb 2012 10:21:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nooiOkKzI72m; Sat, 25 Feb 2012 10:21:51 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id DCFEB21F85C3; Sat, 25 Feb 2012 10:21:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id C467712C8BF; Sat, 25 Feb 2012 10:21:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q4a5DRSDtbVV; Sat, 25 Feb 2012 10:21:51 -0800 (PST)
Received: from [192.168.2.107] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) by c8a.amsl.com (Postfix) with ESMTPSA id 2C64B12C88E; Sat, 25 Feb 2012 10:21:51 -0800 (PST)
Subject: Re: Major upgrade to the IETF Datatracker
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: IETF Chair <chair@ietf.org>
In-Reply-To: <3848B9FF-5F07-42A2-B4AE-06A4567CB143@ietf.org>
Date: Sat, 25 Feb 2012 13:21:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <54733A77-6D00-46A9-9F2C-4C571D4E7D67@ietf.org>
References: <E50AF16F-60A4-48AC-9B39-ED8E3560FB24@ietf.org> <3848B9FF-5F07-42A2-B4AE-06A4567CB143@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF WG Chairs <wgchairs@ietf.org>, IAOC <iaoc@ietf.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: <http://www.ietf.org/mail-archive/web/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: Sat, 25 Feb 2012 18:21:52 -0000

There were a few surprises during the Datatracker database conversion that caused it to take longer than planned, but in the end the conversion was successful.

At 07:01 PST the Datatracker was switched to the converted database.  So far, everything looks good.  Of course, we are keeping an eye out to look for potential problems.

A very heartfelt thank you to Henrik Levkowetz, Ole Laursen, and Ryan Cross for their extra efforts during the conversion.

Russ

On Feb 24, 2012, at 4:21 PM, IETF Chair wrote:

> Thanks for all of the testing.  Several bugs were found and fixed.  At this time there are no show stopper bugs, so we will convert to the new Datatracker database this weekend.  Of course, to be prudent, we will run a complete backup before we being the database conversion.
> 
> The database conversation is scheduled to begin at 01:00 PST on Saturday, 25 February 2012.  After checking for any errors in the conversion process, the Datatracker will be pointed at the new database.  The database conversion it is expected to finish around 03:00 PST.  Expect the Datatracker to be unavailable during this two hour period, and please plan accordingly.
> 
> Hopefully, this significant Datatracker major change will go unnoticed by the whole community.
> 
> Thanks again for you help with the testing,
>  Russ
> 
> 
> On Feb 14, 2012, at 2:36 PM, IETF Chair wrote:
>> 
>> Shortly, the IETF datatracker will go through a major change, one of the two largest since it was first deployed more than 10 years ago.  Hopefully no one will notice.
>> 
>> The previous major change was in 2007, when we switched the public Datatracker from Perl cgi-bin scripts to a much more modern and safe implementation based on the Django web application framework.  Very few people noticed that change at the time.
>> 
>> In a few days, we will transition to completely redesigned Datatracker database schema.  The new schema will better support today's needs, and we believe it will better support future enhancements.  Frankly, we outgrew the old schema some time ago.
>> 
>> In order to achieve a nearly unnoticeable change-over, we now invite you to try out the new Datatracker, bang on it, kick the tires, and generally see if it works as well for you as the old one.
>> 
>> For some additional insight, you may want to read the instructions that was given to our testers:
>> http://trac.tools.ietf.org/tools/ietfdb/wiki/InstructionsForTesters
>> 
>> Or, you may want to just jump in and see how it works.  Either way, please report any bugs, problems, surprises, gremlins, hiccups, flaws, and so on that you discover.  Reports will receive prompt attention.  We deploy new code upgrades (if any are available) every hour. Please use this mail list to report issues:
>> iola-conversion-tool@ietf.org
>> 
>> Try out the new Datatracker, and help us make a smooth transition.  The new Datatracker is running here:
>> https://trackerbeta.ietf.org/
>> 
>> Thank you for your assistance,
>> Russ
>