If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

relocate free buildbot masters to the bb vlan

RESOLVED DUPLICATE of bug 1040926

Status

Release Engineering
General
P2
normal
RESOLVED DUPLICATE of bug 1040926
3 years ago
3 years ago

People

(Reporter: arr, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 obsolete attachment)

(Reporter)

Description

3 years ago
We have a new buildbot vlan, .bb that was created to make new buildbot master standup much simpler from a network security perspective. The intention is that this vlan will host all of the buildbot masters going forward. Currently, there are a number of "free" buildbot masters listed in puppet, and I'd like to propose that we move them now before they see use. According to puppet, this means the following masters:

buildbot-master56
buildbot-master57
buildbot-master58
buildbot-master59
buildbot-master60
buildbot-master61
buildbot-master62
buildbot-master63
buildbot-master64
buildbot-master65
buildbot-master80
buildbot-master90
buildbot-master92
buildbot-master93
buildbot-master95
buildbot-master96
buildbot-master97
buildbot-master98

In addition to any releng config changes, we'd need to rename/recreate/re-puppetize the hosts and modifying inventory and nagios.

Comment 1

3 years ago
These are all previous-generation AWS buildbot masters that I just removed in bug 1003898. I'll grab this bug and remove the stubs from puppet as well.
Status: NEW → ASSIGNED
Priority: -- → P2

Comment 2

3 years ago
Created attachment 8460201 [details] [diff] [review]
Remove unused masters from puppet
Attachment #8460201 - Flags: review?(pmoore)
(Reporter)

Comment 3

3 years ago
If we're just deleting, I can roll that into bug 1040926.

Updated

3 years ago
Attachment #8460201 - Attachment is obsolete: true
Attachment #8460201 - Flags: review?(pmoore)

Updated

3 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1040926
QA Contact: pmoore → mshal
You need to log in before you can comment on or make changes to this bug.