Closed Bug 685530 Opened 14 years ago Closed 14 years ago

puppetize / migrate off of test-master01 and buildbot-master3

Categories

(Release Engineering :: General, defect, P3)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: catlee, Unassigned)

References

Details

(Whiteboard: [buildmasters][puppet])

Attachments

(1 file)

The masters below aren't managed by puppet. We should fix that. buildbot-master2.build.scl1.mozilla.com buildbot-master3.build.mozilla.org buildbot-master5.build.scl1.mozilla.com test-master01.build.mozilla.org I think fresh images would be cleanest, then we can retire these old machines/VMs.
Blocks: 674146
Priority: -- → P5
The only master left of that list is test-master01
Summary: puppetize / migrate off of old buildbot masters → puppetize / migrate off of test-master01
How do we create a master in MTV? Do we have ganetti in mtv? or vmware?
I was so wrong about buildbot-master3! It is still in use as a try master. (I got confused with bm02).
Summary: puppetize / migrate off of test-master01 → puppetize / migrate off of test-master01 and buildbot-master3
buildbot-master19 and buildbot-master20 are now ready to be puppetized.
Priority: P5 → --
No longer blocks: 674146
If we migrate off tm01, we need to make sure we get MAX_BROKER_REFS = 2048 in the buildbot.tac of the new master(s). https://bugzilla.mozilla.org/show_bug.cgi?id=701864#c18
Priority: -- → P3
Can this now be closed?
yes(In reply to Amy Rich [:arich] [:arr] from comment #7) > Can this now be closed? yes
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Attachment #589521 - Flags: review?(aki) → review+
Attachment #589521 - Flags: checked-in+
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: