Bug 711294
| Summary: | RFE : Remove failed option on instances should remove the erroneous instances not just stop them. | ||
|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Shveta <ssachdev> |
| Component: | aeolus-conductor | Assignee: | Tomas Sedovic <tsedovic> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 0.3.1 | CC: | akarol, dajohnso, deltacloud-maint, dgao, matt.wagner, ssachdev, tsedovic |
| Target Milestone: | beta | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-08 13:47:43 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
Shveta
2011-06-07 06:24:33 UTC
any idea what the plan is for this.. So the latest on this is that we won't allow deleting instances directly at all. We'll UI for deleting deployables. And for the time being, we'll only allow to delete whose instances are either in create_failed or stopped state. k.. so just repeating to make sure I understand.. A user *can* delete a deployable A user *can* delete a instance in *failed* or *stopped* state Also just making sure... In a deployable w/ more than one instance... say three instances.. One instance gets "create_failed" or is stopped for other reasons, but the other two instances in the deployable are running. Can a user delete the one bad instance in a deployable w/ three total? I assume you mean "deployment" not "deployable" -- deployable is the XML definition of a deployment. Deployment is the thing running in the cloud that consists of one or more instances. User *cannot* delete instances individually. Only deployments can be deleted. Deleting a deployment removes all instances that belong to it, too. If any of the deployment's instances are running, the user cannot delete the deployment. However, they can stop all the instances (or stop the deployment itself -- that stops all of its instances, too) and then delete the deployment. I've just sent a patch implementing this to the mailing list: https://fedorahosted.org/pipermail/aeolus-devel/2011-June/002783.html Pushed into next: db176192f8e02a4ba345e78de947abfff1b5021a verified: Individual instances cannot be deleted. Only deployments can be deleted. conditions: Deployment is not deleted if instances are running. if instances are failed or stopped then it can be deleted. Also when deployment is stopped itself which intern stops all instances, then it can be deleted. [root@dell-pe860-01 ~]# rpm -qa | grep aeolus aeolus-configure-2.0.1-0.el6.20110706084705git542b456.noarch aeolus-conductor-0.3.0-0.el6.20110706142422git0ebf7d1.noarch aeolus-conductor-doc-0.3.0-0.el6.20110706142422git0ebf7d1.noarch aeolus-conductor-daemons-0.3.0-0.el6.20110706142422git0ebf7d1.noarch rubygem-aeolus-cli-0.0.1-1.el6.20110706142422git0ebf7d1.noarch aeolus-all-0.3.0-0.el6.20110706142422git0ebf7d1.noarch removing verified bugs from tracker release pending... release pending... perm close |