Hi I've setup Hyper-V compute services and attached it to a controller infrastructure. I can boot images sucessfully and I can start, stop and resize vms. I now shutdown an instance from the console in Hyper-V. However the instance is still marked as active in nova. Am I missing some configuration to make nova get state changes triggered from the hypervisor ?
Instances created by Nova are supposed to be managed (and thus shut down) by Nova. Said that Nova checks e.g. when nova-compute starts if the VM is active and updates the instance status accordingly.
This applies to every Nova diver (libvirt/KVM, ESXI, Hyper-V, etc), so requests to change this behaviour should be brought to the attention of the general OpenStack community (e.g. OpenStack Dev ML, etc)
Thanks for your answer. This makes sense to me. I found out that there is a setting in nova called sync_power_state_interval. If you set this to -1 then nova seems to not sync the power states but leaves the powerstate independent of each other.
Asked: 2014-11-26 12:17:30 +0300
Seen: 597 times
Last updated: Nov 26 '14
© 2014-2023 Cloudbase Solutions Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
Update, I found that the state gets updated in a way that if the instance is marked as shutoff in nova and running in Hyper-V. Nova will initiate a shutdown and the instance is powered off in Hyper-V. Can this behaviour be changed so that it is the other way round Nova will mark instance as running