You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Wei Zhou (JIRA)" <ji...@apache.org> on 2013/09/20 11:21:53 UTC
[jira] [Assigned] (CLOUDSTACK-4505) expungeDestroyedVirtualMachine
API call
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wei Zhou reassigned CLOUDSTACK-4505:
------------------------------------
Assignee: Wei Zhou
> expungeDestroyedVirtualMachine API call
> ---------------------------------------
>
> Key: CLOUDSTACK-4505
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4505
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: API
> Affects Versions: Future
> Reporter: David Matteson
> Assignee: Wei Zhou
>
> We want to provide users a long recovery time before expunging their VMs automatically. Recovery is a great feature. But the problem is that users cannot deploy a new VM with the same hostname or IP address as a Destroyed VM which has not yet been expunged.
> So it would be great to have an API call that lets users say "No I really don't want to recover that VM, please delete it so I can deploy a new one."
> expungeDestroyedVirtualMachine would be called with a single vmid to specify which Destroyed VM should be cleared, and of course it would only work on a VM which is in Destroyed state already.
--
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