You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Ellinger, David" <de...@ltionline.com> on 2013/04/25 21:04:23 UTC
Manually 'Stopping' an EC2 Instance from the EC2 Driver results in
Deltacloud 502 error
I have a Deltacloud server that is utilizing the EC2 driver.
As of right now, Deltacloud doesn't support 'Starting' a 'Stopped' EC2 instance and 'stopping' and 'Running' instance - It terminates it instead.
I have a java program that is interfacing with the Deltacloud API/Rest endpoint, and instead of going through Deltacloud to start/stop I am just using the EC2 Driver for start/stop functionality.
As if, I was able to successfully start a stopped instance this way.
My issue is when I use Amazons api to stop a running instance - the instance DOES get stopped but if I query '/api/instances' on the deltacloud server I receive a 502 Error.
The log shows
D, [2013-04-25T14:25:09.318195 #18889] DEBUG -- : New Aws::Ec2 using per_thread-connection mode
E, [2013-04-25T14:25:09.482855 #18889] ERROR -- 502: [Deltacloud::Exceptions::ProviderError] Backend Server Error
*removed IP* - - [25/Apr/2013 14:25:09] "GET /api/instances HTTP/1.1" 502 152644 0.4670
So is it possible to use the EC2 driver and deltacloud simultaneously? Is there any workaround to stopping a running instance?
Can deltacloud 'states' be redefined?
Just throwing some questions out there to come up with a solution to my problem.
Thanks!