-
Notifications
You must be signed in to change notification settings - Fork 66
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
[New] Opensci cluster and hub #3733
[New] Opensci cluster and hub #3733
Conversation
Merging this PR will trigger the following deployment actions. Support and Staging deployments
Production deployments
|
Ok, so there's a hub running now at https://sciencecore.opensci.2i2c.cloud. It can build and push imageas the the registry, but cannot pull and I don't understand what's missing :/ The error I'm seeing in the hub is a 403:
And the error in the binderhub pod is a 401:
|
Ah, there's also this in the binderhub pod:
Which is similar to #2699 (comment) Update1: I believe this is the relevant bit ⬆️ Update2: It's clear that the docker client cannot find the k8s secret with the proper creds. But why? Update3: The k8s secrets with the registry creds get mounted and loaded correctly by the binderhub builder pods. Update4: Aha, so the issue is with the notebook pod not being able to pull from google artifact registry. This issue is only on AWS nodes 🤔 Update 5: I've managed to switch to the quay registry, but pulling still doesn;'t work, because by default, the images get pushed as private (even though our quay plan doesn't allow it 🙄 ) |
I managed to get a workaround on the situation above. @jmunroe, you should now be able to test and use the hub at https://sciencecore.opensci.2i2c.cloud So, this hub now builds and pushes images to our quay.io account under the prefix So, the notebook pods need credentials to be able to pull these images in order to start the server. A temporary fix to this is to put the robot's account's credentials under |
@GeorgianaElena nice work it seems like we can get an image built and that we then can launch it. I figure we shouldn't use the 2i2c organization on quay.io long term, but that was the workaround you referred to right? |
@consideRatio, yes! This and the fact that the images being pushed to quay default to being private images, so we need I couldn't find a way to signal to quay to default any new image to be a public image :( I believe there is a |
Thank you @GeorgianaElena and team! I'll try to give this new hub a try to today. If it works for me (I can log in, build an image from a repo, and launch that image I'll call that a win!) I'll be asking others within ScienceCore to try as well. |
People have been added to the hub and hopefully we'll get some 'real world' testing from other ScienceCore teams over the next few weeks. The only 'issue' encountered is the domain name: looks like sciencecore.opensci.2i2c.cloud is blocked through NASA firewall or security settings. Speculation is that *.2i2c.cloud may be the issue. I'll be working with the NASA folks to establish a preferred domain to use but we shouldn't be blocked waiting for a decision. I think this PR should be merged and say this sciencecore hub has been deployed! We can create new issues/support issues for future iterations. |
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 is incredible work, @GeorgianaElena. I've a couple suggestions, but otherwise this is good.
BinderHub: | ||
base_url: /services/binder | ||
use_registry: true | ||
image_prefix: quay.io/2i2c/opensci-sciencecore |
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.
Long term we should move to ECR, but in the meantime, I would suggest we create a different quay.io organization (perhaps 2i2c-opensci-sciencecore
) for now?
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.
I thought ECR is not yet supported by binderhub jupyterhub/binderhub#705. Ah, you mean, once its supported, we should use that instead of quay right?
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.
@GeorgianaElena ah, I had thought it is now supported given that we have a mybinder.org federation member running on AWS (thanks to Simon's work). I've pinged him in the ticket to ask.
Thanks for the feedback @yuvipanda. I believe I've addressed all the comments 🚀 |
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.
Thanks @GeorgianaElena! This looks good to me!
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.
Thank you @GeorgianaElena for working this and pulling in some cluster unspecific improvements!
Co-authored-by: Erik Sundell <[email protected]>
Co-authored-by: Erik Sundell <[email protected]>
Thank you @yuvipanda and @consideRatio! Merging 🚀 |
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/8154719390 |
Fixes #3667