Closed Bug 1310254 Opened 9 years ago Closed 9 years ago

decom aus.mozilla.org

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Atoll, Assigned: danielh)

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/3547])

Attachments

(1 file)

Per bug 1309997, let's decom aus.mozilla.org. Some level of auditing of weblogs and explicit approvals requested in bug from Balrog and Product Delivery teams should occur before we proceed with removing it from DNS and then in a while from our cluster. This deprecates bug 1309997, as there's no point in upgrading it to HTTPS and applying security rules when it can simply be shut down instead. If this bug is closed with being fixed, please reopen bug 1309997.
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/3547]
:bhearsum: bug 1309997 comment 3 contains something resembling your approval for us to decom this site. Who should we speak to besides you to confirm that this is an acceptable path?
Flags: needinfo?(bhearsum)
(In reply to Richard Soderberg [:atoll] from comment #1) > :bhearsum: bug 1309997 comment 3 contains something resembling your approval > for us to decom this site. Who should we speak to besides you to confirm > that this is an acceptable path? As far as I'm concerned, aus.mozilla.org is already decom'ed - it hasn't served updates in a very long time. Do whatever you want with it :)
Flags: needinfo?(bhearsum)
Assignee: server-ops-webops → rsoderberg
Assignee: rsoderberg → dhartnell
Hey Ben, Thank you for the update. I'm performing this decom right now but I do have one more question for you. Looking through some of our Apache configs, I found that update.mozilla.org has some rewrite rules in place that appear to direct traffic to aus.mozilla.org. I want to avoid disrupting anything that relies on the connection to update.mozilla.org. Do you have any concerns about that?
Flags: needinfo?(bhearsum)
(In reply to Daniel Hartnell [:danielh] from comment #3) > Hey Ben, > > Thank you for the update. I'm performing this decom right now but I do have > one more question for you. Looking through some of our Apache configs, I > found that update.mozilla.org has some rewrite rules in place that appear to > direct traffic to aus.mozilla.org. > > I want to avoid disrupting anything that relies on the connection to > update.mozilla.org. Do you have any concerns about that? That's a new one to me, but it is most definitely not involved with the update process for Firefox 3.0 or later. I think it's safe to kill it.
Flags: needinfo?(bhearsum)
FWIW, I found a mention of it in a 17-year-old bug: http://update.mozilla.org/themes/?application=firefox And it's part of Firefox 0.10: > Mozilla Firefox Preview Release Release Notes > https://www.mozilla.org/en-US/firefox/releases/0.10.html > You can now open blocked popups, and the Extension install system now blocks all attempts to install software from sites other than update.mozilla.org. Someone should grep m-c and make sure it's not mentioned anywhere.
The Webops config for the domain was imported from pre-2009 static cluster, so no version history is available for it.
latest commit ec1f8a3e57fbf083cce56d663ef59a608bb69e9a
/me agrees with :bhearsum in comment 4 -- time for it to go
Thanks everyone :) I'll keep a record of what I've changed here: - DNS: Removed Inventory CNAME record: aus.mozilla.org -> static-non-ssl.external.scl3.mozilla.com - Puppet: Removed aus.mozilla.org.conf and update.mozilla.org.conf Apache configs from Puppet - Content: Delete www and src content from static admin node and corresponding web heads - Content: Deleted aus.m.o Apache logs for both sites from web heads - Zeus: No SSL certificates found for update or aus.m.o Marking as solved.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
(In reply to Richard Soderberg [:atoll] from comment #5) > FWIW, I found a mention of it in a 17-year-old bug: > > http://update.mozilla.org/themes/?application=firefox > > And it's part of Firefox 0.10: > > > Mozilla Firefox Preview Release Release Notes > > https://www.mozilla.org/en-US/firefox/releases/0.10.html > > You can now open blocked popups, and the Extension install system now blocks all attempts to install software from sites other than update.mozilla.org. > > Someone should grep m-c and make sure it's not mentioned anywhere. For posterity, I did this last night - and it's not.
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: