Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of kirk.jantzer@gmail.com
 designates 209.85.217.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <521B6481.2050802@a2hosting.com>
References: <521B59B5.4070108@a2hosting.com>
	<BBE32686-D518-4567-8E02-40D951D782B4@tgraham.us>
	<521B6481.2050802@a2hosting.com>
Date: Mon, 26 Aug 2013 10:24:02 -0400
Message-ID: 
 <CALuK5bFtgX+Tyt_C9KS6f2piiCjJuhRXpbu5v3Z9u5mOL8kvZw@mail.gmail.com>
Subject: Re: Remote force expunge?
From: Kirk Jantzer <kirk.jantzer@gmail.com>
To: Cloudstack users mailing list <users@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=001a11c344380c5f3f04e4da82b5

--001a11c344380c5f3f04e4da82b5
Content-Type: text/plain; charset=ISO-8859-1

I like that idea :-)


Regards,

Kirk Jantzer
http://about.met/kirkjantzer


On Mon, Aug 26, 2013 at 10:21 AM, David Matteson <dmatteson@a2hosting.com>wrote:

> Hi Travis,
>
> Wanting to provide a 10 minute (or longer) recovery time is exactly why
> I'm looking for some way to force an expunge remotely on demand.
>
> The problem with providing a long recovery time is that a user cannot
> deploy a new VM with the same hostname (or IP address) until the old one is
> expunged. Thus the desire to be able to say "No I really don't want to
> recover the old one, get rid of it so I can make a new one."
>
> It seems like an expungeDestroyedVirtualMachine API call might be in order?
>
>
> On 8/26/13 10:06 AM, Travis Graham wrote:
>
>> Hey David,
>>
>> As far as I understand it, there is no way to immediately expunge a
>> deleted VM easily. By design there's a minimum 10 minute window to allow
>> the recovery of a VM once it has been deleted.
>>
>> If you wanted to remove all references from the database and manually
>> remove the associated files on your primary and secondary storage, there's
>> nothing stopping you from doing that, but you'd probably be best to set
>> your expunge.delay and expunge.interval to 600 and let the system do the
>> heavy lifting.
>>
>> Travis
>>
>> On Aug 26, 2013, at 9:35 AM, David Matteson <dmatteson@a2hosting.com>
>> wrote:
>>
>>  Hey everybody,
>>>
>>> Quick question; there is no API call for it, but does anybody know of a
>>> way to force an expunge to run remotely? Ideally on a specific vmid.
>>>
>>> Thanks!
>>>
>>
>

--001a11c344380c5f3f04e4da82b5--