[Openstack] [Openstack-operators] sync power states and externally shut off VMs
mnaser at vexxhost.com
Wed Nov 16 21:32:04 UTC 2016
Typically, you should not be managing your VMs by virsh. After a power outage, I would recommend sending a start API call to instances that are housed on that specific hypervisor
Sent from my iPhone
> On Nov 16, 2016, at 4:26 PM, Gustavo Randich <gustavo.randich at gmail.com> wrote:
> When a VM is shutdown without using nova API (kvm process down, libvirt failed to start instance on host boot, etc.), Openstack "freezes" the shutdown power state in the DB, and then re-applies it if the VM is not started via API, e.g.:
> # virsh shutdown <domain>
> [ sync power states -> stop instance via API ], because hypervisor rules ("power_state is always updated from hypervisor to db")
> # virsh startup <domain>
> [ sync power states -> stop instance via API ], because database rules
> I understand this behaviour is "by design", but I'm confused about the asymmetry: if VM is shutdown without using nova API, should I not be able to start it up again without nova API?
> This is a common scenario in power outages or failures external to Openstack, when VMs fail to start and we need to start them up again using virsh.
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openstack