cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei Zhou (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-4505) expungeDestroyedVirtualMachine API call
Date Thu, 24 Oct 2013 09:55:01 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Wei Zhou resolved CLOUDSTACK-4505.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Future)
                   4.3.0

> 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: 4.2.0
>            Reporter: David Matteson
>            Assignee: Wei Zhou
>             Fix For: 4.3.0
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message