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 <dmatte...@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!
