From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5935 invoked by alias); 1 Oct 2009 18:02:45 -0000 Received: (qmail 5801 invoked by uid 22791); 1 Oct 2009 18:02:44 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 01 Oct 2009 18:02:39 +0000 Received: from int-mx05.intmail.prod.int.phx2.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.18]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n91I2cE4013629; Thu, 1 Oct 2009 14:02:38 -0400 Received: from fche.csb (vpn-240-19.phx2.redhat.com [10.3.240.19]) by int-mx05.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id n91I2bSX010599; Thu, 1 Oct 2009 14:02:37 -0400 Received: by fche.csb (Postfix, from userid 2569) id 3E39958122; Thu, 1 Oct 2009 14:02:37 -0400 (EDT) Date: Thu, 01 Oct 2009 18:02:00 -0000 From: "Frank Ch. Eigler" To: Jonathan Pickard Cc: cgf@sourceware.org, overseers@sourceware.org, Eric Brown Subject: Re: Required host migration (Sourceware) Message-ID: <20091001180237.GD20893@redhat.com> References: <4AC25F6E.6050208@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AC25F6E.6050208@redhat.com> User-Agent: Mutt/1.4.2.2i Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org X-SW-Source: 2009-q4/txt/msg00001.txt.bz2 Hi - On Tue, Sep 29, 2009 at 12:26:38PM -0700, Jonathan Pickard wrote: > You or your group manages one or more servers located in Red Hat's PHX1 > datacenter: > > sourceware > sourceware1 Actually there are three machines, with DNS names sourceware.org, server2.sourceware.org, server3.sourceware.org. > [...] > Work required: > * reconfigure networking on systems (IP address/netmask/gateway will change) > * reconfiguration of services on system (if necessary, due to new IPs) > * updates to DNS (due to new IPs) Can the new IP addresses be provided in advance? Would it be possible to configure the machines in PHX1 with (temporary) dual-homing to actually exercise the new addresses, so as to give us a transition period? > We will take care of physically migrating the server for you, This could be an opportune (for us) time to get a helpful upgrade for the main old machine. None of our guys are near PHX, so would it be possible to coordinate having you guys add in new memory DIMMs during the downtime? > as well as (re)configuring any available remote management access, > such as serial, DRACs, RSAs, iLO's, etc. Once remote management > access is available, you can perform the needed network/daemon > reconfigurations [...] The machines currently have a somewhat incestuous interconnection for their serial consoles, which may preclude trivial remote-access bootstrapping. I believe has another separate console access method that he would have to share with us. > Note that the physical move will result in downtime for the hosts. > Allowing time for unracking, transportation, and re-racking, you can > anticipate up to 48 hours of downtime. Specific dates and times are > not yet available, but will be communicated out as soon as they are > determined. The longer notice, the better. These machines are hubs of several well-known free software projects, so a large community is being impacted. - FChE