Bug 799481

Summary: Using the Deployment screen to Stop an instance in EC2 will Terminate that instance
Product: [Retired] CloudForms Cloud Engine Reporter: Forrest Taylor <ftaylor>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED NEXTRELEASE QA Contact: wes hayutin <whayutin>
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, ssachdev
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-08 11:31:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Forrest Taylor 2012-03-02 17:49:11 UTC 
Once you have launched an instance, you can monitor the instance by going to Monitor->Deployable_name.  The Instances tab shows the status of the instance, including the IP address and state.  When the instance is in the EC2 cloud, the Stop button will Terminate the instance.  This will leave the machine in an unrecoverable state.

The Stop button should stop the instance so it could be started at a later date.  At the very least we need a warning about what this button does.
Comment 1 Forrest Taylor 2012-03-03 21:12:09 UTC 
There is also no way to start them once they are shutdown.  If you poweroff a machine and start it again, it may get a different IP address (as with EC2).  Once it gets a different IP address, there is no way to manage it in CloudForms.  Perhaps this is desired behavior?  Reboot or terminate a machine, otherwise, create a new application.
Comment 2 Angus Thomas 2012-03-08 11:31:05 UTC 
Support for stateful instances, which can be stopped and restarted later (as opposed to immediately rebooted) is planned for future releases.