[Decommission Hub] Catalyst Cooperative

[colliand]

Summary

Catalyst Cooperative (CC) carries out their data analysis group using local Jupyter installed on laptops. The data sizes and compute requirements for their work have not benefited from cloud-based JupyterHub. As a result, and after a virtual meeting with @zaneselvans, this hub should be commissioned.

There may be future opportunities for 2i2c to engage with Catalyst Cooperative. CC generates and shares open data on the energy system. This data, and associated analyses, are used by various stakeholders to understand and improve the energy system. For example, stakeholders use CC data and shared computational narratives to advocate for transitions from fossil fuels over to renewable energy sources. CC needs improved methods for sharing interactive computational narratives. Mybinder is too slow and does not offer enough compute for their needs. Some other ideas were discussed and will be shared with the 2i2c team internally.

Info

• Community Representative: @zaneselvans
• Link to New Hub issue:
• Proposed end date: 2023-06-30

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
  • [ ] 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/en/latest/hub-deployment-guide/hubs/other-hub-ops/delete-hub.html)

• [ ] Manage existing data (migrate data from the hub or delete it)
• [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.
• [ ] Remove the hub deployment
  • helm --namespace HUB_NAME delete HUB_NAME
  • kubectl delete namespace HUB_NAME
• [x] Delete the hub's authentication application on auth0, GitHub or CILogon

Phase III - Cluster Removal

This phase is only necessary for single hub clusters.

• [ ] Run terraform plan -destroy and terraform apply from the appropriate workspace, to destroy the cluster
• [ ] Delete the terraform workspace: terraform workspace delete <NAME>
• [ ] Remove the associated config/clusters/<cluster_name> directory and all its contents
• Remove the cluster from CI:
  • [ ] deploy-hubs.yaml
  • [ ] validate-clusters.yaml
• [ ] Remove the cluster from the list of grafana datasources at https://grafana.pilot.2i2c.cloud/datasources
• [ ] Remove A record from Namecheap account

[yuvipanda]

@colliand can you confirm wether the data is to be deleted too?

[colliand]

Yes. Let's keep the hub up through June so that @zaneselvans can pull down any data or code. We can then decommission and delete everything.

[zaneselvans]

@yuvipanda is there a way to tell whether there are any users that have saved data up there that's been touched recently in their user-space? All of the data in the shared directory is from archives that exist elsewhere and doesn't need to be preserved but it would be nice if I could at least notify folks who might have data there that they want to pull down before we pull the plug.

[yuvipanda]

@zaneselvans if you look at the admin panel after logging in, you should be able to see when they last logged in. That should be able to help?

[damianavila]

@sgibson91 will be leading the decommissioning once we get the green light.

I now realized @colliand suggested keeping the hub up through June, although it might be the case we can decommission it earlier if @zaneselvans already got all the information he needed.

@zaneselvans, can you update us on your status to see if we can proceed with the decommission on the current sprint cycle? Thanks!!

[sgibson91]

@zaneselvans are we good to decommission this hub now?

[zaneselvans]

Ack sorry @sgibson91 @damianavila. Yes, we are good go go with the decommissioning of the hub.

[sgibson91]

Hub has been decommissioned!