After we have switched to ATMO v2 we will keep running v1 until the end of January. The reason being that we have several jobs that still run on ATMO v1 and haven't been ported to v2 yet. We have given ample time to our users to do the move but just to be on the safe side we will not kill v1 just yet. Note that even if ATMO v1 will still be running users won't be able to access it.
Mark, could you please take care of this?
Yes, I can take care of this once we've ported the job formerly known as "executive summary" (see bug 1309574) which powers the dashboard at . At that time, we should also be able to kill the associated Redshift cluster.  http://metrics.services.mozilla.com/firefox-dashboard/
So... it looks like this machine has been killed, but not by me. The host was ec2-54-218-247-10.us-west-2.compute.amazonaws.com which I can't seem to find anywhere in cloudservices-aws-dev or cloudservices-aws-stage. Maybe it got "cleaned up" as part of some end of quarter housekeeping? Jason, do you know what happened to this server?
EC2 has detected degradation of the underlying hardware hosting your Amazon EC2 instance (instance-ID: i-028308576af386fb1) in the us-west-2 region. Due to this degradation, your instance could already be unreachable. After 2017-07-02 08:00 UTC your instance, which has an EBS volume as the root device, will be stopped. You can see more information on your instances that are scheduled for retirement in the AWS Management Console (https://console.aws.amazon.com/ec2/v2/home?region=us-west-2#Events) Since this instance is part of a autoscaling group once the instance was stopped it was terminated and replaced with a new instance. This new instance can be reached at ec2-54-149-171-135.us-west-2.compute.amazonaws.com. :mreid could you try to ssh into it and validate the instance? I am not able to ssh into since I don't have the ssh key.
This instance is located in 'cloudservices-aws-dev'.
Ok, I was able to log in and get old-atmo working. Thanks! Unfortunately it appears that people.m.o is now gone (which was a dependency of some of the jobs), so I can't re-run the jobs anymore anyways.
Status: NEW → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → FIXED
Old ATMO is finally dead. Long live new ATMO.
You need to log in before you can comment on or make changes to this bug.