Closed Bug 940659 Opened 12 years ago Closed 12 years ago

create and puppetize 4 additional buildbot masters in scl3

Categories

(Infrastructure & Operations :: RelOps: General, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: arich, Assigned: dustin)

References

Details

We need to stand up 4 additional buildbot masters in scl3 on vmware to handle load for bug 867583. They are designed to replace and should be configured the same as the buildbot masters on kvm in mtv1.
buildbot-master99.srv.releng.scl3.mozilla.com buildbot-master100.srv.releng.scl3.mozilla.com buildbot-master101.srv.releng.scl3.mozilla.com buildbot-master102.srv.releng.scl3.mozilla.com 4G, 40G, 1 vCPU
These are done. I'd like to make sure the VMDK's are aligned, and any other ESXy things are taken care of, so please hold off a bit on setting these up in case we need to reboot. Greg, can you take a look? If there are things you need to adjust, would there be any way to put those into a pre-kickstart template?
Flags: needinfo?(gcox)
These are in nagios and I've downtimed them for 1 week.
I thick- instead of thin-provisioned these, and didn't apply the key-repeat fix (http://kb.vmware.com/kb/196). I'll re-do these tomorrow, and actually make a template for it this time. And some docs.
Added a section to https://mana.mozilla.org/wiki/display/SYSADMIN/VM+Deployments to mention the things I went looking for, after audible'ing with Dustin on this. Since we hadn't documented it, and all.
Flags: needinfo?(gcox)
OK, now these are (re)done with thin provisioning and a fancy template.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.