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 shutting down through CS UI/API) and doesn't trigger
HA even if it is enabled in vSphere. This might be different for other
hypervisors since VMSync for vSphere is different.
Best regards,
Kirk
On 07/10/2013 01:03 PM, Chip Childers wrote:
> 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 <jorgen.m...@gmail.com> wrote:
>> 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, <nicolas.lamira...@orange.com> wrote:
>>
>>> Hi,
>>> We are testing CS 4.1.0 with VMWare vSphere 5.0.
>>> If we stop a VM using vCenter, CS doesn't try to restart it. In logs we
>>> see :
>>>
>>> Skip HA for VMware VM i-xxxxxx
>>>
>>> In source code, we can see :
>>>
>>> @Override
>>> public void scheduleRestartForVmsOnHost(final HostVO host, boolean
>>> investigate) {
>>>
>>> [...]
>>>
>>> if(host.getHypervisorType() == HypervisorType.VMware) {
>>> s_logger.info("Don't restart for VMs on host " +
>>> host.getId() + " as the host is VMware host");
>>> return;
>>> }
>>>
>>>
>>> [...]
>>>
>>> }
>>>
>>>
>>> So, CS does not care to restart the VM ?
>>> Regards.
>>>
>>>
>>> --
>>> Nicolas Lamirault
>>>
>>>
>>> _________________________________________________________________________________________________________________________
>>>
>>> Ce message et ses pieces jointes peuvent contenir des informations
>>> confidentielles ou privilegiees et ne doivent donc
>>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
>>> recu ce message par erreur, veuillez le signaler
>>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
>>> electroniques etant susceptibles d'alteration,
>>> Orange decline toute responsabilite si ce message a ete altere, deforme ou
>>> falsifie. Merci.
>>>
>>> This message and its attachments may contain confidential or privileged
>>> information that may be protected by law;
>>> they should not be distributed, used or copied without authorisation.
>>> If you have received this email in error, please notify the sender and
>>> delete this message and its attachments.
>>> As emails may be altered, Orange is not liable for messages that have been
>>> modified, changed or falsified.
>>> Thank you.
>>>
>>>
>>
>>
>> --
>> Grtz,
>> Jörgen Maas
