New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ipcluster local -n 4 fails #285
Comments
You are correct, the command should be the scripts were refactored (a long time ago now), and we still need to update the docs. This is already reported as Issue #7 |
Thanks, and sorry for the duplicate. I noticed after submitting the ticket that the whole documentation for ipcluster is out of date. I'd be very interested to learn how to use ipcluster with remote machines, especially over ssh. Is there somewhere else I can get that information from for now? |
Honestly, I don't know of a better place than the When you say "ipcluster" do you really mean the ipcluster script, or the whole machinery? Because ipcluster is just a convenience script that calls ipcontroller and ipengine a number of times. The ssh mode in
several times, which you can do just as easily with your own scripts if you want. You will need to distribute the furls if it is not on a shared filesystem, as described in the docs, that has not changed. The descriptions of ipcontroller/ipengine are still fairly up-to-date. |
Ok, thanks! I'll just use |
The following section in the documentation says to type the following command to start up a controller and engines:
However, this gives the error:
Should the command be:
The text was updated successfully, but these errors were encountered: