Page MenuHomeSoftware Heritage

Clean up unused azure vms or services
Closed, MigratedEdits Locked

Description

We still have running and no longer used vms (and maybe services). Let's investigate
what really needs to run and stop what's not needed (and stop then destroy those):

|------------------+---------+------------+---------------------------------------------------------------|
| node             | status  | new status | note                                                          |
|------------------+---------+------------+---------------------------------------------------------------|
| cassandra[01-06] | stopped | dropped    | no longer required                                            |
| mirror-test      | running | dropped    | no longer required [in terraform manifest]                    |
| dbreplica0       | running | dropped    | softwareheritage db replication in azure (unused)             |
| dbreplica1       | running |            | replicated softwareheritage-indexer db (sole indexer db copy) |
| storage01        | running |            | required but some services can be stopped                     |
| storage02        | stopped | dropped    | no longer required                                            |
| ns0              | running |            | required: secondary azure dns                                 |
| vangogh          | running |            | required: vault server                                        |
| worker[01-13]    | running |            | indexer and cooker workers                                    |
| webapp0          | stopped | dropped    | associated dangling resources left-over                       |
|------------------+---------+------------+---------------------------------------------------------------|

Event Timeline

ardumont updated the task description. (Show Details)

There are also:

ardumont updated the task description. (Show Details)
ardumont updated the task description. (Show Details)

After using terraform to clean up the no longer used resources, we still had to remove some of leftovers manually:

  • cassandra-euwest (left over after removing cassandra nodes and resources)
  • resource group: euwest-mirror-test (including a pgmirror0 db)
  • disk os-storage02 (leftover after removing storage02 node and resources)
ardumont changed the task status from Open to Work in Progress.Feb 18 2022, 4:50 PM
ardumont moved this task from Backlog to in-progress on the System administration board.

Extra resources removal:

  • dbreplica0 vm and associated resources
  • webapp0 associated resources

There are also:

  • a LB for the postgresql replicas: (swh-postgres-public)

destroyed.

  • 2 cosmos db for provenance (almost empty)

euwest-provenance resource group drop ongoing.
That will take care care of this as well.

  • 2 cosmos db for provenance (almost empty)

euwest-provenance resource group drop ongoing.
That will take care care of this as well.

Finally "Deleted resource group euwest-provenance".

So we are done with the clean up of unused azure resources.

ardumont claimed this task.
ardumont moved this task from deployed/landed/monitoring to done on the System administration board.