From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24720 invoked by alias); 13 Dec 2009 03:46:52 -0000 Received: (qmail 24458 invoked by uid 22791); 13 Dec 2009 03:46:51 -0000 X-SWARE-Spam-Status: No, hits=-0.2 required=5.0 tests=AWL,BAYES_05,EXECUTABLE_URI,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 SMTP; Sun, 13 Dec 2009 03:46:46 +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 nBCCf59n001103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 12 Dec 2009 07:41:05 -0500 Received: from jpickard-laptop.phx ([10.8.7.155]) by int-mx05.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id nBCCf49l005586; Sat, 12 Dec 2009 07:41:04 -0500 Message-ID: <4B238F60.9080700@redhat.com> Date: Sun, 13 Dec 2009 03:46:00 -0000 From: Jonathan Pickard User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Thunderbird/3.0b4 MIME-Version: 1.0 To: "Frank Ch. Eigler" , cgf@sourceware.org, overseers@sourceware.org CC: Eric Brown Subject: Re: Required Host Migration Information (Sourceware) References: <4B214130.9050201@redhat.com> In-Reply-To: <4B214130.9050201@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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/msg00145.txt.bz2 All, The migration will begin momentarily. If you haven't halted your hosts you still have some time to do so. We expect power to be disconnected to the cabinets within the next 30 minutes. This will be my last update until the all-clear is given to your pre-designated contact. Please contact me if you have any questions or concerns throughout the day. Regards, Jonathan On 12/10/2009 11:42 AM, Jonathan Pickard wrote: > The required PHX-PHX2 Community Hosts migration will begin at 5:30am MST > on Saturday, December 12, 2009. Red Hat IT will be responsible for: > > * disconnecting systems from power > * physical transport of the systems, including insurance coverage > * re-racking systems in new location > * reconfiguring primary IP address of each system (via single user mode) > * connecting and (re)configuring remote management mechanisms (serial, > KVM, RSA/IMM/DRAC-type devices) > * submitting requests to Network team for ACLs and External Static Maps > * DNS changes (if Red Hat manages your DNS) > > On your side, your predesignated contact (Chris Faylor) will be > responsible for: > > * alerting any impacted users of the downtime > * halting your hosts at or before 5:30am MST on 12/12 > * DNS changes (if you manage your own DNS) > * any necessary service reconfigurations > * testing services and remote management access once hosts come back online > * assisting in troubleshooting any network issues (missing ACLs or maps) > > Specific details about the move follow. > > > - Network details > > * IPs > The following IPs have been assigned to your host(s) and will be used in > the new location. > > sourceware: 209.132.180.131 > server2: 209.132.180.132 > server3: 209.132.180.133 > > Once your host is racked and powered in its new location, it will be > brought into single user mode where its primary network interface will > be updated and basic network confirmation will take place. Console > access will be strictly limited to these activities and will be > performed only by on-site Red Hat IT staff. > > If you prefer to update the network information yourself using one of > the remote access methods that will be made available, please notify us > in advance. Allowing us to update the network information for you will > result in decreased downtime, but we understand if you prefer to > maintain your own systems and can accommodate the additional downtime > that may ensue. > > * ACLs > The following ACLs have been requested for your hosts and are based on > any existing ACLs that are already in place: > > 209.132.180.131: 3690, udp gt 1023, ssh, ftp-data, ftp, smtp, ident, > 53, 53, 174, 209, 330, 443, 873, 2401, 8080, 9418 > 209.132.180.132: ssh, ftp-data, ftp, smtp, ident, 53, 53, 174, 209, > 330, 443, 873, 2401, 8080, 9418 > 209.132.180.133: ssh, ftp-data, ftp, smtp, ident, 53, 53, 174, 209, > 330, 443, 873, 2401, 8080, 9418 > > - Remote Access > All non-SSH remote access is limited to within the internal Red Hat > Network only. Access is available right now but won't connect to > anything since the hosts have not been migrated yet. > > * Serial > Hostname: rack55-serial01.mgmt.phx2.redhat.com (SSH or HTTPS) > Username: sourceware > Password: (will be provided to the predesignated contact the day of > migration) > > Once connected, run the ts_menu command and select the host that you are > wanting to connect to. You may or may not have had serial access > configured previously. If not, it may require some configuration at the > OS level and in the BIOS, which you can do through the KVM access > mentioned below. > > * KVM > Hostname: rack55-kvm01.mgmt.phx2.redhat.com > Username: sourceware > Password: (will be provided to the predesignated contact the day of > migration) > > The KVM software can be downloaded at: > http://ftp.us.dell.com/RACK%20SOLUTIONS/DELL_MULTI-DEVICE_A01_R193912.exe > > The executable is a self-extracting zip file which you can unzip like > any other zip file, it is not a Windows-only file. Once extracted there > is a setup file that you will run for installation. After installed, > when adding the KVM, you will prompted for the device type that you are > adding -- select Dell 4161DS and provide the hostname or IP address from > above. > > * On-board Management Devices (RSA, IMM, DRAC, etc.) > Your server does not have an on-board management device. > > * Power Management > If a host becomes unresponsive and you are unable to powercycle it > through other means (such as remote power management through an on-board > management device), you can request that Red Hat IT powercycle it > through our managed PDUs. To do this, include the name of the device you > want to powercycle in an e-mail sent to helpdesk@redhat.com. Only the > documented owner of the system will be able to request this, and > follow-up verification will be made to ensure that the request is coming > from the owner before the system is powercycled. > > > - Migration Timeline > > The outage will begin at 5:30am MST on 12/12. Every effort will be taken > to minimize downtime. You should expect that your hosts will be back > online no later than 5pm on 12/13, although if all goes as planned your > hosts should be online before the evening of 12/12. > > Once your hosts are back online, your predesignated contact will be > notified and then can perform any needed follow-up actions. > > > - Communication > I am your Red Hat IT point of contact for this migration and my contact > details follow. > > Name: Jonathan Pickard > E-mail: jpickard@redhat.com > Cell: +1 919-559-8266 (US) > IRC (Red Hat networks): essteepee > PHX2 Cage phone: +1 480-722-0294 (US) > > If you have any questions or concerns please do not hesitate to contact me. > > Regards, > Jonathan