> 1. I feel http-mode belongs to a separate repo as the use case is very > different from kernel-gateway. >
We discussed splitting the modes out long ago and decided that there's wasn't really a benefit to maintain another repo with its own packaging and release cycle at the time. If having two packages in the repo is causing problems, then we should reconsider it. > 2. kg-http-mode should really support a mode where you can specify the > seed_uri via an API - while the service is running. This way you could do a > requests.get to a cell of a notebook running in Jupyter notebook server - > for each of running kernels, not just one. > This sounds like a good PR. There's some complications to solve with the kernel pool concept where N kernels are running to service requests for a single notebook simultaneously. I don't think there's any blockers, just work that has to be done to maintain a kernel pool per notebook. > 3. nb2kg is even more powerful extension that allows offloading > computational power to a dedicated box. It is the key component that > ensures the notebooks and the dashboards server reference exactly the same > environment. An example in > https://github.com/jupyter-incubator/dashboards_setup/blob/master/docker_deploy/Dockerfile.notebook > > is suboptimal as it installs required dependencies twice - once for the > kernels container, and second time for the Jupyter notebook server. What if > your environment a bit more complex and makes use of environment variables > too? I think a better use case of making the notebook server and the > gateway referencing the same kernel environment is presented here: > https://github.com/rs2/pyconuk-2016-jupyter-workshop/blob/master/docker/Dockerfile.notebook > > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Frs2%2Fpyconuk-2016-jupyter-workshop%2Fblob%2Fmaster%2Fdocker%2FDockerfile.notebook&sa=D&sntz=1&usg=AFQjCNHbdDHjh_-SpNYsBjBXM055ee-cIA> > > nb2kg really needs to be available on pypi/conda-forge. Happy to give a > hand, I think it's a really powerful project. > @jtyberg wrote the nb2kg as a proof-of-concept. It's definitely a cool little extension. I don't have cycles to spend on it, but if you want to submit PRs I'm sure someone can review and merge them. If you think it really deserves to be its own repo and package, maybe we can move it to jupyter-incubator or make it a top-level Jupyter project if there's enough consensus for people to maintain it? Cheers, Pete -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/900742d8-cbed-4ea2-b4a2-e17692200cde%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
