Show More
@@ -403,13 +403,6 b" The controller's remote location and configuration can be specified:" | |||||
403 | # in the location specified by the `profile-dir` argument. |
|
403 | # in the location specified by the `profile-dir` argument. | |
404 | # c.SSHControllerLauncher.controller_args = ['--reuse', '--ip=*', '--profile-dir=/path/to/cd'] |
|
404 | # c.SSHControllerLauncher.controller_args = ['--reuse', '--ip=*', '--profile-dir=/path/to/cd'] | |
405 |
|
405 | |||
406 | .. note:: |
|
|||
407 |
|
||||
408 | SSH mode does not do any file movement, so you will need to distribute configuration |
|
|||
409 | files manually. To aid in this, the `reuse_files` flag defaults to True for ssh-launched |
|
|||
410 | Controllers, so you will only need to do this once, unless you override this flag back |
|
|||
411 | to False. |
|
|||
412 |
|
||||
413 | Engines are specified in a dictionary, by hostname and the number of engines to be run |
|
406 | Engines are specified in a dictionary, by hostname and the number of engines to be run | |
414 | on that host. |
|
407 | on that host. | |
415 |
|
408 | |||
@@ -434,11 +427,27 b' a single location:' | |||||
434 |
|
427 | |||
435 | Current limitations of the SSH mode of :command:`ipcluster` are: |
|
428 | Current limitations of the SSH mode of :command:`ipcluster` are: | |
436 |
|
429 | |||
437 | * Untested on Windows. Would require a working :command:`ssh` on Windows. |
|
430 | * Untested and unsupported on Windows. Would require a working :command:`ssh` on Windows. | |
438 | Also, we are using shell scripts to setup and execute commands on remote |
|
431 | Also, we are using shell scripts to setup and execute commands on remote hosts. | |
439 | hosts. |
|
432 | ||
440 | * No file movement - This is a regression from 0.10, which moved connection files |
|
433 | ||
441 | around with scp. This will be improved, Pull Requests are welcome. |
|
434 | Moving files with SSH | |
|
435 | ********************* | |||
|
436 | ||||
|
437 | SSH launchers will try to move connection files, controlled by the ``to_send`` and | |||
|
438 | ``to_fetch`` configurables. If your machines are on a shared filesystem, this step is | |||
|
439 | unnecessary, and can be skipped by setting these to empty lists: | |||
|
440 | ||||
|
441 | .. sourcecode:: python | |||
|
442 | ||||
|
443 | c.SSHLauncher.to_send = [] | |||
|
444 | c.SSHLauncher.to_fetch = [] | |||
|
445 | ||||
|
446 | If our default guesses about paths don't work for you, or other files | |||
|
447 | should be moved, you can manually specify these lists as tuples of (local_path, | |||
|
448 | remote_path) for to_send, and (remote_path, local_path) for to_fetch. If you do | |||
|
449 | specify these lists explicitly, IPython *will not* automatically send connection files, | |||
|
450 | so you must include this yourself if they should still be sent/retrieved. | |||
442 |
|
451 | |||
443 |
|
452 | |||
444 | IPython on EC2 with StarCluster |
|
453 | IPython on EC2 with StarCluster |
General Comments 0
You need to be logged in to leave comments.
Login now