You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Andrei Savu (Created) (JIRA)" <ji...@apache.org> on 2012/01/03 23:38:39 UTC
[jira] [Created] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
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: Improvement
Reporter: Andrei Savu
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
[jira] [Commented] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231922#comment-13231922 ]
Andrei Savu commented on WHIRR-464:
-----------------------------------
Great. Let me know if you need help.
> 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
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Fix For: 0.8.0
>
>
> 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
[jira] [Commented] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Rodrigo Duarte Sousa (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231428#comment-13231428 ]
Rodrigo Duarte Sousa commented on WHIRR-464:
--------------------------------------------
I've tried to reproduce without success. Can you share a example recipe on how to reproduce it?
> 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
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Fix For: 0.8.0
>
>
> 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
[jira] [Assigned] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Andrei Savu (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu reassigned WHIRR-464:
---------------------------------
Assignee: Andrei Savu
> 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
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Fix For: 0.8.0
>
>
> 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
[jira] [Updated] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Andrei Savu (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-464:
------------------------------
Comment: was deleted
(was: 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
[jira] [Commented] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Rodrigo Duarte Sousa (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231498#comment-13231498 ]
Rodrigo Duarte Sousa commented on WHIRR-464:
--------------------------------------------
Nevermind, I've just reproduced it =)
> 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
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Fix For: 0.8.0
>
>
> 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
[jira] [Commented] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234380#comment-13234380 ]
Andrei Savu commented on WHIRR-464:
-----------------------------------
+1 I will go ahead and commit.
> 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, WHIRR-464_2.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
[jira] [Updated] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Rodrigo Duarte Sousa (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rodrigo Duarte Sousa updated WHIRR-464:
---------------------------------------
Attachment: WHIRR-464_2.patch
New patch with suggested modifications.
> 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, WHIRR-464_2.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
[jira] [Commented] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Rodrigo Duarte Sousa (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235740#comment-13235740 ]
Rodrigo Duarte Sousa commented on WHIRR-464:
--------------------------------------------
Done!
> 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: Rodrigo Duarte Sousa
> Fix For: 0.8.0, 0.7.2
>
> Attachments: WHIRR-464.patch, WHIRR-464_2.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
[jira] [Updated] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Andrei Savu (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-464:
------------------------------
Fix Version/s: (was: 0.8.0)
0.7.1
> 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
> Reporter: Andrei Savu
> Fix For: 0.7.1
>
>
> 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
[jira] [Updated] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Rodrigo Duarte Sousa (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rodrigo Duarte Sousa updated WHIRR-464:
---------------------------------------
Attachment: WHIRR-464.patch
> 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
[jira] [Commented] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234255#comment-13234255 ]
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
[jira] [Commented] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235658#comment-13235658 ]
Andrei Savu commented on WHIRR-464:
-----------------------------------
Rodrigo can you create a follow-up JIRA issue as a task under WHIRR-393 to disable password based authentication?
> 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: Rodrigo Duarte Sousa
> Fix For: 0.8.0, 0.7.2
>
> Attachments: WHIRR-464.patch, WHIRR-464_2.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
[jira] [Commented] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234221#comment-13234221 ]
Andrei Savu commented on WHIRR-464:
-----------------------------------
Looks great! I'm testing the change now on aws-ec2.
> 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
[jira] [Updated] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Andrei Savu (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-464:
------------------------------
Fix Version/s: 0.8.0
Issue Type: Bug (was: Improvement)
> 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
> Reporter: Andrei Savu
> Fix For: 0.8.0
>
>
> 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
[jira] [Commented] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202975#comment-13202975 ]
Andrei Savu commented on WHIRR-464:
-----------------------------------
Here we need to change the behaviour from create user to ensure user exists.
> 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
> Reporter: Andrei Savu
> Fix For: 0.8.0
>
>
> 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
[jira] [Commented] (WHIRR-464) Do not fail if whirr.cluster-user
already exists on the remote machine
Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
[ 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