[
https://issues.apache.org/jira/browse/WHIRR-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096791#comment-13096791
]
David Alves commented on WHIRR-379:
-----------------------------------
I'm having problems logging into instances created by whirr.
doing an euca-describe-instances on the local cloud gives:
{code}
RESERVATION r-rhjoa2jk admin default
INSTANCE i-00000002 ami-59aa5f14 10.0.86.4 10.0.86.4
running test (admin, nova) 0 m1.tiny 2011-09-04T01:55:51Z
nova
RESERVATION r-say9iqm0 admin default
INSTANCE i-00000001 ami-59aa5f14 10.0.86.3 10.0.86.3
running None (admin, nova) 0 m1.tiny 2011-09-04T01:19:21Z
nova
{code}
where the *.86.3 instance was created by whirr and the *.86.4 was created
manually (euca-run-instances) notice the lack of keypair in the instance
launched by whirr.
Is this supposed to happen?
I had provided a keypair and pointed ClusterSpec to it (in order not to use
temporary keys and be able to log into instances).
Am I doing something wrong?
> Provide a local cloud for testing
> ---------------------------------
>
> Key: WHIRR-379
> URL: https://issues.apache.org/jira/browse/WHIRR-379
> Project: Whirr
> Issue Type: New Feature
> Reporter: David Alves
> Attachments: WHIRR-379, WHIRR-379.patch, WHIRR-379.patch, solo.txt
>
>
> As discussed on the list the idea is to create a local cloud using vagrant
> and openstack and allow whirr tests to run against it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
