[
https://issues.apache.org/jira/browse/LIBCLOUD-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801044#comment-13801044
]
ASF subversion and git services commented on LIBCLOUD-414:
----------------------------------------------------------
Commit df6dc6119003c7d6ebe3bf3a237ad4d9d56982d1 in branch refs/heads/trunk from
[~kami]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=df6dc61 ]
Add log statements to our ParamikoSSHClient wrapper. This should make
debugging deployment issues easier.
Part of LIBCLOUD-414.
> Add log statements to our SSH client wrapper
> --------------------------------------------
>
> Key: LIBCLOUD-414
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-414
> Project: Libcloud
> Issue Type: Improvement
> Components: Core
> Reporter: Tomaz Muraus
> Assignee: Tomaz Muraus
> Priority: Critical
> Labels: paramiko, ssh
>
> Currently we enable paramiko's debug log when user uses LIBCLOUD_DEBUG, but
> we don't do any additional logging in our paramiko SSH client wrapper.
> Paramiko itself doesn't log when it executes a command which makes debugging
> harder.
> We should log the following things in our wrapper:
> - Log every command which is executed (command, arguments)
> - Log stdout and stderr of every executed command
> - Log file uploads and deletes
--
This message was sent by Atlassian JIRA
(v6.1#6144)
