807877 - review source IPs for b1/b2 db's before rename

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

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

joduinn asked for a review of the source IPs for the b1 and b2 db's.  From a bit over 24h of sampling (enough to catch daily crontasks), here's the list, narrowed down to releng-related hosts (and a bonus host for coop):

17.48.12.10.in-addr.arpa domain name pointer slavealloc.build.scl1.mozilla.com.
43.48.26.10.in-addr.arpa domain name pointer cruncher.srv.releng.scl3.mozilla.com.
88.81.22.10.in-addr.arpa domain name pointer web1.releng.webapp.scl3.mozilla.com.
89.81.22.10.in-addr.arpa domain name pointer web2.releng.webapp.scl3.mozilla.com.
128.74.22.10.in-addr.arpa domain name pointer relengweb1.dmz.scl3.mozilla.com.
138.75.22.10.in-addr.arpa domain name pointer relengwebadm.private.scl3.mozilla.com.

Recall that not all of these hosts are necessarily using the wrong name, since the IPs are not changing.

The new date to remove the old names is Monday.  I think all of the above hosts have already been validated, but please double-check.  Find me with questions.

Comment 1

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

Today's the day to delete these names.  Are releng's checks complete?

Comment 2

[Hal Wine [:hwine] use NI!]

Coop - I think you worked on these most recently - any concerns about the above traffic?

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

I don't know what on cruncher might be using the wrong name, personally I have buildbot-ro-vip.db.scl3 in my configs.

Comment 4

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

See "Recall" in comment 0 - this is a list of hosts using either the old or the new name.

Comment 5

[Chris Cooper [:coop] (he/him)]

(In reply to Dustin J. Mitchell [:dustin] from comment #0) 
> 17.48.12.10.in-addr.arpa domain name pointer
> slavealloc.build.scl1.mozilla.com.

slavealloc prod and staging are already using devtools-rw-vip

> 43.48.26.10.in-addr.arpa domain name pointer
> cruncher.srv.releng.scl3.mozilla.com.

buildfaster is already using buildbot-ro-vip
last-job-per-slave is now using devtools-ro-vip (*)

> 88.81.22.10.in-addr.arpa domain name pointer
> web1.releng.webapp.scl3.mozilla.com.

No access.

> 89.81.22.10.in-addr.arpa domain name pointer
> web2.releng.webapp.scl3.mozilla.com.

No access.

> 128.74.22.10.in-addr.arpa domain name pointer
> relengweb1.dmz.scl3.mozilla.com.

clobberer is now using devtools-rw-vip (*)

> 138.75.22.10.in-addr.arpa domain name pointer
> relengwebadm.private.scl3.mozilla.com.

No access.

So I found and fixed two instances (*) of us using the old CNAME: last-job-per-slave and clobberer.

FWIW, I haven't heard of the hosts I cannot access (web1, web2, relengwebadm) prior to this bug. That doesn't mean they shouldn't be checked, but it's also unlikely they have releng-critical services running on them.

Comment 6

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

Correct - they're part of the new releng cluster that is still stalled waiting for releng approval - bug 774354.

So we're good to go?

Comment 7

[Hal Wine [:hwine] use NI!]

good to go, given:
 - lets do some non-Friday morning
 - please check with buildduty - just in case
 - you'll take care of whatever is actively querying the db from the not-yet-up cluster

Comment 8

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

I'll do it tomorrow (Tuesday).  I'll check with buildduty first.

The new cluster has been using the right names since it was built, so nothing to worry about there.