Add support for port forwarding in SSHCluster #3895
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mrocklin
reviewed
Jun 15, 2020
|
This looks slick to me. It might be nice to have an example in the docstring (or a follow-on PR to docs.dask.org) |
|
Any thoughts on the TravisCI failures here? They appear to be related. |
|
Thanks for keeping this up to date @jacobtomlinson It looks like the Travis CI failures here are still live |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #3881
Added
forward_scheduler_portandforward_dashboard_portkwargs toSSHClusterto automatically handle port forwarding. This means you only need access to port22on the remote system and you'll still be able to connect to the cluster.Not set on the kwarg names, happy to take input on those.