Mothball TB2.0 production machines

RESOLVED FIXED

Status

defect
RESOLVED FIXED
9 years ago
6 years ago

People

(Reporter: joduinn, Assigned: joduinn)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

From offline emails with dmose, et al, we are now able to power off the TB2 machines. This release is long past EOL, and now the TB3.1 is offering MU to the remaining TB2 users. As usual, this bug is to track exactly what machines we will be powering off and when.


According to inventory, the TB2 machines still in production are:

bm-xserve01
bm-xserve05
crazyhorse
patrocles
production-crazyhorse
production-patrocles  
production-prometheus-vm
production-1.8-master

Does this look accurate? Are there any other machines that I missed?
Pretty sure that's incomplete, and bm-xserve01 should not be on there (unless you mean we no longer need a backup ppc machine). I'll loop to this next week.
prometheus-vm  can also go.
(In reply to comment #1)
> Pretty sure that's incomplete, and 
Thats all I could find in inventory and tinderbox waterfalls - whats missing?

> bm-xserve01 should not be on there (unless
> you mean we no longer need a backup ppc machine). 
Exactly what I mean. :-) We can recycle them as slaves on geriatric-master if we care, depending on the hardware.
Powered off following VMs: 

production-crazyhorse
production-patrocles  
production-prometheus-vm
production-1.8-master
crazyhorse
patrocles
prometheus-vm

...and physical machines:
bm-xserve01 (PPC G5 xserve; 2 x 2.3ghz cpu; 4gb ram)
bm-xserve05 (PPC G5 xserve; 2 x 2.3ghz cpu; 2gb ram)
Missed:
production-pacifica-vm
staging-nightly-updates
egg     (no more configure.in -> configure for CVS)

All VMs.
(In reply to comment #5)
> Missed:
> production-pacifica-vm
> staging-nightly-updates
> egg     (no more configure.in -> configure for CVS)
> 
> All VMs.

All now off.
Nothing left to do here; VMs backed up. All remaining machine reset and setup work covered in dep.bugs.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.