Hi Simon,
On Tue, Oct 29, 2013 at 6:04 PM, Simon Boulet si...@nostalgeek.com wrote:
Rubén could not retrieve that 'paused' state from libvirt, no matter how
the
vm was destroyed, he always got 'stopped'. Are we missing something?
It depends of the Libvirt backend you're using and how it
On Tue, Oct 29, 2013 at 7:04 PM, Simon Boulet si...@nostalgeek.com wrote:
Oh, yes, I get your point. The Core uses disappear for setting the
VM as UNKNOWN. I think we need to keep disappear as it is, or at
least keep the current UNKNOWN behaviour. If the VM can't be monitored
for some reason
Hi Carlos
We could have a global default in oned.conf, and then allow to change the
behaviour with an attribute in the
VM template. This wouldn't require any extra hooks, and it would work with
any hypervisor.
I think thats the ideal solution! The libvirt paused method I
suggested is a
Hi,
On Tue, Oct 29, 2013 at 4:43 PM, Simon Boulet si...@nostalgeek.com wrote:
The libvirt paused method I
suggested is a hack that works with OpenNebula and turns the VM that
are internally shutdown to SUSPENDED in OpenNebula.
Rubén could not retrieve that 'paused' state from libvirt, no
On Tue, Oct 29, 2013 at 12:26 PM, Carlos Martín Sánchez
cmar...@opennebula.org wrote:
Hi,
On Tue, Oct 29, 2013 at 4:43 PM, Simon Boulet si...@nostalgeek.com wrote:
The libvirt paused method I
suggested is a hack that works with OpenNebula and turns the VM that
are internally shutdown to
Hi Simon + Nistor,
We've done some tests in the stock drivers when the VM is shutdown (from
inside) the VM disappears from the list, show we cannot get the state (not
even with --all). How do you get the paused state?
On the other hand, the libvirt hook seems a good approach, since we could
Hi Ruben,
Do we really care if the VM was shut down from the inside or not? I was
thinking of a hook script like the following:
#!/bin/bash
VMID=$(echo $1 | cut -d- -f2)
if [ $2 == stopped ]; then
onevm shutdown $VMID
fi
It's obviously just a big fat (untested) hack, which will probably
Hi,
Maybe you can use libvirt hooks[1] to notify oned via the xmlrpc that the
VMs have shut down?
[1] http://libvirt.org/hooks.html
Andrei
On Fri, Oct 4, 2013 at 6:45 PM, Simon Boulet si...@nostalgeek.com wrote:
Hi,
Here our driver reports the state as returned by Libvirt [1], which
Hi Sharuzzaman,
Thanks for your response. I am aware of the fact that OpenNebula requires human
intervention when shutdown is issued from inside the VM. We can write scripts
to do lot of things, but when in the business of resource provisioning, the
resource provider does not necessarily
Hi,
Here our driver reports the state as returned by Libvirt [1], which
reports VM terminated from the inside (shutdown) as Paused. When the
OpenNebula driver sees a VM as being reported as paused [2], it
switches the VM to SUSPENDED state in OpenNebula. Then you can restart
the VM by issuing the
Hi,
Does OpenNebula EC2 interface support shutting down a VM from with in the VM
itself and have the scheduler recognize that VM has been stopped/shutdown? How
do we enable this feature? At Fermi, we have OpenNebula v3.2 and when the VM is
shutdown it stays in the UNKNOWN state. Can OpenNebula
Hi Parag,
I believe OpenNebula need to have human intervention to really determine
whether to remove or not the VM that it has deployed.
I also think that you can write a script that signal or call OpenNebula
command as soon as the task finish, to shutdown the VM. Or if direct
calling command
12 matches
Mail list logo
