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] NeuroHackademy 2022 #1620

Closed
11 of 15 tasks
damianavila opened this issue Aug 11, 2022 · 5 comments · Fixed by #1721
Closed
11 of 15 tasks

[Decommission Hub] NeuroHackademy 2022 #1620

damianavila opened this issue Aug 11, 2022 · 5 comments · Fixed by #1721
Assignees

Comments

@damianavila
Copy link
Contributor

damianavila commented Aug 11, 2022

Summary

The hub is transient and event-focused hub and the event is over: #1300 (comment)

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 decribed in more detail in the docs at https://infrastructure.2i2c.org/en/latest/howto/hubs/delete-hub.html.)

  • Manage existing data (migrate data from the hub or delete it)
  • 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
  • Delete the hub's authentication application on auth0, GitHub or CILogon

Phase III - Cluster Removal

This phase is only necessary for single hub clusters.

@damianavila damianavila moved this from Ready to work to Needs Shaping / Refinement in DEPRECATED Engineering and Product Backlog Aug 11, 2022
@damianavila damianavila self-assigned this Aug 11, 2022
@damianavila damianavila moved this from Needs Shaping / Refinement to Waiting in DEPRECATED Engineering and Product Backlog Aug 11, 2022
@arokem
Copy link
Contributor

arokem commented Aug 12, 2022

Confirmed! You can take it down whenever you are ready. Thanks!

We've already migrated off data that we'd like to retain, so it is OK to delete everything stored there.

@colliand
Copy link
Contributor

I believe this event is over and the associated hub has been decommissioned. I am closing this issue.

Repository owner moved this from Waiting to Complete in DEPRECATED Engineering and Product Backlog Sep 20, 2022
@damianavila damianavila reopened this Sep 20, 2022
@damianavila
Copy link
Contributor Author

I reopened it because we need to merge #1721 and confirm some of the items listed above before closing it 😉.

Repository owner moved this from Waiting to Complete in DEPRECATED Engineering and Product Backlog Sep 21, 2022
@GeorgianaElena
Copy link
Member

I've merged the PR and I confirm I followed all the manual decommissioning steps in the docs

@damianavila
Copy link
Contributor Author

Thanks @GeorgianaElena!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

4 participants