[
https://issues.apache.org/jira/browse/JCLOUDS-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562516#comment-14562516
]
Stuart Hendren commented on JCLOUDS-913:
----------------------------------------
{quote}
The password in the LoginCredentials should be the SSH password used to connect
to the node. In other words, the returned password should be the one that can
be used to run scripts, and automated stuff on the node, and the VNC one does
not meet that goal.
In CloudSigma, however, the images don't allow a password login, because an
interactive prompt is shown on the first login to set the password. The only
images that allow an automated interaction are the cloud-init ones, which allow
to configure an SSH public key. jclouds configures that ssh key and the
username, and intentionally sets the password to null.
{quote}
[~nacx]
> CloudSigma2ComputeServiceAdapter does not put the password in the
> LoginCredentails
> ----------------------------------------------------------------------------------
>
> Key: JCLOUDS-913
> URL: https://issues.apache.org/jira/browse/JCLOUDS-913
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-labs
> Affects Versions: 1.9.0
> Reporter: Stuart Hendren
>
> A vnc password is supplied in the template, or the default is used when
> creating the server but this is not included in the login credentials
> returned.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
