Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 30 Apr 2015 13:42:06 +0000 (UTC)
From: "Wido den Hollander (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12665510.1377527418000.34785.1430401326772@Atlassian.JIRA>
In-Reply-To: <JIRA.12665510.1377527418000@Atlassian.JIRA>
References: <JIRA.12665510.1377527418000@Atlassian.JIRA>
 <JIRA.12665510.1377527418995@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-4505) expungeDestroyedVirtualMachine
 API call
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521503#comment-14521503 ] 

Wido den Hollander commented on CLOUDSTACK-4505:
------------------------------------------------

This is already closed, but I also see a Use Case if Users could do this. We could make this a setting so that per Domain/Account we can grant users the ability to Expunge their Instance?

> 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.3.4#6332)