[
https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234256#comment-13234256
]
Andrei Savu commented on WHIRR-464:
-----------------------------------
Here are a few improvement ideas:
* rename createUserWithPublicAndPrivateKey to something like
ensureUserExistsWithPublicAndPrivateKey
* copy the public key to .ssh/id_rsa.pub
* implement lock sshd. See:
https://github.com/jclouds/jclouds/blob/master/scriptbuilder/src/main/java/org/jclouds/scriptbuilder/statements/ssh/SshStatements.java
ps: make sure you mark the attachment for inclusion on upload
> Do not fail if whirr.cluster-user already exists on the remote machine
> ----------------------------------------------------------------------
>
> Key: WHIRR-464
> URL: https://issues.apache.org/jira/browse/WHIRR-464
> Project: Whirr
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Fix For: 0.8.0
>
> Attachments: WHIRR-464.patch
>
>
> I think we should not fail if whirr.cluster-user already exists on the remote
> machine unless it's root. This becomes a critical issue when starting a new
> cluster from inside Amazon as ec2-user.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
