924199 - Shutdown server that runs telemetry-dash.mozilla.org - after migration to S3

Status: RESOLVED FIXED

(Infrastructure & Operations :: IT-Managed Tools, task, P4)

Description

[Jonas Finnemann Jensen (:jonasfj)]

The server that runs cron jobs for telemetry dashboard on mango, and the server that hosts the generated data on telemetry-dash.mozilla.org should be shutdown.

With bug 921077 we hosting telemetry dashboard on S3 and telemetry-dash.mozilla.org will no longer point to whatever server currently starts the map/reduce job on mango.

Note, this should not be done before telemetry-dash.mozilla.org is pointing to:
http://telemetry-dashboard-web.s3-website-us-east-1.amazonaws.com/

See bug 921077, which is about that...

Comment 1

[Jonas Finnemann Jensen (:jonasfj)]

As suggested by :solarce on bug 924551#2, I'm moving this to Web Ops asking for the server that ran telemetry-dash.mozilla.org before migration to be decommissioned.

Telemetry-dashboard is currently hosted in S3 and updated by EC2 instances, so there's no need to keep this around anymore.
I'll begin merging AWS specific code to the master branch for telemetry-dashboard soon, so existing the cron job will start to fail and make noise.

Comment 2

[Jake Maul [:jakem]]

This is on the static cluster in phx1... so no servers to remove, but some config to purge. I think :phrawzty set this up originally (not that he has to tear it down, but just for reference).

Comment 3

[Daniel Maher [:phrawzty]]

I've disabled the Puppet elements, removed the appropriate cron jobs, and removed the telemetry-dash user account on staticadm.