buildslaves should get their hostname from DHCP/DNS

RESOLVED FIXED

Status

Release Engineering
General
P4
normal
RESOLVED FIXED
7 years ago
5 years ago

People

(Reporter: zandr, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [buildslaves][q2goal?])

(Reporter)

Description

7 years ago
The existence of https://wiki.mozilla.org/PostImage should be considered a bug. 

Top of that list is pulling hostnames from DHCP/DNS.

What's required from the releng side to do this?
The release group spent a *lot* of time on this at Zmanda.  It's a matter of
 a. making sure the right options are present in the DHCP replies
 b. mucking with the network startup code of each OS/distro to get it to work.

Sadly, I don't remember any of the details of that work.  What's more, I didn't have any Windows slaves there.
Whiteboard: [buildslaves]
(Reporter)

Comment 2

7 years ago
Right, I'll add option-hostname to DHCP as a starting point.

/me notes that the Windows section doesn't say a thing about hostnames.

Comment 3

7 years ago
Some platforms are going to be easier to do than others, i.e. not Windows.

Do we want dependent bugs per-platform here?
OS: Mac OS X → All
Priority: -- → P4
Hardware: x86 → All
Whiteboard: [buildslaves] → [buildslaves][q2goal?]
I misspoke about doing this at Zmanda - we were trying to get the DHCP server to update DNS (via DDNS) based on a hostname provided by the slave.  That was hard.  This might be easier.

To the extent that this can happen asynchronously with other work on the slaves, let's do it - but there are a lot of other active slave-related projects that also need attention!
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
I'm pretty sure slaves get their hostnames set correctly these days.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.