Closed Bug 1287462 Opened 9 years ago Closed 9 years ago

Decommission legacy mesos cluster

Categories

(Participation Infrastructure :: Community Ops, task)

Product:
Participation Infrastructure
Component:
Community Ops
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nemo-yiannis, Assigned: nemo-yiannis)

References

Details

At the moment we are maintaining a legacy mesos cluster that got replaced by the one described here [1]. We need to remove all * legacy EC2 instances * legacy RDS instances * legacy ELB instances * legacy route53 entries [1] https://wiki.mozilla.org/images/0/07/Ca6cacef9dff91f5c3cfa1ec271f90bac2fb41fe.png
Depends on: 1287465
Started decommissioning legacy cluster * Stopped all ec2 instances * For archival purposes took snapshot of all volumes * Deleted all unused ELB instances
Assignee: nobody → jgiannelos
* Deleted legacy autoscaling groups and configurations
* Deleted legacy *.paas.mozilla.community DNS entry * Deleted legacy VPN internal hosted zone "mesos.partinfra.internal"
* Deleted legacy takebacktheweb RDS instance
The last action item pending is to delete (the already stopped) ec2 instances and volumes. :yalam96, pierros What do you think? Do you want to wait for a day or two?
Flags: needinfo?(yousef)
Flags: needinfo?(pierros)
Sure, we can wait a bit.
Flags: needinfo?(yousef)
Instances are down for 5 days. I am going ahead to delete what's left in EC2.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(pierros)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.