Skip to content
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

incremental improvements to SSH launchers #1634

Merged
merged 2 commits into from Apr 23, 2012
Merged

Conversation

minrk
Copy link
Member

@minrk minrk commented Apr 19, 2012

  • add to_send/fetch steps for moving connection files around.
  • add SSHProxyEngineSetLauncher, for invoking to ipcluster engines on a remote host.
    This can be used to start a set of engines via PBS/SGE/MPI remotely.

This makes the SSHLauncher usable on machines without shared filesystems, and might.

When sending files, the destination directory must already exist - that is, ipython profile create may be necessary on the remote system, before the security dir exists for putting the connection file the first time.

I still think the SSHLaunchers are pretty crummy, but this addresses one of their shortcomings.

* add to_send/fetch steps for moving connection files around.
* add SSHProxyEngineSetLauncher, corresponding to `ipcluster engines` on a remote host.
  This can be used to start a set of engines via PBS/SGE/MPI *remotely*.
check = check_output(self.ssh_cmd + self.ssh_args + \
[self.location, 'test -e', remote, "&& echo 'yes' || echo 'no'"])
check = check.strip()
if check.strip() == 'no':
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to call strip() again here, since it was just done in the line above.

@fperez
Copy link
Member

fperez commented Apr 23, 2012

Looks good to me, other than minor comments. Thanks!

@minrk
Copy link
Member Author

minrk commented Apr 23, 2012

edits made. Thanks!

I won't do any Windows testing, and just go with:

SSH Launchers are not supported on Windows.

I won't assert, in case some advanced user has a weird setup that actually works, but it's not worth anyone else's time to support it.

@fperez
Copy link
Member

fperez commented Apr 23, 2012

Did you forget to push? I don't see the commit with the new edits.

Agreed on Windows support: when an enterprising Windows user shows up who can make this work, we'll be happy to take his/her PRs. Given how most of the time I wasted yesterday was dealing with the quirks of a Windows release, I have no problem with you punting on Win/SSH.

@minrk
Copy link
Member Author

minrk commented Apr 23, 2012

Did you forget to push? I don't see the commit with the new edits.

Oops, could be. I'll make sure it's pushed in the morning.

fix a few docstrings, names, and extra strips
@minrk
Copy link
Member Author

minrk commented Apr 23, 2012

yep, I pushed to trunk instead of my own branch. Should be up to date now.

@fperez
Copy link
Member

fperez commented Apr 23, 2012

Great, thanks. Merging in.

fperez added a commit that referenced this pull request Apr 23, 2012
Incremental improvements to SSH launchers:

* add to_send/fetch steps for moving connection files around.
* add SSHProxyEngineSetLauncher, for invoking to `ipcluster engines` on a remote host. This can be used to start a set of engines via PBS/SGE/MPI *remotely*.

This makes the SSHLauncher usable on machines without shared filesystems.

When sending files, the destination directory must *already exist* - that is, `ipython profile create` may be necessary on the remote system, before the security dir exists for putting the connection file the first time.
@fperez fperez merged commit 66e42d9 into ipython:master Apr 23, 2012
@minrk
Copy link
Member Author

minrk commented Apr 23, 2012

Oops, I just pushed one more commit with associated doc updates. Sorry, I'll do a tiny PR for that.

@minrk
Copy link
Member Author

minrk commented Apr 23, 2012

PR #1650 has just the doc commit

@fperez
Copy link
Member

fperez commented Apr 23, 2012

done, merged. thanks!

mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this pull request Nov 3, 2014
Incremental improvements to SSH launchers:

* add to_send/fetch steps for moving connection files around.
* add SSHProxyEngineSetLauncher, for invoking to `ipcluster engines` on a remote host. This can be used to start a set of engines via PBS/SGE/MPI *remotely*.

This makes the SSHLauncher usable on machines without shared filesystems.

When sending files, the destination directory must *already exist* - that is, `ipython profile create` may be necessary on the remote system, before the security dir exists for putting the connection file the first time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants