-
Notifications
You must be signed in to change notification settings - Fork 64
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
Switch VEDA staging hub from EFS to jupyter-home-nfs server #4821
Switch VEDA staging hub from EFS to jupyter-home-nfs server #4821
Conversation
Merging this PR will trigger the following deployment actions. Support and Staging deployments
Production deployments
|
@sunu I don't know if you want to make changes here or just merge it and make a new PR for figuring out the NFS filepath mount. You have merge rights so I'll leave it up to you :) |
Newer version of jupyter-home-nfs uses a different server name. So the nfs server ip also changed after deploying the new version.
Storage quota is enforced on all home directories under the configured path.
@sgibson91 I've added a few more changes here. Added a note to the top comment describing the changes. Could you take another quick look please? |
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/10939355537 |
Changes include:
/export/
). For the staging hub, we set it to/export/staging
.