From: Jonathan Pickard <jpickard@redhat.com>
To: Jonathan Pickard <jpickard@redhat.com>
Cc: me@cgf.org, overseers@sourceware.org
Subject: Re: Red Hat PDU upgrades (Mesa, AZ datacenter)
Date: Fri, 21 Nov 2008 02:15:00 -0000 [thread overview]
Message-ID: <73BF3899-5FC5-4469-A5DB-B865218A06AF@redhat.com> (raw)
In-Reply-To: <C808ED51-82E6-4CD6-AECE-A6C03C49CEF1@redhat.com>
All,
The maintenance finished without major incident.
Regards,
Jonathan
On Nov 19, 2008, at 9:18 AM, Jonathan Pickard wrote:
> [Reminder that this maintenance will take place tomorrow.]
>
> Hello,
>
> The PDU upgrades have been scheduled for Thursday, November 20,
> 2008 at 6pm MST (5pm PST, 8pm EST). I will follow-up once the work
> is completed or if issues arise.
>
> Regards,
> Jonathan
>
> On Nov 10, 2008, at 11:45 AM, Jonathan Pickard wrote:
>
>> Hello,
>>
>> We will soon be conducting an upgrade to the PDUs that provide
>> power to the servers that you are hosting with Red Hat in our
>> Mesa, AZ (PHX) facility. To minimize service disruption, I am
>> coordinating the work with the various host owners. You are listed
>> as a contact for the following machines:
>> sourceware
>> sourceware1
>> sourceware2
>>
>> Your affected machines have dual power supplies, and the work
>> being planned is staged to take advantage of this through the
>> following steps:
>>
>> * Install new PDU (new-a)
>> * Removing servers power from old primary PDU (old-a)
>> * Connecting servers power to new primary PDU (new-a)
>> * Repeat process with secondary PDUs (old-a and old-b)
>>
>> If your hosts are properly configured and the hardware is in
>> working order, there should be no downtime. However, it may be at
>> the point of power swap that a problem is realized. To minimize
>> that risk, we are working with the host owners to schedule a date
>> and time that will lessen the impact of a downed host or hosts.
>>
>> Please respond to me as soon as possible with the following:
>> * Confirmation that you have working remote management access to
>> the host, in order to bring it back online if power is disrupted
>> (something such as remote serial access through a Cyclades, a Dell
>> DRAC, IBM RASII, or the like).
>> * A range of dates and times, before November 21, that you prefer
>> the outage be scheduled for.
>>
>> Once I have this information I will work with the various owners
>> to coordinate a finalized date and time for the work.
>>
>> Thanks,
>> Jonathan Pickard
>> Corporate Infrastructure Services
>> Red Hat, Inc
>
prev parent reply other threads:[~2008-11-21 2:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 18:46 Jonathan Pickard
2008-11-10 21:27 ` Frank Ch. Eigler
2008-11-10 23:14 ` Matthew Galgoci
2008-11-11 0:49 ` Christopher Faylor
2008-11-11 15:29 ` Matthew Galgoci
2008-11-11 15:38 ` Christopher Faylor
2008-11-14 20:18 ` Jonathan Pickard
2008-11-19 16:18 ` Jonathan Pickard
2008-11-19 16:28 ` Christopher Faylor
2008-11-21 2:15 ` Jonathan Pickard [this message]
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=73BF3899-5FC5-4469-A5DB-B865218A06AF@redhat.com \
--to=jpickard@redhat.com \
--cc=me@cgf.org \
--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).