Closed Bug 1003898 Opened 8 years ago Closed 8 years ago

Ensure all AWS buildbot masters are in inventory

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P2)

x86_64
Windows 7

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Assigned: coop)

References

Details

Per :dustin,

AWS Buildbot Masters should *all* be in inventory, especially because as we add/move/whatever slaves we'll be missing flows whenever we need flows to "all buildbot masters"

Assigning to ben initially as he added bm01->04 which are currently not in inventory. feel free to reassign though
I don't think there was any buildbot masters in the "systems" section of inventory when I created these.

AFAIK, we don't add AWS machines to that section in the first place. If that's changed, that's fine - but we probably have some docs/scripts to update in that case.
Flags: needinfo?(rail)
Flags: needinfo?(catlee)
We don't usually add slaves to the "systems" section, only to DNS. In the nearest future it won't be necessary.

AFAIK, we may need to have the masters in the inventory to simplify netflow bugs. I'd rather not have them in the "system" section unless we have tools to add/remove masters.
Flags: needinfo?(rail)
We've not done this previously. If netops is working on some magic to let us manage flows to "all buildbot masters" that requires us to put them into inventory, that's great. Otherwise, is there an immediate benefit to this?
Flags: needinfo?(catlee)
Well, currently there are *some* masters in inventory, which led me to suggest those for a flow request.  I think we can agree we should be consistent.

If AWS masters are *not* in inventory, then I'm not sure how best to manage flows for them, as that leaves me without a reliable common source of information about what the current set of Buildbot masters is.
I added buildbot-master01 through 06 to the system sections. I'm not sure if there's more missing, but those are the ones I created.
Assignee: bhearsum → nobody
Assignee: nobody → coop
All masters are in inventory already, but based on the current contents of production-masters.json, there are some that need to be removed:

> buildbot-master55.srv.releng.use1.mozilla.com
> buildbot-master56.srv.releng.usw2.mozilla.com
> buildbot-master57.srv.releng.use1.mozilla.com
> buildbot-master58.srv.releng.usw2.mozilla.com
> buildbot-master59.srv.releng.use1.mozilla.com
> buildbot-master60.srv.releng.usw2.mozilla.com
> buildbot-master61.srv.releng.use1.mozilla.com
> buildbot-master62.srv.releng.use1.mozilla.com
> buildbot-master63.srv.releng.use1.mozilla.com
> buildbot-master64.srv.releng.usw2.mozilla.com
> buildbot-master65.srv.releng.usw2.mozilla.com
> buildbot-master66.srv.releng.usw2.mozilla.com
> buildbot-master80.srv.releng.usw2.mozilla.com
> buildbot-master90.srv.releng.use1.mozilla.com
> buildbot-master92.srv.releng.use1.mozilla.com
> buildbot-master93.srv.releng.usw2.mozilla.com
> buildbot-master95.srv.releng.usw2.mozilla.com
> buildbot-master96.srv.releng.use1.mozilla.com
> buildbot-master97.srv.releng.usw2.mozilla.com
> buildbot-master98.srv.releng.use1.mozilla.com
Status: NEW → ASSIGNED
Priority: -- → P2
These have all been removed from inventory.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
buildbot-master66.srv.releng.usw2.mozilla.com added back since it's actually running stuff, just not buildbot.
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.