Closed Bug 554226 Opened 10 years ago Closed 9 years ago
.0 production machines
The plan is to: - ship FF3.0.19 - wait some number of days/week to make sure there is no surprise FF3.0.20 - get formal "ok to power off" from beltzner/christian/dveditz - disable nagios alerts - powerdown all remaining FF3.0.x systems - backup systems - delete VMs, recycle hardware. - remove tinderbox tree. For now, lets start by listing what machines will eventually be powered off, and make sure that nothing is missing (or also being used for something else!). According to http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox3.0, these can go: fx-linux-1.9-slave07 fx-linux-tbox fxdbug-linux-tbox bm-xserve08 bm-xserve20 fx-win32-1.9-slave07 fx-win32-tbox fxdbug-win32-tb (the inventory shows a suspiciously long list of other machines on FF3.0.x which I'll verify before adding to this bug).
10 years ago
3.0.x is the only thing that's keeping the old version of the l10n dashboard alive, too. So I'd mothball stuff on my side, too.
10 years ago
The release machines are fx-linux-1.9-slave2 fx-win32-1.9-slave2 fx-mac-1.9-slave2 (previously bm-xerve10) We also run l10n and shark nightlies on those (via buildbot). There may also be some staging slaves left over (replace 2 with 1,3,4).
Updating comment #2: fx-linux-1.9-slave2 - releases fx-win32-1.9-slave2 - releases fx-mac-1.9-slave2 - releases, 110n nightlies, shark nightlies fx-linux-1.9-slave4 - l10n nightlies fx-win32-1.9-slave4 - l10n nightlies
Notice sent to newsgroups.
Will be turning these machines off as soon as FF3.5.10 ships. Current (rescheduled) release schedule for FF3.5.10 is Tuesday, 15th June 2010.
FF3.5.10 shipped today, so its now ok to power off these FF3.0.x machines.
I've now powered off the following VMs and machines: fxdbug-linux-tbox fxdbug-win32-tbox fx-linux-1.9-slave2 fx-linux-1.9-slave04 fx-linux-1.9-slave07 fx-win32-1.9-slave2 fx-win32-1.9-slave04 fx-win32-1.9-slave07 fx-linux-tbox fx-win32-tbox production-1.9-master fx-mac-1.9-slave2 (which seems to be bm-xserve10, even though not in inventory?) bm-xserve08 bm-xserve20 We're now ready for backup and then deleting these VMs.
Depends on: 573923
(In reply to comment #7) > I've now powered off the following VMs and machines: > > fxdbug-linux-tbox > fxdbug-win32-tbox > fx-linux-1.9-slave2 > fx-linux-1.9-slave04 > fx-linux-1.9-slave07 > fx-win32-1.9-slave2 > fx-win32-1.9-slave04 > fx-win32-1.9-slave07 > fx-linux-tbox > fx-win32-tbox > production-1.9-master > > > fx-mac-1.9-slave2 (which seems to be bm-xserve10, even though not in > inventory?) > bm-xserve08 > bm-xserve20 > > We're now ready for backup and then deleting these VMs. This looks like the complete list to me, FWIW.
See Also: → 574062
Stopped unittest staging buildbot master at sm:/builds/buildbot/unittest-master.
Depends on: 577127
Remaining work is being tracked in depbugs, so all done here.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.