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-conductor | Assignee: | Angus Thomas <athomas> |
Status: | CLOSED NEXTRELEASE | QA Contact: | wes hayutin <whayutin> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.0.0 | CC: | 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: | |
Embargoed: |
Description
Forrest Taylor
2012-03-02 17:49:11 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. Support for stateful instances, which can be stopped and restarted later (as opposed to immediately rebooted) is planned for future releases. |