public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: "Frank Ch. Eigler" <fche@redhat.com>,
	Eric Brown <ebrown@redhat.com>,
	overseers@sourceware.org, Jonathan Pickard <jpickard@redhat.com>,
	Matthew Galgoci <mgalgoci@redhat.com>,
	ian@airs.com
Subject: Re: Required host migration (Sourceware)
Date: Thu, 01 Oct 2009 19:11:00 -0000	[thread overview]
Message-ID: <20091001191144.GA22850@ednor.casa.cgf.cx> (raw)
In-Reply-To: <alpine.LFD.2.00.0910011500580.13564@oynqr.eqh.erqung.pbz>

On Thu, Oct 01, 2009 at 03:05:48PM -0400, Matthew Galgoci wrote:
>> >> 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 know the new network details in advance of the move, but I don't
>> think its possible to do the dual-homing. I've cc:ed mgalgoci who can
>> provide a definitive answer.
>
>Setting up the new netblock and then moving it would be somewhat of a pain.
>I would rather see us expend our effort on the new setup and suggest we take
>one of the lighter used servers and migrate it before the other two and setup
>some preliminary services on it. Make sense?

Actually, no, I don't think so.  The other two servers are actually very
underused.  Frank might correct me but I think we probably wouldn't
notice if they went down right now.

What would be great is if, in the process of this move, we could get what
we'd originally hoped for when sourceware was upgraded a few years ago -
two identical (or nearly identical) machines.  We could use one for the
main system and one for backup, allowing us to hot swap between the two
if needed.

If we could have one of the systems set up at the new site ahead of time
we wouldn't even need 48 hours down time.

cgf

  reply	other threads:[~2009-10-01 19:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 19:26 Jonathan Pickard
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 [this message]
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=20091001191144.GA22850@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=ebrown@redhat.com \
    --cc=fche@redhat.com \
    --cc=ian@airs.com \
    --cc=jpickard@redhat.com \
    --cc=mgalgoci@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).