608747 - Add 11 tegra test slaves to production pool

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

...bringing us to total of 13. 

These are now all imaged, powered and racked in Hexxor. Still to do:
* install SDcards 
* attach ethernet cables
* buildbot master config settings
* nagios settings
* entries in graphserver

Comment 1

[Mike Taylor [:bear]]

do they also need static IP assignment?

Comment 2

[John Ford [:jhford] CET/CEST Berlin Time]

while not strictly requried unless you want to remote into them, it might be a good idea to get static ips to ensure that each device is always able to get a DHCP lease.  If too many devices get non-static IPs on the build network, the tegras won't be able to get a DHCP lease at all.

Comment 3

[Mike Taylor [:bear]]

They need to be static because bm-foopy connects to them and has a config file of IP's to monitor (well, DHCP assigned)

Comment 4

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Additional one tegra donated by jmaher.

Comment 5

[Mike Taylor [:bear]]

Attachment: add 14 tegras to graph server

sql inserts required to add the 14 tegras to graph server

Comment 6

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

(In reply to comment #5)
> Created attachment 487544 [details] [diff] [review]
> add 14 tegras to graph server
> 
> sql inserts required to add the 14 tegras to graph server

justdave: can you land this patch in production graphserver, so the new tegras can be moved from staging to production early next week?

Comment 7

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

tegra-004...013 are now all running in staging in RFroom, lets see how they run over the weekend. Note that tegra-014 is still being used by Aki on his desk.

Comment 8

[Mike Taylor [:bear]]

assigning bug to IT for graph sql commit

Comment 9

[Mike Taylor [:bear]]

Attachment: inserts only for above patch

Comment 10

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

(In reply to comment #8)
> assigning bug to IT for graph sql commit

after landing sql changes, pls reassign back mozilla.org/ReleaseEngineering (specifically bear).

Comment 11

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

5,6,10,11,12 show as offline, stuck over weekend. Someone needs to hook up a
monitor to find out if they are stuck in a test or what

4,7,8,9,13 ran all weekend, and reporting good. bear is going to shepherd these into production.

Comment 12

[matthew zeier [:mrz]]

John says he needs this sooner than later.

Comment 13

[Justin Dow [:jabba]]

have the sql changes been done yet? If not, I can do them given specific instructions. I'll go see if I can figure out what is up with the ones in comment 11.

Comment 14

[Mike Taylor [:bear]]

the tegra's that are offline are not because of connection issues, more test environment so it's not on IT's plate.

The sql has not been checked in yet, i've prepared a simple cut-n-paste to be run where ever these sql inserts are run.

Comment 15

[Justin Dow [:jabba]]

I ran ran the insert statements in attachment 488906 [details].

Comment 16

[Justin Lazaro [:jlaz] (use needinfo)]

Rebooted 5,6,10,11,12

Comment 17

[Mike Taylor [:bear]]

Attachment: add 14 new tegras to the tegra_android slave list

Comment 18

[John Ford [:jhford] CET/CEST Berlin Time]

doing so

Comment 19

[John Ford [:jhford] CET/CEST Berlin Time]

Comment on attachment 489032 [details] [diff] [review]
add 14 new tegras to the tegra_android slave list

http://hg.mozilla.org/build/buildbot-configs/rev/a003ced58cd1

Comment 20

[John Ford [:jhford] CET/CEST Berlin Time]

updated on all masters between 1823-1855 Pacific.