public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Pickard <jpickard@redhat.com>
To: cgf@sourceware.org, overseers@sourceware.org
Cc: Eric Brown <ebrown@redhat.com>
Subject: Required host migration (Sourceware)
Date: Tue, 29 Sep 2009 19:26:00 -0000	[thread overview]
Message-ID: <4AC25F6E.6050208@redhat.com> (raw)

Hello,

You or your group manages one or more servers located in Red Hat's PHX1
datacenter:

sourceware
sourceware1

If you are not the correct owner for the listed system(s) please respond
and let me know. If you know who the correct owner is, please include
that as well.

We are retrofitting PHX1 and your host(s) will need to be moved to our
PHX2 datacenter sometime in the next few months. Additionally, steps
will need to be taken by you or your group to make sure your hosts and
services remain accessible.

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)

We will take care of physically migrating the server for you, 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 using the new
network information we will provide. We will be available to assist if
any problems relating to the needed reconfigurations come up.

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.

With that said, your options for proceeding are:
1) move to PHX2 (migrate)
2) have us return the systems to you if you own them (leave)
3) have us power off and store the systems (decommission)

Please respond to this message to acknowledge ownership of the listed
system(s), inform us which listed option you will proceed with, and
state that you or someone form your group will be available to assist in
the work required for migration.

Thanks,
Jonathan Pickard
Principal Systems Administrator
Corporate Infrastructure Services
Red Hat, Inc.

             reply	other threads:[~2009-09-29 19:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 19:26 Jonathan Pickard [this message]
2009-10-01 18:02 ` Frank Ch. Eigler
     [not found]   ` <4AC4F8D6.7070200@redhat.com>
2009-10-01 19:06     ` Matthew Galgoci
2009-10-01 19:11       ` Christopher Faylor
2009-10-01 19:20         ` Frank Ch. Eigler
2009-10-01 21:11           ` Matthew Galgoci
2009-11-05 22:37             ` Jonathan Pickard
2009-11-05 22:57               ` Christopher Faylor
2009-11-06 16:09                 ` Frank Ch. Eigler
2009-11-06 21:52                   ` Jonathan Pickard
2009-12-03 20:57                     ` Jonathan Pickard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AC25F6E.6050208@redhat.com \
    --to=jpickard@redhat.com \
    --cc=cgf@sourceware.org \
    --cc=ebrown@redhat.com \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).