[
https://issues.apache.org/jira/browse/DTACLOUD-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ronelle Landy closed DTACLOUD-474.
----------------------------------
Fixed in master ... deltacloud commit version:
b114f2e961bd2772ddb354a0291a1f27d1efa23d
> No listing of commands executed on Deltacloud server when using the ec2
> frontend
> ---------------------------------------------------------------------------------
>
> Key: DTACLOUD-474
> URL: https://issues.apache.org/jira/browse/DTACLOUD-474
> Project: DeltaCloud
> Issue Type: Bug
> Components: EC2/Frontend
> Environment: Deltacloud gem under test - 1.1.1
> ec2 Frontend
> Mock driver
> Reporter: Ronelle Landy
> Assignee: Michal Fojtik
>
> Start a Deltacloud server with both the ec2 and deltacloud frontends:
> >> deltacloudd -i mock -f ec2,deltacloud
> Starting Deltacloud API :: mock :: http://localhost:3001/api
> >> Thin web server (v1.5.0 codename Knife)
> >> Debugging ON
> >> Maximum connections set to 1024
> >> Listening on localhost:3001, CTRL+C to stop
> Now GET /api ... see the command listed in the server terminal ...
> Now GET /ec2/?Action=DescribeImages ... see no relevant command listed in the
> server terminal ...
> After the two command the server terminal has the following output:
> >> deltacloudd -i mock -f ec2,deltacloud
> Starting Deltacloud API :: mock :: http://localhost:3001/api
> >> Thin web server (v1.5.0 codename Knife)
> >> Debugging ON
> >> Maximum connections set to 1024
> >> Listening on localhost:3001, CTRL+C to stop
> 127.0.0.1 - - [14/Feb/2013 09:38:51] "GET /api?format=xml HTTP/1.1" 200 1460
> 0.0375
> Note only the command issued against the deltacloud api is listed in the
> server terminal above. There is no trace of the command issued against the
> ec2 frontend.
--
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
