[jira] [Issue Comment Edited] (DTACLOUD-79) Launching multiple Instances with a AMI through images doesnot return all the Instance id's

["Ramesh A (Issue Comment Edited) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DTACLOUD-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185136#comment-13185136 ] 

Ramesh A edited comment on DTACLOUD-79 at 1/12/12 6:54 PM:
-----------------------------------------------------------

Applied the patch and tested it and following are the observed behavior
1. UI seems to work properly.  After launching the instance in ui, dcloud api seems to return all the instance ids properly
2. When trying to start the instances using curl, throws error as shown below.  However the instances seems to be started on the amazon ec2 console.

[rananda@rananda ~]$ curl -X POST -F "keyname=ramesh-new" -F "image_id=ami-31d41658" -F "instance_count=3" -F "realm_id=us-east-1a" -F "hwp_id=t1.micro" -F "firewalls1=default" --user "<userid>:<password>" "http://servername:port-number/api/instances?format=xml"
<error status='500' url='/api/instances?format=xml'>
  <kind>backend_error</kind>
  <backend driver='ec2'>
    <code>500</code>
  </backend>
  <message><![CDATA[ERROR: Missing template: instances/action_handler.xml.haml]]></message>
</error>
[rananda@rananda ~]$

This needs to be fixed for further verification.
                
      was (Author: rananda):
    Applied the patch and tested it and following are the observed behavior
1. UI seems to work properly.  After launching the instance in ui, dcloud api seems to return all the instance ids properly
2. When trying to start the instances using curl, throws error as shown below.  However the instances seems to be started on the amazon ec2 console.

[rananda@rananda ~]$ curl -X POST -F "keyname=ramesh-new" -F "image_id=ami-31d41658" -F "instance_count=3" -F "realm_id=us-east-1a" -F "hwp_id=t1.micro" -F "firewalls1=default" --user "<userid>:<password>" "http://<servername>:<port-number>/api/instances?format=xml"
<error status='500' url='/api/instances?format=xml'>
  <kind>backend_error</kind>
  <backend driver='ec2'>
    <code>500</code>
  </backend>
  <message><![CDATA[ERROR: Missing template: instances/action_handler.xml.haml]]></message>
</error>
[rananda@rananda ~]$

This needs to be fixed for further verification.
                  
> Launching multiple Instances with a AMI through images doesnot return all the Instance id's
> -------------------------------------------------------------------------------------------
>
>                 Key: DTACLOUD-79
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-79
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Client (Ruby)
>         Environment: Deltacloud API 0.4.0
> Amazon EC2
>            Reporter: Ramesh A
>            Assignee: Michal Fojtik
>         Attachments: 0001-EC2-A-full-list-of-created-instances-should-be-now-r.patch
>
>
> Launching multiple instances through images yields only one Instance id, in reality, should retrieve all the instance id's for this AMI
> Reproduction Steps:
> ===============
> 1. Choose an AMI in Images, and click on launch button.
> 2. In the "Launch new instance " page, specify "# of instances to be launched:" as more than 1(say 2 or 3) under  the "Additional parameter" section and provide the other necessary details and click on "Create Instance" button
> 3. in the next preceding page i.e, "Instance" page check for the instance id at the top right hand corner
> Expected Result:
> ============
> Should display multiple instance id's depending on the value provided for the "# of instances to be launched" field
> Actual Result:
> ===========
> Nevertheless of how many instances has been started, Application displays only one Instance id

--
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