'sparse submit' should use the user's existing ssh config file

[asasturkar]

This allows sparse to reuse any user configured ssh keys.

This requires the addition of a single line to the streamparse/ext/fabric.py file, to the activate_env function.

env.use_ssh_config = True

[msukmanowsky]

Rather than override this in streamparse's fabric, users can do this right now by modifying a streamparse project's fabfile.py:

from fabric.api import env
env.use_ssh_config = True
from streamparse.ext.fabric import *

Not sure we need to make this change as much as just document that it's available maybe.

[amontalenti]

@msukmanowsky Not sure I agree, I think it's probably more common for people to expect their SSH config to be used for this. I actually don't really understand why this setting isn't True in Fabric proper.

[hadisotudeh]

I've added "from fabric.api import env env.use_ssh_config = True" to the fabfile.py, but I get the following error when I ran the "sparse submit" command
Deploying "topology" topology...
bind: Cannot assign requested address
ssh tunnel to Nimbus 127.0.0.1:6627 established.
Routing Python logging to None.
Running lein command to submit topology to nimbus:
lein run -m streamparse.commands.submit_topology/-main topologies/topology.clj --option 'topology.workers=2' --option 'topology.acker.executors=2' --option 'topology.python.path="/home/hadi/Desktop/Storm//topology/bin/python2.7"'
{:option {topology.python.path /home/hadi/Desktop/Storm//topology/bin/python2.7, topology.acker.executors 2, topology.workers 2}, :debug false, :port 6627, :host localhost, :help false}
channel 1016: open failed: administratively prohibited: open failed
channel 1017: open failed: administratively prohibited: open failed
Caught exception: org.apache.thrift7.transport.TTransportException
What should I do?

[msukmanowsky]

@hadisotudeh see http://unix.stackexchange.com/questions/14160/ssh-tunneling-error-channel-1-open-failed-administratively-prohibited-open and in the future, for SSH errors, try Googling the error first (found this just by Googling "channel 1016: open failed: administratively prohibited: open failed").

[hadisotudeh]

yes, I've searched before, but the problem didn't solve and I thought maybe this problem is special for streamparse projects.

[dan-blanchard]

I agree with @amontalenti and made this happen by default now.