-
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
[New Hub] Temple University Education Hub #1648
Comments
@yuvipanda and @GeorgianaElena were assigned to this issue and they are going to help deploy this hub. @laserchemist (and maybe @colliand?) if you can help answer any further questions the engineers might need (besides the info already shared at the top comment) that would be super helpful. Thanks!!! |
I will monitor the thread and be available to assist with other channels as well. |
Top comment missing info:Thanks everyone. I believe right now the missing info would be the answers to these two questions from @colliand in the top comment:
Example: See the AWI/CIRHO logo shown at the top of this hub landing page: https://ciroh.awi.2i2c.cloud/hub/login?next=%2Fhub%2F
Broader questions:
This would be deploying a hub on the shared 2i2c GCP cluster. But wonder if it wouldn't be smarter to create a new cluster on Azure under a 2i2c billing account and deploy the hub there until December. I'm not sure however how easy it would be to change the billing account starting with December? @yuvipanda, what do you think? Deploy a new hub super fast now, on the shared infra and move any user data to the new Azure cluster starting with December, or create a new cluster on Azure specifically for this? I believe knowing the expected number of users until December would help with the decision above. @colliand, or @laserchemist, do you have an approximation of this number? |
The number referenced in the call with @laserchemist was 300 to 500 users. More growth is expected in 2023. |
So it's 300 to 500 users right away, before December, and after that, that number is expected to grow? |
@GeorgianaElena given the start date is only a couple days away, my suggestion is to use the shared cluster and migrate later |
We are at ~300 users now. Class time peaks with 60 in section and >+15 others concurrent. Materials: |
@laserchemist As you're part of the InCommon federation, looks like no extra config is needed for auth! I've set up https://temple.2i2c.cloud now (PR in #1664). Can you try out authenticating with your university credentials and see if it works? If you can provide me with your username, I can mark you as admin there as well - and that should help you control the image being used! |
Very helpful, Authentication works, jmsmith1. Is Jupyterlab possible since the students are now used to this profile? |
Couple requests before students can use:
|
@laserchemist I'll mark you as admin today, which will allow you to set the docker image and select lab as default. For pulling, my recommendation is to make an nbgitpuller link - https://temple.2i2c.cloud/hub/user-redirect/git-pull?repo=https%3A%2F%2Fgithub.com%2FDataScienceTempleFirst%2FEDS&urlpath=lab%2Ftree%2FEDS%2F - and distribute that to students. In my experience, this is more robust than trying to pull in the background each time they login. You can generate arbitrary such links with http://nbgitpuller.link, or use the browser extensions linked to from there. What do you think? |
I see, I can redirect so it remains transparent to students, I was aware of this approach but always trying to make it straightforward/foolproof for students. I have noted some cases where the startup gets hung up when pulling from GitHub. In terms of setting the image this way, will it be apparent to me? |
@laserchemist you should be able change the environment + set up via the configurator: https://docs.2i2c.org/en/latest/admin/howto/configurator.html. Can you try it out? |
I see the configurator. I used what I thought was a standard way to refer to the image but the there was a spawning error. I am not sure the syntax to refer to a docker image on docker. I can work through repo2docker, etc. but I know this image does what I need. |
@laserchemist can you tell me what error you got? And where is the image built from? |
First: 2022-09-03T14:06:22Z [Normal] Pulling image "laserchemist/eds-jup:v4"
|
@laserchemist ah ok! If the repo making the image isn't on github somewhere, we won't really be able to help much with image problems unfortunately. I've merged the config changes, so the hub is fully live now. LMK if you run into any issues |
Hub Description
Jonathan Smith of Temple University requests an education hub. The use-case will be similar to Data8 at Berkeley. The expected user base consists of 300 to 500 1st year students. Jonathan has experience setting up this kind of infrastructure. In particular, he set up a z2jh hub for use during previous year(s). He'd like to have a similar resource up and running and managed by 2i2c so that he can focus on teaching, his students, and helping his colleagues use these tools.
Community Representative(s)
Important dates
Hub Authentication Type
CILogon (e.g., [email protected])
Hub logo information
Example: See the AWI/CIRHO logo shown at the top of this hub landing page: https://ciroh.awi.2i2c.cloud/hub/login?next=%2Fhub%2F
What image should be used for the Temple hub?
Hub user image
@laserchemist: Do you have a Docker image with the desired software environment? If not, 2i2c can proceed with a standard software environment for an education hub. We can improve on this during the Fall term.
Extra features you'd like to enable
2i2c Engineering should set this hub up now using the simplest path forward. Based on the early discussions with Jonathan Smith, we anticipate that this hub service will move over to a dedicated cluster on an Azure billing account owned by Temple University. The anticipated transition time is during December 2022 with the service on the new cluster ready for usage by students in January 2023.
Other relevant information
No response
Hub URL
temple.pilot.2i2c.cloud
Hub Type
basehub
Tasks to deploy the hub
The text was updated successfully, but these errors were encountered: