nal Message-
> >>> From: Kirk Kosinski [mailto:kirkkosin...@gmail.com
> <mailto:kirkkosin...@gmail.com>]
> >>> Sent: Thursday, July 11, 2013 6:30 AM
> >>> To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org>
>
Thanks!
> >
> >
> > On Wed, Jul 10, 2013 at 11:22 PM, Koushik Das >wrote:
> >
> >> That's right. Cloudstack relies on native HA capabilities provided by
> >> vSphere.
> >>
> >>> -----Original Message-
> >>> From: Kirk Kosinski [mailto:k
here.
>>
>>> -Original Message-
>>> From: Kirk Kosinski [mailto:kirkkosin...@gmail.com]
>>> Sent: Thursday, July 11, 2013 6:30 AM
>>> To: users@cloudstack.apache.org
>>> Cc: Chip Childers; d...@cloudstack.apache.org
>>> Subjec
-
> > From: Kirk Kosinski [mailto:kirkkosin...@gmail.com]
> > Sent: Thursday, July 11, 2013 6:30 AM
> > To: users@cloudstack.apache.org
> > Cc: Chip Childers; d...@cloudstack.apache.org
> > Subject: Re: HA for VMWare
> >
> > Hi, unless something changed (I checked 4.0/4
he.org
> Subject: Re: HA for VMWare
>
> Hi, unless something changed (I checked 4.0/4.1 release notes and found
> nothing), CloudStack uses the native vSphere HA (unlike XenServer and
> KVM), so HA must be enabled in a CloudStack-managed vSphere for HA to
> work. Shutting down a
Hi, unless something changed (I checked 4.0/4.1 release notes and found
nothing), CloudStack uses the native vSphere HA (unlike XenServer and
KVM), so HA must be enabled in a CloudStack-managed vSphere for HA to
work. Shutting down a VM through vCenter is probably seen as a valid
shutdown (same as
It "should" work for CS to do the HA (typically with the VMware
cluster *not* having HA enabled).
Nicolas, perhaps open a bug?
On Wed, Jul 10, 2013 at 4:01 PM, Jörgen Maas wrote:
> This should be done by ESX instead of CS, to CS ESX hypervisor is
> externally managed (vCenter)
> I guess you need
This should be done by ESX instead of CS, to CS ESX hypervisor is
externally managed (vCenter)
I guess you need to enable HA in your vmware configuration
On Wed, Jul 10, 2013 at 12:11 PM, wrote:
> Hi,
> We are testing CS 4.1.0 with VMWare vSphere 5.0.
> If we stop a VM using vCenter, CS doesn't
