-
-
Notifications
You must be signed in to change notification settings - Fork 37
Rocky start with dask-ec2 - neither default ami, nor Ubuntu 14.04, 16.04, 17.04 work #99
Comments
Hi @sotte , sorry that you've had a poor experience here. Unfortunately the primary developer of this repository, @danielfrg, is mostly occupied with other things. He might stop by and fix things like this, but we probably can't depend on it. Are you able / interested in helping to resolve some of the issues that you've raised here? If so, that would be greatly appreciated. |
Hey @mrocklin, thanks for the quick reply. I'm not complaining about dask-ec2 :) It looks like a great project. I was just trying to summarize the problem I had when checking out the project hoping that it would help to fix some of the issues. Sadly I don't have the time to help out nor do I have any salt experience. |
I'm a big fan of Dask. Works seamlessly on my local machine. But when I try to use dask-ec2 in Australia (ap-southeast-2), I pretty much ran into the same issues as @sotte. I'd appreciate it, if you could please provide some help. Thanks! Some details:
|
Dask-ec2 looks like a gread project! Currently the initial user experience is pretty rocky unfortunately.
Neither the default ami, nor amis for Ubuntu 14.04, 16.04, and 17.04 allow me to setup a cluster.
I'll run you through the steps I tried.
I used the current version from master 1849efc for the experiments.
Default AMI
The default ami ami-d05e75b8 is for us-east-1 and does not work for Europe. Ok, no problem, I'll just use an appropriate ami for Europe (see further down).
Maybe dask-ec2 should suggest a resonable ami based on the region?
Ubuntu 14.04 for Europe
This runs for a while, creates 4 instances, gives me access to the dask status frontend and the jupyter notebook (via http), but the scheduler does not know about the workers.
Ubuntu 16.04
Doing the same with newer ami: ami-958128fa (Ubuntu 16.04, eu-central-1)
This leads to the ssl error #98
Ubuntu 17.04
Like 16.04, this leads to
The text was updated successfully, but these errors were encountered: