From: "Frank Ch. Eigler" <fche@redhat.com>
To: overseers@sourceware.org, Eric Brown <ebrown@redhat.com>,
Jonathan Pickard <jpickard@redhat.com>,
ian@airs.com, Matthew Galgoci <mgalgoci@redhat.com>
Subject: Re: Required host migration (Sourceware)
Date: Fri, 06 Nov 2009 16:09:00 -0000 [thread overview]
Message-ID: <20091106160920.GB7039@redhat.com> (raw)
In-Reply-To: <20091105225721.GA2699@ednor.casa.cgf.cx>
Hi -
On Thu, Nov 05, 2009 at 05:57:21PM -0500, Christopher Faylor wrote:
> [...]
> >[...]
> >1) move to PHX2 (migrate)
> >2) order new hardware for PHX2 (phased migration)
> >
> >For 1) - Red Hat IT will move the machines and bring them back up in
> >PHX2, reconfiguring their network details if wanted and providing remote
> >access (serial and/or KVM along with remote power management).
> >
> >For 2) - Red Hat IT will install any new hardware and provide remote
> >access (serial and/or KVM along with remote power management) and you
> >will migrate your services from PHX to PHX2.
> I would very much prefer 2.
I don't think IT was offering to procure a new machine for us, just to
install one if we can get hold of same. (And as we discussed before,
since our server2/server3 machines were purchased with inadequate
resources, they can't bear the load.)
So by default, this would mean option #1.
(As I offered before, I can arrange to have a RAM upgrade package sent
to RH IS to install, along with option #1.)
- FChE
next prev parent reply other threads:[~2009-11-06 16:09 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
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 [this message]
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=20091106160920.GB7039@redhat.com \
--to=fche@redhat.com \
--cc=ebrown@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).