Create centralized management system to control which buildbot and puppet master a slave has to talk to

RESOLVED FIXED

Status

P4
normal
RESOLVED FIXED
8 years ago
5 years ago

People

(Reporter: armenzg, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
Using buildbot-tac.py to generate the right buildbot.tac helped us a lot but with so many pods and trying to port this to the testing pools is making it a really difficult system to maintain.

Once a machine is re-imaged it should have a centralized service from where to discover to which buildbot master to talk to and to which puppet server to talk to depending on OS, slave type and IP. This system should not need to refresh the reference images.

I think that tackling this on Q1 would be good as the dust of the new colo and new platforms should have settled by then.

Shall we call this system WDITT (who do I talk to) and open-source it? :P
(Reporter)

Updated

8 years ago
Priority: -- → P4
Should we dupe this bug to or from bug 508673?
(Reporter)

Comment 2

8 years ago
To note that this extends the scope to also help with puppet.
Up to you.
Fixed by slavealloc
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.