[
https://issues.apache.org/jira/browse/JCLOUDS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097760#comment-14097760
]
Ignasi Barrera commented on JCLOUDS-670:
----------------------------------------
I already had written the comment thinking about the description on the issue
talking about Nova but the PR is actually implemented in the portable layer, so
it LGTM.
The only concern I have is the "shorcut" thing, as it enables a different path
to configure the credentials just for a very particular use case. I'm just
worried about how complex using the TemplateOptions can become if this kind of
"shorcuts" start to appear.
How do you feel about this? Does the approach to call the "runScript" method
independentlt work for you?
> Option force no password when launching images on providers
> -----------------------------------------------------------
>
> Key: JCLOUDS-670
> URL: https://issues.apache.org/jira/browse/JCLOUDS-670
> Project: jclouds
> Issue Type: Improvement
> Reporter: Werner Buck
> Priority: Minor
>
> Images may return passwords from Nova. I have seen this happen with the
> official fedora openstack image as well as other times.
> When SSH is used to connect, the password from nova is used, which results in
> authentication errors while you might want to use the ssh-agent for
> authentication.
> To fix this I suggest the "forceNoPassword" option, to force the password to
> be empty even if we receive a password from the provider. This option is by
> default "false" and can be set in RunScriptOptions or TemplateOptions.
> Github: https://github.com/jclouds/jclouds/pull/486
--
This message was sent by Atlassian JIRA
(v6.2#6252)
