1074342 - [tracker] Eliminate "outlier hosts"

Status: RESOLVED INCOMPLETE

(Release Engineering :: General, defect)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

Bug 1073601 is all about "outlier hosts" that are not managed by puppet.  So the bug nicely encapsulates sources of needless friction, risk, and slowness.

We should have zero outliers.  One we've accomplished that, it should become the law of the land.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

* partner-repack1.srv.releng.scl3.mozilla.com
* vcssync1.srv.releng.usw2.mozilla.com
* vcssync2.srv.releng.usw2.mozilla.com
* github-sync1-dev.dmz.scl3.mozilla.com
* github-sync1.dmz.scl3.mozilla.com
* github-sync3.dmz.scl3.mozilla.com
* funsize AMIs
* blobber AMIs
* b2g-snapshot-mapper (??)
* releng-jenkins01

Comment 2

[Chris AtLee [:catlee]]

cruncher?

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

I'd love to, but slightly different project -- cruncher is at least puppetized, which means its configuration is maintained by (infra) puppet and monitored by opsec.  This bug's about finding and fixing everything that's slipped through the cracks and isn't on *any* configuration management or opsec monitoring radars.

I should add the AWS proxy instance to this list, I think..

Comment 4

[Julien Vehent]

Based on what MIG sees, the github sync nodes are currently managed by infra puppet:

                 name                  | operator |                        ips                        
---------------------------------------+----------+---------------------------------------------------
 github-sync1-dev.dmz.scl3.mozilla.com | IT       | ["10.22.74.67/24","fe80::222:99ff:fe36:8622/64"]
 github-sync3.dmz.scl3.mozilla.com     | IT       | ["10.22.74.134/24","fe80::e611:5bff:fee0:990/64"]
 github-sync1.dmz.scl3.mozilla.com     | IT       | ["10.22.74.72/24","fe80::222:99ff:fe37:702/64"]

The proxy instances, if you are referring to Proxxy, are managed by puppetagain:

                 name                  | operator |                        ips                        
---------------------------------------+----------+---------------------------------------------------
 proxxy1.srv.releng.scl3.mozilla.com   | releng   | ["10.26.48.46/22","fe80::e611:5bff:fed9:745c/64"]
 proxxy1.srv.releng.use1.mozilla.com   | releng   | ["10.134.100.191/24","fe80::1065:f1ff:fe7b:400e/64"]
 proxxy1.srv.releng.usw2.mozilla.com   | releng   | ["10.132.100.234/24","fe80::466:ceff:fe4f:1b13/64"]

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

So

Hosts:
* partner-repack1.srv.releng.scl3.mozilla.com
* vcssync1.srv.releng.usw2.mozilla.com
* vcssync2.srv.releng.usw2.mozilla.com

Cloudy Stuff:
* funsize AMIs
* blobber AMIs
* b2g-snapshot-mapper (??)
* releng-jenkins01

Comment 6

[Dustin J. Mitchell [:dustin] (he/him)]

Adding the AWS proxxy instances, which are hand-rolled and have a few issues like bug 1134468.

Comment 7

[Dustin J. Mitchell [:dustin] (he/him)]

dev-stage01 - https://bugzilla.mozilla.org/show_bug.cgi?id=808025

So the current list of odd ducks is:

* partner-repack1.srv.releng.scl3.mozilla.com
* vcssync1.srv.releng.usw2.mozilla.com
* vcssync2.srv.releng.usw2.mozilla.com
* github-sync1-dev.dmz.scl3.mozilla.com
* github-sync1.dmz.scl3.mozilla.com
* github-sync3.dmz.scl3.mozilla.com
* proxxy1.srv.releng.use1.mozilla.com
* proxxy1.srv.releng.usw2.mozilla.com
* dev-stage01.srv.releng.scl3.mozilla.com
* funsize AMIs
* blobber AMIs
* b2g-snapshot-mapper (??)
* releng-jenkins01