Thank you @minrk 
Looking forward to meet you in Oslo
Best
Arnim
1 Like
I just learned of this and am interested in going (and have been waiting for it for a while)! I’ll have to talk tomorrow but possibly someone else on my team may come. Is it still possible for more to come and is there travel money still available?
I’ll update with what I’m interested in working on tomorrow.
1 Like
I think we do have one more spot available. I’m not sure about travel funding remaining, since I budgeted based on the earlier responses, but I’ll check.
I’m sure we can figure something out. The trains start at about 04:30 and take 30 minutes, if that’s early enough.
I’m definitely coming. Let me know if I am confirmed and what arrangements I should make myself.
The topics I am interested in (that I can think of now):
- batchspawner/kubespawner/wrapspawner maintnance and relationship (I will make issues about my topics beforehand)
- documentation
- promiting JH as an interface to existing resources, not a separate platform
- general JH hacking and development
1 Like
That sounds great! Definitely confirmed we have space for you, I just have to follow-up on funding, if that’s okay. Will do that via email.
1 Like
What’s the schedule? For now all I know is “Thursday to Sunday”. In particular, what are the earliest arrival times/latest departure times, and is there a difference in program each day or all hacking/social time that we’ll divide up depend on who is there and what we feel like? (Will it be empty the first/last days?)
I will arrive Friday around lunch time and be around till Sunday evening (my plane is Monday late afternoon). I think others I know of will arrive a bit earlier and stay till Sunday (afternoon).
I don’t think anyone has put together a formal agenda. Maybe we can spend some time on this issue working on one?? Would it be useful? Or maybe each morning do a brief “planning for the day” session? For me the most important part is “spend time with people I work with a lot online and haven’t ever/rarely seen in person”. This means it almost doesn’t matter what we spend time on related to the projects because it’ll all be interesting.
Of the three things I said I’d be interested in working on probably the third one is the one I’d start with because it benefits the most from in person communication and a shared white board. The other two are more technical in nature, more sit together with others and discover how to do this by trying to write some code.
I arrive Wednesday afternoon and leave Monday afternoon!
I’m currently very excited about @GeorgianaElena’s work on the Traefik proxy. The GitLab Helm chart comes with a Highly Available Redis deployment that I’d like to see if I can integrate with.
I read in the Jupyterhub Trafik Proxy docs here about the TKvProxy class that abstracts away the underlying mechanism on how the key value pairs are stored etc. I’m not very confident about the differences about using ETCD, Consul or other underlying KeyValue storage provides but eager to learn about Redis specifically because GitLab’s Helm chart comes with such deployment.
PS: I’m 0% confident about Redis vs ETCD etc but I like to not introduce additional containers running if possible.
1 Like
I’ll be there Thursday morning (8:10 at airport) to Sunday afternoon (16:10 from airport).
I’ll introduce myself: My background is as a computational researcher, and now I work for Aalto University (in Helsinki) in both the HPC group and Computer Science IT. For the last year, we’ve been doing more and more with Jupyter, and now we run two installations: one using batchspawner integrated to our HPC cluster for research, one using kubernetes on local hardware for teaching and general use. Through this time, I’ve ended up contributing to jupyterhub, batchspawner, nbgrader, and docker-stacks. Now we’ve got three other people working on Jupyter stuff for part of their time.
My vision is that Jupyter isn’t just another service, but a way to access services. I’ve gone through great efforts to make my JupyterHub deployments integrate to existing clusters, shell servers, data storage, and so on (easy with batchspawer, less obvious with kubernetes). My vision is that anywhere there’s an ssh server server or other ways of doing compute, Jupyter can exist in parallel and the old and new ways can support each other.
In the process I’ve worked on various add-on tools, such as envkernel, nbscript, and sjupyter. These generally fit the idea of “don’t redesign everything for Jupyter, but allow a seamless transition between Jupyter and existing systems”.
2 Likes
If we want it to run outside gitlab, we have to introduce a container for KV. I don’t really see any downsides to doing this, since it’s very small and a minor, hidden implementation detail where the lack of variability seems to outweigh the cost of one small container.
Just wanted to share my thoughts about agenda and topics: I agree with Tim that everything that will be worked on is going to be interesting :-). IMO the core devs should leverage the time to their best use, so the rest of this post is to be taken as less important as the “main BinderHub” developments.
From my side, I want to build two projects with BinderHub:
- To make a web application from a research project (the o2r reference implementation) and API we have developed “Binder-ready” so that I have a scalable solution without reimplementing 80% of stuff that BinderHub already does, cf. https://github.com/o2r-project/nbo2rproxy and Enabling root execution in repo2docker
- Create a Binder-based workflow to power CODE CHECK, which hopefully boils down to making several features work with a BinderHub: https://github.com/codecheckers/binderhub/labels/breakthrough (tl;dr: save the image of an execution to a tarball and push that tarball along with the repo contents to a data repository, run an image imported from a Binder instead of building one with r2d)
[ For all of this I need to install my BinderHub on OpenStack, and am not sure I’ll manage to do that before the meeting. ]
I’d love to discuss “my topics” in person for just short bits of time if possible, or selfishly work on them a few hours and get some jump-starting from the experts. I’m also open to take the time and contribute big or small features! Here’s some that I came up with and that could be fun and completable:
- I’d really like more DOIs to be supported, e.g. https://github.com/jupyterhub/binderhub/issues/216 or https://github.com/jupyterhub/binderhub/issues/938 or b2share (API docs)
- Plaudit for Binders: https://github.com/jupyterhub/binderhub/issues/898
- What’s the current state of pinning a specific r2d version for a specific binder? (can’t find the issue, but relevant for reproducibility)
2 Likes
I’ve added a hackmd for folks to start filling out the agenda and notes. I included logistics info for getting to the venue, times, etc.
I’m interested in a group dinner on Fri/Sat, and Saturday is also fine by me to practice my talk 
Thank you for organising, can’t wait to meet everyone! 
Hey @minrk just wondering where the venue is tomorrow? The hackmd isn’t super clear, is it in the hotel?
1 Like
Sorry it wasn’t clear! Yes, it’s in the hotel, in a room called “Michelsen.” There should be signs marked “Simula” in the morning to point the way. I added this to the hackmd, but I will make it more prominent.
See you tomorrow!
3 Likes
Thank you, see you tomorrow!
I asked this evening. It should be on the 7th floor.
4 Likes