adding diagram for jupyterhub #481
Conversation
|
Hey @choldgraf, I added comments + made some minor changes in the google slides you linked to. Thank you very much for making these! |
|
I considered some changes, it's really tough to make a clean concise diagram though. The original document is available in the Feb 13 at 4:22 pm revision by Chris. |
|
I incorporated a bunch of @consideRatio 's changes and cleaned things up a bit more in general...LMK what people think. |
choldgraf
force-pushed
the
diagram
branch
2 times, most recently
from
48a2f0a to
ac6ea06
Compare
|
one question: on the jupyterhub side, what serves the actual user interface? is it |
|
Guessing it works like the proxy will ask he hub if the user is logged in
based on cookies, then redirect based on that without serving any HTML
content. Don't really know though.
UPDATE: Additional thinking, the hub will serve, through the proxy, until the user is logged in, then the singleuser server will serve content through the proxy? In other words, the proxy will always serve, but the content server is initially the hubs, then the singleuser server. Hmm?
|
|
yep - I think that's it...basically if the cookie says the person has a jupyter server for them it'll just redirect you to the pod...if the server isn't present or cookie not there, it redirects you to the hub which handles authentication etc and then the way I think Binder works is that it directs you to a Hub that's using a dummy authenticator that automatically creates a temporary user and immediately redirects to your pod when it's ready. |
|
@choldgraf is all HTML etc always server through the proxy? Will the binder use the jupyterhub's proxy or have one additional layer of proxy on top perhaps? Im thinking that the user will keep speaking with the same IP all the time, for the JH and the BH, is that correct? |
|
@consideRatio I think it's a different IP since if you notice, on binder you're redirected to https://hub.mybinder.org which handles subsequent directing to user pods |
|
FYI this one is ready to go from my end. I think the diagram could use improvements but is a helpful addition. I'm happy to spot-check things moving forward... |
|
Looks great! |
|
@choldgraf Sorry this one slipped off my radar. Merging. |
This adds a diagram for a high-level view of JupyterHub. I think there are probably many improvements to be made, but I feel like it's better to have something we can iterate on. Would love to hear what people think!
The google slide used to create the image can be found here: https://docs.google.com/presentation/d/1t5W4Rnez6xBRz4YxCxWYAx8t4KRfUosbCjS4Z1or7rM/edit#slide=id.p
edits or comments are welcome!
closes #10