Hi,
We have here a couple of different issues:
* Delete images of VMs in FAILED state. The rationale behind this is
not to leave unneeded images in the worker-nodes that would eventually
fill the node disks or the $ONE_LOCATION/var directory. However this
is not always the desired behavior (e.g.
On Sep 7, 2010, at 1:35 PM, Shi Jin wrote:
> Right. I actually commented out the delete action since some failure
> shouldn't cause a deletion.
Yeah, I actually did the same. I'm hoping to see a "PERSISTENT_VM" lifecycle or
something that could be configured from the one conf file.
> I guess
Right. I actually commented out the delete action since some failure
shouldn't cause a deletion.
Here is the original issue: http://dev.opennebula.org/issues/265
I guess there is no way in 1.4 then.
I hope in 2.0 this is handled more gracefully.
Shi
On Tue, Sep 7, 2010 at 1:03 PM, Tres Wong-Godfr
On Sep 7, 2010, at 11:54 AM, Shi Jin wrote:
> In short, after rescuing a failed VM, how to bring it back to OpenNebula?
Hi Shi,
Not sure about OpenNebula 2.0, but in 1.4, the lifecycle manager actually
automatically deletes a VM immediately upon falling into a failed state; all
that remains o
Hi there,
I had a situation where a VM is in the FAILED state. I manually run the libvirt
command and now it is running. The problem is how to I let the OpenNebula
service know that it is running now? I tried to do "onevm restart" but it
complains it being in a wrong state.
In short, after res
