[
https://issues.apache.org/jira/browse/WHIRR-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975275#action_12975275
]
Lars George commented on WHIRR-158:
-----------------------------------
Looking at AuthorizeRSAPublicKey and InstallRSAPrivateKey which are the classes
being used internally, they use the node.getCredentials() call, which we could
maybe override with the current username. But this must be an additional
TemplateOption with a list of all nodes (cloned) plus the changed credential,
which by default is set from the metadata of the provider. My knowledge of
JClouds is still too limited to understand if this could be simply added at the
TemplateBuilder level (BootstrapClusterAction.buildTemplate()). Since this is
called per node we may simply be able to add it there as an additional step?
> Allow users to log into clusters as themselves
> ----------------------------------------------
>
> Key: WHIRR-158
> URL: https://issues.apache.org/jira/browse/WHIRR-158
> Project: Whirr
> Issue Type: New Feature
> Components: core
> Reporter: Tom White
>
> Currently you have to log on to cloud instances with a particular user name
> (e.g. ec2-user on Amazon Linux, root on Ubuntu on rackspace). It would be
> nice if you could use the same user as the one that launched the cluster.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
