524645 - Setup buildbot master on talos-master02

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

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

Once this VM is created, install a new buildbot master instance. This instance will be used by a small pool of Talos slaves being run in server room in 650Castro.

To start with, we should have this master, and slaves, reporting to staging *only*. Once we have been running for a while, and the numbers in staging line up with other production talos systems, then we know that this location outside MPT is not causing any performance weirdness.

(If this experiment works, we can continue exploring the idea of hosting minis in a remote redundant colo. If this does not work, we'll have to figure out the results discrepancy before we can proceed with remote colo idea)

Comment 1

[Lukas Blakk [:lsblakk] use ?needinfo]

The buildbot master talos-master02 has been created and running builds in tandem with our current talos box.  

Instructions for setting up a new master have been created here: https://wiki.mozilla.org/ReferencePlatforms/BuildbotMaster

Data is being collected to allow for a comparison between the new talos-master02 and the existing talos production results.

Comment 2

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: Adds all the current talos masters (staging and production) to config.py

While we are working on this talos-master location stuff, all the build reporting should just go out to both mv and mpt talos-masters (staging as well as production) so that we're getting the sendchanges needed to test the setup.

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

Comment on attachment 410694 [details] [diff] [review]
Adds all the current talos masters (staging and production) to config.py 

Looks fine against rev 36cae32d3493, r+.

Comment 4

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 410694 [details] [diff] [review]
Adds all the current talos masters (staging and production) to config.py 

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

Comment 5

[Nick Thomas [:nthomas] (UTC+12)]

Removed sending from pm* to talos-master02.mv.m.c because it doesn't resolve yet, and there's only a hole in the firewall for talos-staging-master02.

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

Comment 6

[Nick Thomas [:nthomas] (UTC+12)]

(In reply to comment #5)
Although this wasn't causing red/orangeness on the tree, it was causing each build to take an extra 10 minutes (for all the retry attempts to fail). Once the infra is fixed and you can go
  telnet talos-master02.mv.mozilla.com 9010
on pm and pm02 then we can add it back in again.

Comment 7

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: Add talos-master02 to production and staging

Comment 8

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

Comment on attachment 410906 [details] [diff] [review]
Add talos-master02 to production and staging

looks good. (Stamp!)

Comment 9

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 410906 [details] [diff] [review]
Add talos-master02 to production and staging

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