[
https://issues.apache.org/jira/browse/CLOUDSTACK-10309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482288#comment-16482288
]
ASF subversion and git services commented on CLOUDSTACK-10309:
--------------------------------------------------------------
Commit f23278a4381d57ac167835d2ff625dc4d61978fd in cloudstack's branch
refs/heads/master from [~slair1]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=f23278a ]
CLOUDSTACK-10309: Add option on if to VM HA power-on a OOB-shut-off-VM (#2473)
When a user shuts down their VM from the guest OS (and VM HA is enabled), the
VM just powers itself back on. Our environment is on KVM hosts.
CloudStack does not know the difference between a VM failing or being shutdown
from within the guest OS.
This is a major pain point for all our users - especially since they don't pay
for VMs when they are shutoff. It is not intuitive for end-users to understand
why they can't shutdown VMs from within the guest OS. Especially when they all
come from (non-cloudstack) VMware and Hyper-V environments where this is not an
issue.
However, if a host fails, we need VM HA to still work.
This PR that creates a configuration option "ha.vm.restart.hostup". With this
option set to false, if CloudStack sees a VM shutdown out-of-band, but the host
it was on is still online, then it won't power the VM back on. The logic is
that since the host is online, it was most likely shutdown from the guest OS.
For when a host actually fails, standard VM HA logic takes over and powers on
VMs (if they have VM HA enabled) if the host they were on fails.
If that "ha.vm.restart.hostup" option is true (the default to match current
functionality), it works like always, and even in-guest shutdowns of VMs causes
CloudStack to power back on the VM.
> VMs with HA enabled, power back on if shutdown from guest OS
> ------------------------------------------------------------
>
> Key: CLOUDSTACK-10309
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10309
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.9.0, 4.10.0.0
> Environment: KVM
> Reporter: Sean Lair
> Priority: Minor
>
> When a user shuts down their VM from the guest OS (and VM HA is enabled), the
> VM just powers itself back on. Our environment is on KVM hosts.
> CloudStack does not know the difference between a VM failing or being
> shutdown from within the guest OS.
> This is a major pain point for all our users - especially since they don't
> pay for VMs when they are shutoff. It is not intuitive for end-users to
> understand why they can't shutdown VMs from within the guest OS. Especially
> when they all come from (non-cloudstack) VMware and Hyper-V environments
> where this is not an issue.
> However, if a host fails, we need VM HA to still work.
> This Issue is being tied to a new PR that creates a configuration option
> "ha.vm.restart.hostup". With this option set to false, if CloudStack sees a
> VM shutdown out-of-band, +*but the host it was on is still* *onlin*e+, then
> it won't power it back on. The logic is that since the host is online, it
> was most likely shutdown from the guest OS.
> For when a host actually fails, standard VM HA logic takes over and powers on
> VMs (with VM HA enabled) if the host they were on fails.
> If that "ha.vm.restart.hostup" option is true (the default to match current
> functionality), it works like always, and even in-guest shutdowns of VMs
> causes CloudStack to power back on the VM.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
