From issues-return-90443-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org Wed Feb 28 01:14:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id DEB6A180671 for ; Wed, 28 Feb 2018 01:14:04 +0100 (CET) Received: (qmail 41620 invoked by uid 500); 28 Feb 2018 00:14:03 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 41526 invoked by uid 500); 28 Feb 2018 00:14:03 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 41487 invoked by uid 99); 28 Feb 2018 00:14:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Feb 2018 00:14:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 21D65C0160 for ; Wed, 28 Feb 2018 00:14:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id afQhDkliNh3x for ; Wed, 28 Feb 2018 00:14:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 7DFA55FB02 for ; Wed, 28 Feb 2018 00:14:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E4DCDE0296 for ; Wed, 28 Feb 2018 00:14:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 602E024106 for ; Wed, 28 Feb 2018 00:14:00 +0000 (UTC) Date: Wed, 28 Feb 2018 00:14:00 +0000 (UTC) From: "Sean Lair (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-10309) VMs with HA enabled, power back on if shutdown from guest OS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sean Lair created CLOUDSTACK-10309: -------------------------------------- Summary: VMs with HA enabled, power back on if shutdown from g= uest OS Key: CLOUDSTACK-10309 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1030= 9 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the defa= ult.) Components: Management Server Affects Versions: 4.10.0.0, 4.9.0 Environment: KVM Reporter: Sean Lair When a user shuts down their VM from the guest OS (and VM HA is enabled), t= he VM just powers itself back on.=C2=A0 Our environment is on KVM hosts. CloudStack does not know the difference between a VM failing or being shutd= own 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.=C2=A0 It is not intuitive for end-users = to understand why they can't shutdown VMs from within the guest OS.=C2=A0 E= specially when they all come from (non-cloudstack) VMware and Hyper-V envir= onments 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 "h= a.vm.restart.hostup".=C2=A0=C2=A0With this option set to false, if CloudSta= ck sees a VM shutdown out-of-band, +*but the host it was on is still* *onli= n*e+, then it won't power it back on.=C2=A0 The logic is that since the hos= t 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 c= auses CloudStack to power back on the VM. =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)