Shane

@consideRatio I'm fine with a block storage path-- something like /dev/nvmep1, or whatever the block device displays 'natively' and needs the least amount of configuration. Using /tmp may not be...

@consideRatio @fperez pinging this issue after our ray discussion last week-- this is related to #92 which has the error message for the block storage. While block storage isn't technically...

...apparently another option for this that doesn't involve setting up block storage is spinning up a separate redis instance and connecting to it-- https://www.anyscale.com/blog/redis-in-ray-past-and-future

Possibly relevant-- appears to have support in aws for respecting the shm flag vis-a-vi docker containers: https://aws.amazon.com/about-aws/whats-new/2018/03/amazon-ecs-adds-support-for-shm-size-and-tmpfs-parameters/ They say use at least 30% of ram; so for our massive high...

One more link for this-- on the kubernetes side, seems like this is possible but not well documented atm: https://github.com/cri-o/cri-o/pull/4174

Ray has always worked locally on the jupyter-hub instance, but if we're looking into it as a tractable replacement for dask, it would be helpful to try it as a...

...perhaps this is something that one of the ray core devs can answer for us? @robertnishihara @ericl @richardliaw the context here is that we're looking into replacing dask with ray...

@consideRatio I'm less worried about the shared directory, because it's generally considered 'read only'... and by that, I mean that the objects that are there are write once and not...

On that point, it probably doesn't need the multi-user setup... the only thing that the daemon is doing is spawning build processes per user, but if each user is in...

@consideRatio We shouldn't need sudo at all once nix is installed. I think the sudo call during installation is mostly to set the correct permissions on the /nix directory, and...