-
Notifications
You must be signed in to change notification settings - Fork 65
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
Tweaking NFS settings and enabling for UToronto and CarbonPlan on Azure #887
Tweaking NFS settings and enabling for UToronto and CarbonPlan on Azure #887
Conversation
NFS is only availabe on Storage Accounts with kind=FileStorage and tier=Premium
Output of terraform plan
I'm going to go ahead and apply this straight away so that I can deploy a hub and test if the NFS protocol resolves #871 |
Support chart successfully deployed |
I'm now trying to deploy a staging hub and figuring out the mount args. I'm pretty sure in the first attempt, I did not get the value of
I don't think the colon between The second attempt also failed.
|
Deployed grafana dashboards in the interim. @yuvipanda will brainstorm the above tomorrow. These warnings in the console feel very relevant. |
9694275
to
c48d8da
Compare
I've pushed two new commits here, and am trying it out on the UToronto cluster. The cluster can mount the NFS setup now! \o/. It's still owned as 'root' though, so need to figure out how to make that instead be uid 1000. |
Co-authored-by: GeorgianaElena <georgiana.dolocan@gmail.com>
This was a replacement for nfs-share-creator for Azure File when we were using it with SMB / CIFS. However, we are now using NFS directly, and this was just causing problems where the actual notebook container was mounting a different path than the volume-mount initcontainer that was setting uid!
for more information, see https://pre-commit.ci
Hmmm, whatever network connection we made in terraform may block us from continuing to manage the infrastructure with terraform once applied 😕 I applied the latest changes, and then did another plan expecting a "Your infrastructure is up-to-date" message, and instead got:
|
I have deployed the staging hub to the cluster and can confirm that chmod does appropriate things now! My only concern is the terraform issue #887 (comment) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me @sgibson91!
We should however investigate that 403 when terraform apply
😕 But I have no idea if that should block merging this PR. We already deployed the changes here...
I have opened #890 to track this since the damage is already done to these clusters |
I have deployed the prod hub and grafana dashboards again. Merging this! |
Summary
This PR is doing a few things.
In terraform:
For CarbonPlan on Azure:
carbonplan-azure
. I have gone withazure.carbonplan.*
instead, to match URLs.For UToronto:
Note
After applying the terraform fix @yuvipanda applied in sgibson91#94, I'm worried that while we have granted the k8s cluster access to the NFS server, we may have also blocked our terraform output as I could not run a successful
terraform plan
after making this upgrade. See #887 (comment)