dask-jobqueue binder
Open
documentation
sprint
- Dominant language
- Python
- Stars
- 256
- Forks
- 150
- PR merge metrics
- No merged PRs in 30d
Description
The idea is to have a binder setup with a toy cluster so that people can play with dask-jobqueue a bit without having to set it up on their cluster.
Our SLURM CI setup uses a single Dockerfile, maybe this image could be used to have a binder.
Binder allows you to use a Dockerfile:
https://github.com/binder-examples/minimal-dockerfile
Questions:
- how does this idea work in practice. Is 1-2GB RAM enough for a toy cluster ?
- if I use binder.pangeo.io does it work better (there seems to be more RAM on pangeo.io?)
If this idea works, we could think about what kind of notebooks to create (related to #253).
Contributor guide
Assessment
This issue has not been assessed yet.