Closed
Bug 1152225
Opened 9 years ago
Closed 9 years ago
Decom tbpl.mozilla.org and tbpl-dev.allizom.org
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: cliang)
References
Details
(Keywords: spring-cleaning, Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/907] )
Broken out of bug 1149753 comment 8. TBPL has been end of lifed. We're keeping around the prod domain for a while, since we're redirecting it to Treeherder (this has been set up in bug 1149753), however we do not need the dev site/domain (tbpl-dev.allizom.org) at all, so can remove it entirely. The DB side has been taken care of already in bug 1149564 comment 10. Thanks!
Reporter | ||
Comment 1•9 years ago
|
||
Making this about both dev and prod - *however* for prod we need to keep the DNS entries for tbpl.mozilla.org since it's required for the redirects set up by bug 1149753.
Depends on: 1149753
Keywords: spring-cleaning
Summary: Decom tbpl-dev.allizom.org → Decom tbpl.mozilla.org and tbpl-dev.allizom.org
Reporter | ||
Updated•9 years ago
|
Assignee | ||
Updated•9 years ago
|
Assignee: server-ops-webops → cliang
Assignee | ||
Updated•9 years ago
|
Assignee | ||
Comment 2•9 years ago
|
||
Ed: There appears to be an old set of DNS records for tbpl.allizom.org. Should they be deleted? tbpl.allizom.org A 63.245.208.168 63.245.208.168 PTR tbpl.mozilla.org [The PTR is not needed for production tbpl.mozilla.org; that is currently a CNAME to static-redirect.zlb.phx.mozilla.net.)
Flags: needinfo?(emorley)
Assignee | ||
Comment 3•9 years ago
|
||
* Deleted A record for tbpl-dev.allizom.org (63.245.217.82) * Deleted puppet-related config pieces for puppet. $ svn commit -m "Remove tbpl web configuration pieces from puppet (BZ 1152225)" date Deleting modules/webapp/files/genericrhel6/etc-httpd/domains/tbpl.mozilla.org.conf Deleting modules/webapp/files/genericrhel6-dev/etc-httpd/domains/tbpl-dev.allizom.org.conf Sending modules/webapp/manifests/genericrhel6.pp Transmitting file data . Committed revision 103318.
Reporter | ||
Comment 4•9 years ago
|
||
(In reply to C. Liang [:cyliang] from comment #2) > Ed: There appears to be an old set of DNS records for tbpl.allizom.org. > Should they be deleted? > > tbpl.allizom.org A 63.245.208.168 > 63.245.208.168 PTR tbpl.mozilla.org > > [The PTR is not needed for production tbpl.mozilla.org; that is currently a > CNAME to static-redirect.zlb.phx.mozilla.net.) Yes please :-)
Flags: needinfo?(emorley)
Assignee | ||
Comment 5•9 years ago
|
||
* Records in comment #2 have been deleted. * Directories cleaned up off of genericadm.private.phx1 * In double-checking things, it looked like the traffic IP group for the tbpl database was still present on the load balancer. Removed it (tbpl-zlb-rw.db.phx1.mozilla.com (10.8.70.171)).
Reporter | ||
Comment 6•9 years ago
|
||
Visiting https://tbpl-dev.allizom.org gives a 403 rather than a DNS resolution error (or equivalent) - expected?
Comment 7•9 years ago
|
||
(In reply to Ed Morley [:emorley] (formerly :edmorley) from comment #6) > Visiting https://tbpl-dev.allizom.org gives a 403 rather than a DNS > resolution error (or equivalent) - expected? Yessir. *.allizom.org will resolve in DNS automatically to a "default" IP.
Assignee | ||
Comment 8•9 years ago
|
||
Yergh. Unfortunately, yes. http://tbpl-dev.allizom.org redirects correctly to https://allizom.org via a combination of catch-all addresses + a redirect. The virtualhost setup doesn't have quite as wide a catch-all and (I believe) ends up redirecting to the local virtualhost that has authentication restraints. I need to ping one of the other webop folks to see if there is a historical or technical reason not to have as wide a catch-all on the HTTPS side. You're not the first person to point this out. =)
Assignee | ||
Comment 9•9 years ago
|
||
See https://bugzilla.mozilla.org/show_bug.cgi?id=1149564#c21 for other relevant pieces of puppet decomm.
Reporter | ||
Comment 10•9 years ago
|
||
Thank you for the explanation - not a problem at all - was just wondering if it meant there was more that could be Killed With Fire :-)
Assignee | ||
Comment 11•9 years ago
|
||
* Removed tbpl related entries from dnsmasq test file * Removed smokeping entry for tbpl.mozilla.org (BZ 1152225) * Changed tbpl.mozilla.org entry in dnsmasq test file to match reality. * Archived a copy of the web site to genericadm:/mnt/spring_cleaning_backups/generic/ [db already gone] Holding this open until Monday, just in case something else pops up.
Assignee | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 12•8 years ago
|
||
This is long resolved, but for propriety I'm adding that I just removed "tree.mozilla.org" and "thetree.mozilla.org", which long ago pointed at tbpl.mozilla.org. They haven't worked in quite some time (just 403'ing), so this is a no-op... but it helps with some related infrastructure cleanup work (over in bug 1215248)
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•