@citrix.com]
Sent: Tuesday, November 26, 2013 10:51 PM
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] User VM HA using native XS HA capabilities
I haven't tried in XS 6.1 but in 6.2 if a VM is marked as HA enabled (based on
ha-restart-priority) in a HA enabled cluster then if the VM
VM HA using native XS HA capabilities
I haven't tried in XS 6.1 but in 6.2 if a VM is marked as HA enabled (based on
ha-restart-priority) in a HA enabled cluster then if the VM is not stopped
using xapi then it is automatically re-started.
I tried the following on XS 6.2 and it worked as expected
Subject: Re: [PROPOSAL] User VM HA using native XS HA capabilities
I looked at the affinity group FS [1]. Based on what I understand with host
affinity even CS HA won't work if the specific host fails. For cluster/pod
affinity it will work though. Can someone confirm if this is the case
Hi Koushik:
Thanks for the reply - a few followup comments inline. I look forward
to seeing this work.
Other folks: please read the entire thread and the links from Koushik;
there's a planned deprecation here.
--David
On Mon, Nov 25, 2013 at 2:38 AM, Koushik Das koushik@citrix.com wrote:
I haven't tried in XS 6.1 but in 6.2 if a VM is marked as HA enabled (based on
ha-restart-priority) in a HA enabled cluster then if the VM is not stopped
using xapi then it is automatically re-started.
I tried the following on XS 6.2 and it worked as expected:
- Logged on to a guest VM marked
Thanks for the comments David. See inline.
-Koushik
On 22-Nov-2013, at 7:31 PM, David Nalley da...@gnsa.us wrote:
Hi Koushik:
In general I like the idea. A couple of comments:
The upgrade section has a manual step for enabling HA manually per
instance. Why a manual step? Why is
Initial draft of the FS
https://cwiki.apache.org/confluence/display/CLOUDSTACK/User+VM+HA+using+native+XS+HA+capabilities
-Koushik
On 21-Nov-2013, at 9:59 AM, Koushik Das koushik@citrix.com wrote:
Cloudstack relies on custom HA logic for user VMs running on Xenserver. The
reason for
Hi Koushik:
In general I like the idea. A couple of comments:
The upgrade section has a manual step for enabling HA manually per
instance. Why a manual step? Why is CloudStack not checking the
desired state (e.g. if HA is enabled in the instance service group)
with the actual state (what is
Cloudstack relies on custom HA logic for user VMs running on Xenserver. The
reason for doing it like this may be due the fact that native HA capabilities
in XS was not mature enough during the initial days. Also in the custom HA
logic, Cloudstack has to correctly determine the state of a VM
