@Jess Hamrick, The link which you have mentioned is no longer exists. can 
you please update it

On Thursday, July 23, 2015 at 4:46:55 AM UTC+5:30, Jess Hamrick wrote:
>
> Hi Michael,
>
> In your spawner, are you setting the IP of the spawned servers after they 
> are spawned? That might be causing you problems because if you don’t set 
> the IP, the hub won’t know how to talk to the user servers. You might have 
> a look at my SwarmSpawner for an example, which spawns servers on a cluster 
> of nodes using Docker swarm:
>
>
> https://github.com/compmodels/jupyterhub-deploy/blob/master/roles/jupyterhub/files/swarmspawner.py#L52
>
> The user servers also need access to the hub, which requires setting the 
> hub_ip. For example, here’s the corresponding jupyterhub_config.py that I’m 
> using:
>
>
> https://github.com/compmodels/jupyterhub-deploy/blob/master/roles/jupyterhub/templates/jupyterhub_config.py#L27
>
> I don’t think you should need to install anything on the nodes except the 
> jupyterhub-singleuser script (as well as IPython itself).
>
> Cheers,
> Jess
>
>
> On Jul 22, 2015, at 4:08 PM, Michael Gilbert <mk...@nau.edu <javascript:>> 
> wrote:
>
> Hi,
>
> I'm trying to create a custom spawner for Jupyterhub (installed on a 
> cluster) that creates spawners on different nodes as opposed to the head 
> node. I've been using the DockerSpawner 
> <https://github.com/jupyter/dockerspawner> example as a reference and am 
> having some trouble figuring out how to get this configured properly.
>
> Without my custom spawner, Jupyterhub is working great, and I can create 
> and run notebooks just fine. When I load my spawner and try to login to 
> Jupyterhub, I can see in the logs that the spawner is in fact running 
> instances of jupyterhub-singleuser on a different node. The problem is that 
> the compute node doesn't seem to communicate any information back to the 
> head node. Here's the command my spawner is submiting to the compute node 
> in the start() method:
>
> export JPY_API_TOKEN="ef98aec6e6bb47ab9181b325feb5c6e3; 
> jupyterhub-singleuser --user=mkg52 --port=33911 
> --cookie-name=jupyter-hub-token-mkg52 --base-url=/user/mkg52 
> --hub-prefix=/hub/ --hub-api-url=http://172.16.2.1:54321/hub/api 
> --ip=127.0.0.1
>
> Once this is submitted, I'm seeing in the logs a couple of 302 GET 
> responses, a 200, then a constant string of 304s. So it's obviously not 
> communicating to the node. This brings me to my main question:
>
> Would someone be able to explain how I need to setup the compute nodes 
> and/or configuration file in order to talk back to the head node via 
> jupyterhub-singleuser? I have jupyterhub installed on the compute nodes, 
> but do I also need all the node.js dependencies and configuration files and 
> whatnot? How do the ports need to be configured? I'm just a little lost at 
> this point, so any help would be greatly appreciated!
>
> Thank you!
>
> Mike
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jupyter+u...@googlegroups.com <javascript:>.
> To post to this group, send email to jup...@googlegroups.com <javascript:>
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jupyter/9d6e51ad-30a1-4dcb-b631-931facf5deec%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jupyter/9d6e51ad-30a1-4dcb-b631-931facf5deec%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/a2631f13-bd4b-44ca-81b6-0cb6a8d499de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to