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] snowex.uwhackweek #2031

Closed
8 of 17 tasks
consideRatio opened this issue Jan 9, 2023 · 5 comments · Fixed by #2059
Closed
8 of 17 tasks

[Decommission Hub] snowex.uwhackweek #2031

consideRatio opened this issue Jan 9, 2023 · 5 comments · Fixed by #2059
Assignees

Comments

@consideRatio
Copy link
Member

consideRatio commented Jan 9, 2023

Summary

It was a hack event that is now over.

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
    UPDATE: Erik asked Scott via freshdesk ticket about this
    • 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)
  • 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.

@scottyhq
Copy link
Contributor

Thanks @consideRatio !

Confirm if there is any data to migrate from the hub before decommissioning

No. You can go ahead and wipe everything.

Out of curiosity though, what is the general procedure for this? Are there docs with recommended options (e.g. an S3 bucket, lab server with a big usb-mounted hard drive, etc.) It could be something we want to do in the future.

@consideRatio
Copy link
Member Author

@scottyhq for now it seems we don't have such policies for migrating data well defined, see this documentation: https://infrastructure.2i2c.org/en/latest/hub-deployment-guide/hubs/other-hub-ops/delete-hub.html#migrate-data

I recall Yuvi has done some work to package things into s3 buckets and provide links for users though.

@consideRatio
Copy link
Member Author

@scottyhq I see a S3 snowex-scratch bucket, is this fine to remove as well?

@consideRatio
Copy link
Member Author

@scottyhq there is still https://staging.uwhackweeks.2i2c.cloud up and running as I haven't worked to tear everything down, but only the snowex hub part of the uwhacksweek cluster.

If everything uwhackweeks related should be cleaned up, there are further actions to take for us. Let us know if that is the case!

@scottyhq
Copy link
Contributor

@scottyhq I see a S3 snowex-scratch bucket, is this fine to remove as well?

Yes!

If everything uwhackweeks related should be cleaned up

Yes, we're not anticipating any events in the near future so everything can be removed.

Thanks @consideRatio !

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

Successfully merging a pull request may close this issue.

2 participants