Closed
Bug 502151
Opened 15 years ago
Closed 14 years ago
[Tracking] netapp-a/b firmware upgrades
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mrz, Assigned: aravind)
Details
(Whiteboard: 04/17/2010 @ 2pm PDT)
Attachments
(2 files)
No description provided.
Reporter | ||
Updated•15 years ago
|
Assignee: server-ops → aravind
Reporter | ||
Updated•15 years ago
|
Whiteboard: [december]
Reporter | ||
Updated•15 years ago
|
Component: Server Operations → Server Operations: Projects
Reporter | ||
Comment 1•15 years ago
|
||
Need to start planning.
Component: Server Operations: Projects → Server Operations
Flags: needs-downtime+
Summary: [Tracking] NetApp firmware upgrades → [Tracking] netapp-a/b firmware upgrades
Whiteboard: [december] → 01/02/2010 ?
Reporter | ||
Updated•15 years ago
|
Group: infra
Reporter | ||
Comment 2•15 years ago
|
||
Reporter | ||
Comment 3•15 years ago
|
||
Assignee | ||
Comment 4•15 years ago
|
||
I'd like to schedule this for Jan 2'nd. Will look at the list of mounts and will let folks know what will be impacted.
Reporter | ||
Updated•14 years ago
|
Whiteboard: 01/02/2010 ? → 03/06/2010
Comment 5•14 years ago
|
||
have we really been trying to plan this for 6 months...? wow.
Reporter | ||
Updated•14 years ago
|
Component: Server Operations → Server Operations: Projects
Reporter | ||
Updated•14 years ago
|
Whiteboard: 03/06/2010 → 04/17/2010 @ 2pm
Reporter | ||
Comment 6•14 years ago
|
||
Date's confirmed, will educating around downtime.
Updated•14 years ago
|
Whiteboard: 04/17/2010 @ 2pm → 04/17/2010 @ 2pm PST
Reporter | ||
Updated•14 years ago
|
Whiteboard: 04/17/2010 @ 2pm PST → 04/17/2010 @ 2pm PDT
Comment 7•14 years ago
|
||
In this downtime, approx how long will you need for the netapp upgrades? (Whatever time is needed is fine; I ask because I'm trying to calc how long the overall tree closure will need to be. RelEng will need to keep the trees closed for a couple of hours afterward netapp work is done, while we spin all build/test/perf systems back up to speed.)
Assignee | ||
Comment 8•14 years ago
|
||
We would like a 3 hour window (from start to stop), before we declare the exports and iscsi shares to be functional. So the downtime starts at 2:00 PM, we should be done by 5:00 PM. Does that answer your question? If you need more information, let me know.
Component: Server Operations: Projects → Server Operations
Comment 9•14 years ago
|
||
The IT upgrade work completed on schedule by 5pm. I'm now verifying RelEng systems are ok before reopening tree.
Comment 10•14 years ago
|
||
vm's should be back online. let me know if i missed anything.
Reporter | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•