Closed Bug 548109 Opened 15 years ago Closed 15 years ago

Reimage 50 old talos-rev2 minis as 10.6 build slaves

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Assigned: jabba)

References

Details

Attachments

(1 file)

According to inventory, these should be called: moz2-darwinX-slave01.build.mozilla.org ... moz2-darwinX-slave40.build.mozilla.org please add following to dns, inventory, nagios, etc. For now I'm leaving this bug in RelEng while we monitor the transition, and also finish up the new 10.6 moz2-darwin10-ref, hence blocked on bug#537065. If all goes well, I'll push this bug to IT in a few days.
rev2 machines now being recycled. Only remaining blocker here is waiting for a working 10.6 moz2-darwin10-ref.
I believe this should be blocked on bug 545539 (64bit ref image bug) instead of bug 537065 (rev3 machines)
hrmm it sounds like these are rev3 machines instead of rev2. Are both rev3 and rev2 going to use the same ref-image?
pushing to bear to track. Once bug#545539 is done, we can push this to IT.
Assignee: nobody → bear
Depends on: 545539
Tweaking summary as part of WONTFIXing bug#548231. All these minis will come up in staging initially. We will probably push 40 to production, and leave 10 in staging, but RelEng can decide that at the time.
Summary: Reimage 40 old talos-rev2 minis for production 10.6 build/unittest pool → Reimage 50 old talos-rev2 minis as 10.6 build slaves
jabba: Here's the bug you were looking for. Just two imaged slaves please. If they run smoothly in staging, we'll give the go to start imaging the rest of them.
Assignee: bear → jdow
Component: Release Engineering → Server Operations
QA Contact: release → mrz
I've got slave01 and slave02 online, in DHCP, in DNS and in Nagios. Let me know when you want me to proceed on the rest of them.
Status: NEW → ASSIGNED
Component: Server Operations → Release Engineering
I just wanted to clarify what the names of these should be. Is it darwinX or darwin10?
(In reply to comment #9) > I just wanted to clarify what the names of these should be. Is it darwinX or > darwin10? I believe the machine names proposed in comment#0 are correct. alice: can you clarify? iirc, the suggestion was darwinX because it sorted correctly along with the darwin8, darwin9 machines. Out of curiosity, I wonder what to do with next OS - maybe call those slaves darwinXI ?
Component: Release Engineering → Server Operations
(In reply to comment #10) > (In reply to comment #9) > > I just wanted to clarify what the names of these should be. Is it darwinX or > > darwin10? > > I believe the machine names proposed in comment#0 are correct. alice: can you > clarify? iirc, the suggestion was darwinX because it sorted correctly along > with the darwin8, darwin9 machines. If that's the case, we need to fix the ref platform to be darwinX, too. Why is sorting in order important? darwin10 is more consistent with existing hostnames.
I think darwin10 is slightly better, since it ends the confusion of whether X is a roman numeral or a place holder. If sorting is an issue, we could also switch to hex and call them darwinA and future versions could be darwinB, darwinC, etc. I think darwin10 is probably the correct choice. Just my two cents.
/me agrees that darwin10 makes more sense.
Go ahead and shut down the ref machine, pull the image, and image all of the minis!
I randomly picked 01 - 04 to be staging slaves.
Attachment #435005 - Flags: review?(catlee)
The following are done and online: moz2-darwin10-slave01 moz2-darwin10-slave02
Attachment #435005 - Flags: review?(catlee) → review+
Attachment #435005 - Attachment description: add 10.6 slaves to puppet manifests → [checked in] add 10.6 slaves to puppet manifests
Comment on attachment 435005 [details] [diff] [review] [checked in] add 10.6 slaves to puppet manifests changeset: 118:b56cc318fd8f
from irc, jabba notes that we have 7 dead rev2 minis, leaving 43 available for imaging. The 4 available minis from bug#549570 helps backfill a little, bringing us back up to 47 available.
(In reply to comment #18) > from irc, jabba notes that we have 7 dead rev2 minis, leaving 43 available for > imaging. The 4 available minis from bug#549570 helps backfill a little, > bringing us back up to 47 available. ...and adding the 3 available minis from bug#549551 brings us back up to 50.
moz2-darwin10-slave01 ... ... moz2-darwin10-slave50 are all online, in DNS, DHCP and Nagios. slaves 01, 02, and 40 through 50 are physically located at 650 Castro, the rest are at MPT.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: