You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "Tomaz Muraus (JIRA)" <ji...@apache.org> on 2010/10/27 17:44:22 UTC
[libcloud] [jira] Created: (LIBCLOUD-61) Allow user to specify custom username
and SSH port for deployment
Allow user to specify custom username and SSH port for deployment
-----------------------------------------------------------------
Key: LIBCLOUD-61
URL: https://issues.apache.org/jira/browse/LIBCLOUD-61
Project: Libcloud
Issue Type: Improvement
Reporter: Tomaz Muraus
Priority: Trivial
Attachments: ssh_username_and_port.patch
Currently, user can't specify custom username and SSH port which are used when deploying a node and this among other things makes deployment impossible for ElasticHosts driver, because they don't use a standard 'root' account.
This patch allows user to pass custom username (ssh_username) and port (ssh_port) to deploy_node method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[libcloud] [jira] Resolved: (LIBCLOUD-61) Allow user to specify custom
username and SSH port for deployment
Posted by "Jerry Chen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Chen resolved LIBCLOUD-61.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.4.1
Assignee: Jerry Chen
This was committed in r1052536.
Thanks for the patch!
> Allow user to specify custom username and SSH port for deployment
> -----------------------------------------------------------------
>
> Key: LIBCLOUD-61
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-61
> Project: Libcloud
> Issue Type: Improvement
> Reporter: Tomaz Muraus
> Assignee: Jerry Chen
> Priority: Trivial
> Fix For: 0.4.1
>
> Attachments: ssh_username_and_port.patch
>
>
> Currently, user can't specify custom username and SSH port which are used when deploying a node and this among other things makes deployment impossible for ElasticHosts driver, because they don't use a standard 'root' account.
> This patch allows user to pass custom username (ssh_username) and port (ssh_port) to deploy_node method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[libcloud] [jira] Commented: (LIBCLOUD-61) Allow user to specify custom
username and SSH port for deployment
Posted by "Tomaz Muraus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925747#action_12925747 ]
Tomaz Muraus commented on LIBCLOUD-61:
--------------------------------------
Yes, they add a special "toor" user which password is the same as the vnc_password you specify when creating a node.
The user is basically the same as root (it has the same user id, home folder, etc.).
The only difference is that it has a password set so you can login via SSH (root password is empty by default).
> Allow user to specify custom username and SSH port for deployment
> -----------------------------------------------------------------
>
> Key: LIBCLOUD-61
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-61
> Project: Libcloud
> Issue Type: Improvement
> Reporter: Tomaz Muraus
> Priority: Trivial
> Attachments: ssh_username_and_port.patch
>
>
> Currently, user can't specify custom username and SSH port which are used when deploying a node and this among other things makes deployment impossible for ElasticHosts driver, because they don't use a standard 'root' account.
> This patch allows user to pass custom username (ssh_username) and port (ssh_port) to deploy_node method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[libcloud] [jira] Commented: (LIBCLOUD-61) Allow user to specify custom
username and SSH port for deployment
Posted by "Jed Smith (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925632#action_12925632 ]
Jed Smith commented on LIBCLOUD-61:
-----------------------------------
Is the custom username just a relabeling of root, or do they disable root and make you add a user?
> Allow user to specify custom username and SSH port for deployment
> -----------------------------------------------------------------
>
> Key: LIBCLOUD-61
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-61
> Project: Libcloud
> Issue Type: Improvement
> Reporter: Tomaz Muraus
> Priority: Trivial
> Attachments: ssh_username_and_port.patch
>
>
> Currently, user can't specify custom username and SSH port which are used when deploying a node and this among other things makes deployment impossible for ElasticHosts driver, because they don't use a standard 'root' account.
> This patch allows user to pass custom username (ssh_username) and port (ssh_port) to deploy_node method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[libcloud] [jira] Updated: (LIBCLOUD-61) Allow user to specify custom username
and SSH port for deployment
Posted by "Tomaz Muraus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomaz Muraus updated LIBCLOUD-61:
---------------------------------
Attachment: ssh_username_and_port.patch
> Allow user to specify custom username and SSH port for deployment
> -----------------------------------------------------------------
>
> Key: LIBCLOUD-61
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-61
> Project: Libcloud
> Issue Type: Improvement
> Reporter: Tomaz Muraus
> Priority: Trivial
> Attachments: ssh_username_and_port.patch
>
>
> Currently, user can't specify custom username and SSH port which are used when deploying a node and this among other things makes deployment impossible for ElasticHosts driver, because they don't use a standard 'root' account.
> This patch allows user to pass custom username (ssh_username) and port (ssh_port) to deploy_node method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.