decom anemometer: IT puppet webapp::anemometer and bits on scalebase1.db.scl3

RESOLVED FIXED

Status

RESOLVED FIXED
2 years ago
7 months ago

People

(Reporter: atoll, Assigned: ericz)

Tracking

Details

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

Bug 862898 implemented Anemometer on the scalebase cluster in PHX1. Is this software still in use? If so, we need to fix this URL

modules/webapp/manifests/anemometer.pp:#       "hg clone http://hg.mozilla.org/qa/testcase-data/ .":

To clone from https://hg instead. I notice that it's commented out, so maybe it can just be removed instead.

(If anemometer is not in use any longer, then this should become a 'decom anemometer' bug.)
Group: metrics-private → mozilla-employee-confidential
Clearing all secgroups, because this doesn't need to be secret.
Group: mozilla-employee-confidential
I'm not aware of our current use of this.
Assignee: nobody → rwatson
This is deployed as a website to scalebase1.db.scl3. If the weblogs on that host confirms it's unused, you're a winner.
Nothing in the weblogs other that 127.0.0.1/server-status for a long time.

Doesn't look like it's used, I suggest stopping apache or the server and seeing if anyone yells loud enough, otherwise I can't see any usage.
Summary: Update HG url in anemometer config → decom anemometer: IT puppet webapp::anemometer and bits on scalebase1.db.scl3
I didn't get time to fully investigate, but the parts I did investigate led me to the conclusion that nobody cares about these machines. I believe they are good to decom.
Assignee: rwatson → nobody
:mpressman, can scalebaseX.db.scl3 be decom'd as a group? If so, that simplifies this dramatically.
Flags: needinfo?(mpressman)
Yep, these can be gone!
Flags: needinfo?(mpressman)
mysqld is now shutdown on scalebase[12].db.(scl3|phx1).mozilla.com

waiting on webops to weigh in on whether they need the newrelic db monitors which run on those hosts.

Updated

9 months ago
Assignee: nobody → server-ops-webops
Component: Other → WebOps: Other
Product: Data & BI Services Team → Infrastructure & Operations
QA Contact: mpressman → smani

Updated

9 months ago
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/6150]
If the DB servers can be shutdown, it seems extremely unlikely that WebOps would need to run New Relic on the now-shutdown servers.

Shyam, rubber-stamp "permission to decom scalebaseX.db.scl3|phx1 *including* New Relic" requested?
Flags: needinfo?(smani)
To clarify: the newrelic monitors are monitoring a bunch of *other* databases (list sent to Shyam under separate cover), not the databases on the scalebase hosts themselves.
That makes more sense - thanks! Clearing needinfo, triage queue is enough.
Flags: needinfo?(smani)
(Assignee)

Comment 12

8 months ago
Closing invalid as Scalebase is now shut down.  Thanks everyone.
Status: NEW → RESOLVED
Last Resolved: 8 months ago
Resolution: --- → INVALID
(Assignee)

Comment 13

8 months ago
Reopening for the removal of the puppet module, overlooked the forest for the trees there.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---

Updated

8 months ago
Assignee: server-ops-webops → eziegenhorn

Updated

8 months ago
Assignee: eziegenhorn → server-ops-webops

Updated

8 months ago
Assignee: server-ops-webops → eziegenhorn
(Assignee)

Comment 14

7 months ago
Removed anemometer-related puppet files in git commit 85d8f66f0805a262a534b4c2168b4fb8ec7bc79c.  There are still scalebase-related files in puppet/manifests/nodes/db_mysql/newrelic.pp which should be removed when we do the full decom, see bug 1442257.
Status: REOPENED → RESOLVED
Last Resolved: 8 months ago7 months ago
Resolution: --- → FIXED
See Also: → bug 1442257
You need to log in before you can comment on or make changes to this bug.