[Decommission Hub] isea.aws.2i2c.cloud

jmunroe commented 3 months ago

Summary

This lead did not progress to a signed contract and the community chose to go with a different vendor instead. It was never used -- no user data should be on the hub.

Info

Community Representative: N/A (community rep on record is not longer with UW ISEA)
Link to New Hub issue: https://github.com/2i2c-org/infrastructure/issues/4090
Proposed end date: 2024-07-05

Task List

Phase I

[x] Confirm with Community Representative that the hub is no longer in use and it's safe to decommission
[x] Confirm if there is any data to migrate from the hub before decommissioning
- [ ] If yes, confirm where the data should be migrated to
- [ ] Confirm a 2i2c Engineer has access to the destination in order to complete the data migration
- [x] If no, confirm it is ok to delete all the data stored in the user home directories

Phase II - Hub Removal

(These steps are described in more detail in the docs at https://infrastructure.2i2c.org/hub-deployment-guide/hubs/delete-hub/)

[x] Manage existing home directory data (migrate data from the hub or delete it)
[ ] Manage existing cloud bucket data (migrate data, or delete it)
[x] Delete the hub's authentication application on GitHub or CILogon (note CILogon removal requires the hub config in place)
[x] Remove the appropriate config/clusters/<cluster_name>/<hub_name>.values.yaml files. A complete list of relevant files can be found under the appropriate entry in the associated cluster.yaml file.
[x] Remove the associated hub entry from the config/clusters/<cluster_name>/cluster.yaml file.
[x] Remove the hub deployment
- helm --namespace HUB_NAME delete HUB_NAME
- kubectl delete namespace HUB_NAME
- TIP: Run deployer use-cluster-credentials <cluster_name> before running the above commands

Phase III - Cluster Removal

This phase is only necessary for single hub clusters.

[ ] Remove the cluster's datasource from the central Grafana with:
- deployer grafana central-ds remove <cluster_name>
[ ] Run terraform plan -destroy and terraform apply from the appropriate workspace, to destroy the cluster
[ ] Delete the terraform workspace: terraform workspace delete <NAME>
[ ] Delete the terraform values file under the projects folder associated with the relevant cloud provider (e.g. terraform/gcp/projects/ for GCP)
[ ] Remove the associated config/clusters/<cluster_name> directory and all its contents
Remove the cluster from CI:
- [ ] deploy-hubs.yaml
- [ ] deploy-grafana-dashboards.yaml
[ ] Remove A record from Namecheap account

jmunroe commented 3 months ago

There may still some further action relating to this hub -- pending a conversation to occur next week.

yuvipanda commented 2 months ago

@jmunroe any updates?

jmunroe commented 2 months ago

This can be put back on the Engineering board for scheduling in the next iteration.

haroldcampbell commented 1 month ago

This needs to be done ASAP since it was opened from Jul

jmunroe commented 1 month ago

Not as critical as ASAP that ... I only unpaused this issue on Monday.

sgibson91 commented 1 month ago

Phase 3 is not required as ISEA is on a shared cluster

2i2c-org / infrastructure