Closed Bug 1264417 Opened 8 years ago Closed 8 years ago

Create five new buildbot masters for Mac testing

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: coop, Assigned: vciobancai)

References

Details

Attachments

(4 files)

We currently have 3 Mac test masters:

bm106-tests1-macosx	
bm107-tests1-macosx
bm108-tests1-macosx

I tried connecting to bm108 today, and it was painfully slow. We have 336 Mac test machines trying to connect to those 3 masters, so that slowness doesn't really surprise me. We've had high pending counts for Mac tests recently (>3000 pending yesterday), so we should do what we can to improve the performance of those masters. 

On top of the general slowness, there are plans to add some 200 more r7 testers (bug 1184181).

We should create five new buildbot-masters to address the current slowdown (giving us 8 Mac testing masters total), and also provide us with master capacity for the new machines when they arrive.

536 Mac test machines / 8 masters = 67 machines per master
No longer blocks: 1184181
Blocks: 1257963
We'll should be ready to start imaging machines in a couple days. Can someone please look at getting the new buildbot masters created and configs modified soon?
Assignee: nobody → vciobancai
Attached you can find the patch that add new 5 buildbot master for macosx in moco-nodes
Attachment #8748209 - Flags: review?(arich)
Attached you can find the patch that add 5 new macosx in production_master.json by default disabled
Attachment #8748210 - Flags: review?(kmoir)
Attachment #8748209 - Flags: review?(arich) → review+
Attachment #8748209 - Flags: checked-in+
Attachment #8748210 - Flags: review?(kmoir) → review+
Depends on: 1269782
Attachment #8748210 - Flags: checked-in+
Attached you can find the csv file for the new masters in order to be added in slavealloc DB
Attachment #8748719 - Flags: review?(kmoir)
Attached you can find the path to enable the new masters in production. This patch needs to be land the last one
Attachment #8748720 - Flags: review?(kmoir)
Attachment #8748719 - Flags: review?(kmoir) → review+
Comment on attachment 8748720 [details] [diff] [review]
bug1264417_enable-masters.patch

Looks good. Remember to lock some machines to the masters
https://wiki.mozilla.org/ReleaseEngineering/AWS_Master_Setup#Lock_a_slave_and_let_it_take_jobs

before enabling it completely to ensure it runs green jobs etc
Attachment #8748720 - Flags: review?(kmoir) → review+
The new masters have been added in slavealloc DB
Attachment #8748719 - Flags: checked-in+
Blocks: 1267712
We have pointed 5 slaves to connect to every buildbot-master created and everything seems to work as intended.
More details can be found bellow :
http://buildbot-master132.bb.releng.scl3.mozilla.com:8201/one_line_per_build
http://buildbot-master133.bb.releng.scl3.mozilla.com:8201/one_line_per_build
http://buildbot-master134.bb.releng.scl3.mozilla.com:8201/one_line_per_build
http://buildbot-master135.bb.releng.scl3.mozilla.com:8201/one_line_per_build
http://buildbot-master136.bb.releng.scl3.mozilla.com:8201/one_line_per_build

From our point of view the new masters are working ok,can we enable them in the production.
Flags: needinfo?(kmoir)
great work! yes please land the final patch
Flags: needinfo?(kmoir)
Attachment #8748720 - Flags: checked-in+
The patch landed https://hg.mozilla.org/build/tools/rev/183ee5c45256
The new masters have been enabled in to the production
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: