You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "David Alves (Created) (JIRA)" <ji...@apache.org> on 2012/03/26 16:52:27 UTC
[jira] [Created] (WHIRR-569) use a default set of keys for itests
(kept in /resources) so that we can login into instances when itests fail
use a default set of keys for itests (kept in /resources) so that we can login into instances when itests fail
--------------------------------------------------------------------------------------------------------------
Key: WHIRR-569
URL: https://issues.apache.org/jira/browse/WHIRR-569
Project: Whirr
Issue Type: Improvement
Components: core
Reporter: David Alves
Assignee: David Alves
Fix For: 0.8.0
as discussed right now when an itest fails we need to edit .properties rerun without temporary keys to be able to login into the boxes, which is less than ideal.
While we should't make the itests depend on a user's keys we could include a set of test keys in the source tree (e.g. /resources) that we use for the purpose of (i)testing.
--
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-569) create a default set of keys for
itests so that we can login into instances when itests fail
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-569:
----------------------------
Fix Version/s: (was: 0.8.0)
0.8.1
> create a default set of keys for itests so that we can login into instances when itests fail
> --------------------------------------------------------------------------------------------
>
> Key: WHIRR-569
> URL: https://issues.apache.org/jira/browse/WHIRR-569
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: David Alves
> Assignee: David Alves
> Fix For: 0.8.1
>
>
> as discussed in IRC right now when an itest fails we need to edit .properties rerun without temporary keys to be able to login into the boxes, which is less than ideal.
> As per Andrei's suggestion while we should't make the itests depend on a user's keys we could make Cluster.withTemporaryKeys() generate the keypair @ ~/.whirr if not present already (and reuse if present), thus keeping the process secure but allowing users to use the itest keys to log into instances.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WHIRR-569) use a default set of keys for itests
(kept in /resources) so that we can login into instances when itests fail
Posted by "David Alves (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Alves updated WHIRR-569:
------------------------------
Description:
as discussed in IRC right now when an itest fails we need to edit .properties rerun without temporary keys to be able to login into the boxes, which is less than ideal.
While we should't make the itests depend on a user's keys we could include a set of test keys in the source tree (e.g. /resources) that we use for the purpose of (i)testing.
was:
as discussed right now when an itest fails we need to edit .properties rerun without temporary keys to be able to login into the boxes, which is less than ideal.
While we should't make the itests depend on a user's keys we could include a set of test keys in the source tree (e.g. /resources) that we use for the purpose of (i)testing.
> use a default set of keys for itests (kept in /resources) so that we can login into instances when itests fail
> --------------------------------------------------------------------------------------------------------------
>
> Key: WHIRR-569
> URL: https://issues.apache.org/jira/browse/WHIRR-569
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: David Alves
> Assignee: David Alves
> Fix For: 0.8.0
>
>
> as discussed in IRC right now when an itest fails we need to edit .properties rerun without temporary keys to be able to login into the boxes, which is less than ideal.
> While we should't make the itests depend on a user's keys we could include a set of test keys in the source tree (e.g. /resources) that we use for the purpose of (i)testing.
--
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-569) create a default set of keys for
itests so that we can login into instances when itests fail
Posted by "Tom White (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246793#comment-13246793 ]
Tom White commented on WHIRR-569:
---------------------------------
When I run itests I use
{noformat}
mvn verify -Pintegration -DargLine="-Dwhirr.test.provider=aws-ec2 -Dwhirr.test.identity=$AWS_ACCESS_KEY_ID -Dwhirr.test.credential=$AWS_SECRET_ACCESS_KEY -Dconfig=.whirr-test.properties"
{noformat}
and put the following in .whirr-test.properties:
{noformat}
whirr.private-key-file=${sys:user.home}/.ssh/id_rsa
whirr.public-key-file=${sys:user.home}/.ssh/id_rsa.pub
{noformat}
That way I can log in to the machines if something fails. Andrei's suggestion sounds good too.
> create a default set of keys for itests so that we can login into instances when itests fail
> --------------------------------------------------------------------------------------------
>
> Key: WHIRR-569
> URL: https://issues.apache.org/jira/browse/WHIRR-569
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: David Alves
> Assignee: David Alves
> Fix For: 0.8.0
>
>
> as discussed in IRC right now when an itest fails we need to edit .properties rerun without temporary keys to be able to login into the boxes, which is less than ideal.
> As per Andrei's suggestion while we should't make the itests depend on a user's keys we could make Cluster.withTemporaryKeys() generate the keypair @ ~/.whirr if not present already (and reuse if present), thus keeping the process secure but allowing users to use the itest keys to log into instances.
--
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-569) create a default set of keys for
itests so that we can login into instances when itests fail
Posted by "David Alves (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Alves updated WHIRR-569:
------------------------------
Description:
as discussed in IRC right now when an itest fails we need to edit .properties rerun without temporary keys to be able to login into the boxes, which is less than ideal.
As per Andrei's suggestion while we should't make the itests depend on a user's keys we could make Cluster.withTemporaryKeys() generate the keypair @ ~/.whirr if not present already (and reuse if present), thus keeping the process secure but allowing users to use the itest keys to log into instances.
was:
as discussed in IRC right now when an itest fails we need to edit .properties rerun without temporary keys to be able to login into the boxes, which is less than ideal.
While we should't make the itests depend on a user's keys we could include a set of test keys in the source tree (e.g. /resources) that we use for the purpose of (i)testing.
Summary: create a default set of keys for itests so that we can login into instances when itests fail (was: use a default set of keys for itests (kept in /resources) so that we can login into instances when itests fail)
> create a default set of keys for itests so that we can login into instances when itests fail
> --------------------------------------------------------------------------------------------
>
> Key: WHIRR-569
> URL: https://issues.apache.org/jira/browse/WHIRR-569
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: David Alves
> Assignee: David Alves
> Fix For: 0.8.0
>
>
> as discussed in IRC right now when an itest fails we need to edit .properties rerun without temporary keys to be able to login into the boxes, which is less than ideal.
> As per Andrei's suggestion while we should't make the itests depend on a user's keys we could make Cluster.withTemporaryKeys() generate the keypair @ ~/.whirr if not present already (and reuse if present), thus keeping the process secure but allowing users to use the itest keys to log into instances.
--
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