Closed
Bug 1220178
Opened 9 years ago
Closed 9 years ago
please instantiate two new buildbot masters
Categories
(Infrastructure & Operations :: Virtualization, task)
Infrastructure & Operations
Virtualization
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: arich, Assigned: cknowles)
References
Details
(Whiteboard: [vm-create:2])
Urgency on this is pretty high (today or Monday would be optimal) since we're trying to migrate some of the linux test machines to be windows test machines so we can support e10s. This has left us with not enough buildbot master capacity. I've created host entries for them in inventory, but they'll need the MAC info to be able to kickstart (we'll also need to be able to input the puppetize pw on boot at the initial kickstart): buildbot-master126.bb.releng.scl3.mozilla.com buildbot-master127.bb.releng.scl3.mozilla.com They should be exactly like the other buildbot masters and use the buildbot master template in the releng folder. Thanks!
Reporter | ||
Comment 1•9 years ago
|
||
There's a request to bump these up to 2 CPUs if possible.
Assignee | ||
Comment 2•9 years ago
|
||
OK, those two vms are created. Due to movement and insane mornings, I neglected to 2cpu-ify buildbot-master126 - but 127 has the 2 cpus. Spreadsheets updated, directions for working with console and bumping 126 have been handed. Only ask from my end is that after the kickstart, once the disks have been partitioned, I would like to check the alignment ... if things are not aligned, we'll have to arrange for an outage to align them, but previous testing says things will likely be alright. I'll set a reminder to poke in a week if I don't hear otherwise. As always, let me know if there is anything else we can do.
Assignee: server-ops-virtualization → cknowles
Whiteboard: [vm-create:2]
Reporter | ||
Comment 3•9 years ago
|
||
I bumped up the cores to 2 on 126. I have one machine up (127) and one down (126) right now, if you want to check alignment. They'll both be up and in prod soon.
Comment 4•9 years ago
|
||
Alignment checked, verbal'ed the closeout from :arr.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•9 years ago
|
||
Apparently the extra load we've added also means we need more RAM. Can we bump these two up to 6G as well as the following machines: buildbot-master109.bb.releng.scl3.mozilla.com buildbot-master110.bb.releng.scl3.mozilla.com buildbot-master111.bb.releng.scl3.mozilla.com buildbot-master112.bb.releng.scl3.mozilla.com For a total of 12G more. (I just a confirmation yes/no, I can do the work in vmware).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 6•9 years ago
|
||
Missed one, sorry: buildbot-master119.bb.releng.scl3.mozilla.com
Assignee | ||
Comment 7•9 years ago
|
||
Per IRC: arr: you're clear to bump the ram on these listed boxes. I'll make sure our sheets match. If you need us, let us know.
Reporter | ||
Comment 8•9 years ago
|
||
I've increased the two new machines to 6G. We'll have to schedule a shutdown of the ones that are currently in production.
Reporter | ||
Comment 9•9 years ago
|
||
Okay, all of the windows buildbot masters now have 2 CPU, 2 socket, and 6G of RAM: buildbot-master109.bb.releng.scl3.mozilla.com buildbot-master110.bb.releng.scl3.mozilla.com buildbot-master111.bb.releng.scl3.mozilla.com buildbot-master112.bb.releng.scl3.mozilla.com buildbot-master119.bb.releng.scl3.mozilla.com buildbot-master126.bb.releng.scl3.mozilla.com buildbot-master127.bb.releng.scl3.mozilla.com
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 10•9 years ago
|
||
For the pedants in all of us (you know who you are) - that's 2CPU, 2 cores per socket - NOT 2 sockets. Checked them over, looks good! you know where to find us.
You need to log in
before you can comment on or make changes to this bug.
Description
•