Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Decommission Hub] [Wait until Aug 23] Neurohackademy #4613

Closed
7 of 19 tasks
sgibson91 opened this issue Aug 13, 2024 · 0 comments · Fixed by #4694
Closed
7 of 19 tasks

[Decommission Hub] [Wait until Aug 23] Neurohackademy #4613

sgibson91 opened this issue Aug 13, 2024 · 0 comments · Fixed by #4694
Assignees

Comments

@sgibson91
Copy link
Member

sgibson91 commented Aug 13, 2024

Summary

This is an event/workshop hub

Info

Task List

Phase I

  • Confirm with Community Representative that the hub is no longer in use and it's safe to decommission
  • 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/hub-deployment-guide/hubs/delete-hub/)

  • Manage existing home directory data (migrate data from the hub or delete it)
  • Manage existing cloud bucket data (migrate data, or delete it)
  • Delete the hub's authentication application on GitHub or CILogon (note CILogon removal requires the hub config in place)
  • 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.
  • 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
    • TIP: Run deployer use-cluster-credentials <cluster_name> before running the above commands
Phase III - Cluster Removal - Only necessary for single hub clusters

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:
  • Remove A record from Namecheap account
@sgibson91 sgibson91 changed the title [Decommission Hub] [Aug 23] Neurohackademy [Decommission Hub] [Wait until Aug 23] Neurohackademy Aug 14, 2024
@sgibson91 sgibson91 self-assigned this Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant