Both in AWS, both have SSL certificates assigned, but both seem broken stooge.mozillalabs.com stooge-dev.mozillalabs.com
I believe :edwong can help determine whether Stooge is still in use or can be shutdown, or at least can give us a next-hop to ask.
:yvan should know
Flags: needinfo?(edwong) → needinfo?(yboily)
Julien was (iirc) doing some stooge related work after Stefan moved to the ios project. If Julien doesn't need it, then I say demise it; we will stand up a new instance when we resume work on stooge in q3.
Flags: needinfo?(yboily) → needinfo?(jvehent)
That's hosted in aws moz-opsec, back from when I helped stefan set it up, but it's been offline for a while now and no one has missed it, so I'd say kill it? I'll destroy the instances on my end.
Summary: Determine if stooge(-dev).mozillalabs.com should still be alive → decom stooge(-dev).mozillalabs.com
stooge-dev.mozillalabs.com CNAME ec2-54-83-177-180.compute-1.amazonaws.com stooge.mozillalabs.com CNAME stooge-lb-prod-1-189252413.us-east-1.elb.amazonaws.com Removed the above two DNS entries. Setting needinfo? :ulfr to confirm the EC2/ELB teardown (in which Amazon account?).
Instances, ELB, EIPs and VPC deleted from moz-opsec. Feel free to decom the CNAMEs.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.