1302549 - add more g2.2xlarge machines to buildbot-configs and slavealloc

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task)

Comment 1

[Jordan Lund (:jlund)]

currently we have:

300 use1 entries in slavealloc. only 100 of those are enabled

200 usw2 entries in slaveallow. *0* of those are enabled

Comment 2

[Jordan Lund (:jlund)]

(In reply to Jordan Lund (:jlund) from comment #1)
> currently we have:
> 
> 300 use1 entries in slavealloc. only 100 of those are enabled
> 
> 200 usw2 entries in slaveallow. *0* of those are enabled

sorry, to be more accurate. we have:

* 100 use1 "g-w732-spot-* g2.2xlarge" enabled
* 0 usw2   "g-w732-spot-* g2.2xlarge" enabled
* 200 use1 "t-w10-spot-* g2.2xlarge" disabled
* 100 usw2 "t-w10-spot-* g2.2xlarge" disabled

can the 't-w10-spot-*' be used for 'g-w732-spot-*' related jobs?

at any rate, we need usw2 spot instances enabled. Ideally every machine should be the same. e.g. "g-w732-spot-*"

Comment 3

[Chris Cooper [:coop] (he/him)]

(In reply to Jordan Lund (:jlund) from comment #2)
> * 100 use1 "g-w732-spot-* g2.2xlarge" enabled
> * 0 usw2   "g-w732-spot-* g2.2xlarge" enabled
> * 200 use1 "t-w10-spot-* g2.2xlarge" disabled
> * 100 usw2 "t-w10-spot-* g2.2xlarge" disabled
> 
> can the 't-w10-spot-*' be used for 'g-w732-spot-*' related jobs?

This is purely a nomenclature thing to make it clear when an instance is running tests for w7 vs w10. 

We should add 100 entries for g-w732-spot to usw2 in slavealloc. Make sure we update the buildbot-configs too.

Comment 4

[Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]]

Attachment: bug1302549_slavealloc.csv

Adding the slaves to slavealloc.

Comment 5

[Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]]

Attachment: bug1302549_bb.patch

Buildbot-config changes.

Comment 6

[Chris Cooper [:coop] (he/him)]

Comment on attachment 8791261 [details]
bug1302549_slavealloc.csv

datacenter is listed as "us-weast-2" but should be "us-west-2"

r+ with that change

Comment 7

[Chris Cooper [:coop] (he/him)]

Comment on attachment 8791262 [details] [diff] [review]
bug1302549_bb.patch

Review of attachment 8791262 [details] [diff] [review]:
-----------------------------------------------------------------

::: mozilla-tests/production_config.py
@@ +26,4 @@
>  for i in range(1, 101) + range(102, 600):  # Omit 101 due to win7 golden issues // Bug 1223509
>      SLAVES['win7_vm']['t-w732-spot-%03i' % i] = {}
>  
> +for i in range(1, 201):

Your CSV is adding up to g-w732-spot-201, so it needs to be range(1, 202) because of the way range() works.

r+ with that change.

Comment 8

[Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]]

Attachment: bug1302549_slavealloc.csv

New csv with changes west and last machine g-w732-spot-200.

Comment 9

[Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]]

Attachment: bug1302549_slavealloc.csv

Comment 10

[Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]]

New 100 g-w732-spot machines were added having this configuration (usw2 and g2.2xlarge)

New machines are g-w732-spot-[101-200]
mysql> select count(*) from slaves where name like 'g-w732-spot%';
+----------+
| count(*) |
+----------+
|      200 |
+----------+
1 row in set (0.01 sec)

mysql> select slaveid, name from slaves where name like 'g-w732-spot%' order by cast(substring(name, -3) as unsigned) desc limit 5;
+---------+-----------------+
| slaveid | name            |
+---------+-----------------+
|   32210 | g-w732-spot-200 |
|   32208 | g-w732-spot-199 |
|   32206 | g-w732-spot-198 |
|   32204 | g-w732-spot-197 |
|   32202 | g-w732-spot-196 |
+---------+-----------------+
5 rows in set (0.00 sec)

Should we enable these new 100 machiens?

Comment 11

[Chris Cooper [:coop] (he/him)]

(In reply to Andrei Obreja [:aobreja][:buildduty] from comment #10)
> Should we enable these new 100 machines?

Yes, please.

Comment 12

[Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]]

All new g-w732-spot machines were enabled.