clyne on master
Update pangeo-showcase.rst Add… Update pangeo-showcase.rst Merge pull request #843 from le… (compare)
rabernat on master
Update pangeo-showcase.rst (#84… (compare)
clyne on master
Update pangeo-showcase.rst add… Merge pull request #841 from le… (compare)
@jhamman At scipy you talked about how pangeo's binder can scale down to 0. Any idea how long it keeps things alive before shutting everything down? What about time to start up? What about timeout on individual inactive JLab sessions?
I was thinking if I load a repository X minutes before a tutorial then everyone should have speedy access to their JLab session. However, if I do it too early then we'll have to wait anyway.
Is anyone here using ocean.pangeo.io heavily right now? pangeo-data/pangeo-cloud-federation#360. Trying to figure out why it’s giving a 504.
It looks like there’s a bunch of dask worker pods running. Trying to figure out the hub isn’t handling new users though.
I have deployed pango in my local cluster (thanks for making it easy!). I do have question about the dask integration. I have a few volumes containing data that are mounted in the jupyter notebook server and defined in the cluster specific configuration jupyter_config.yaml (using extraVolumes and extraVolumeMounts). So far so good.
The problem is that when launching dask using KubeCluster from the notebook, these volumes are not available from the dask workers. Is there an 'automatic' way of doing this or do I need to define the volumes as well in the dask.yaml file? Or am I gettting this wrong (possibly!)?