[
https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730507#comment-13730507
]
Wido den Hollander commented on CLOUDSTACK-3535:
------------------------------------------------
Fyi, Lennert is my colleague :)
I've been writing some extra code for the HA. It's mainly a PoC for myself, but
I was thinking about running an extra Python webservice on port 8251 on the KVM
Agent which only tells which Instances are still running on the host in case
the Agent doesn't respond.
The Agent can crash due to some unforeseen reason, but the Instances might
still be running just fine.
So I wanted to create a backup where the Investigator can double-check if the
Instance is still alive without doing a ICMP ping.
It's a simple Webservice which gives back some JSON data about what Instances
are running on that host so the Investigator knows that.
> No HA actions are performed when a KVM host goes offline
> --------------------------------------------------------
>
> Key: CLOUDSTACK-3535
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller, KVM, Management Server
> Affects Versions: 4.1.0, 4.1.1, 4.2.0
> Environment: KVM (CentOS 6.3) with CloudStack 4.1
> Reporter: Paul Angus
> Assignee: edison su
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.log.Agent
>
>
> If a KVM host 'goes down', CloudStack does not perform HA for instances which
> are marked as HA enabled on that host (including system VMs)
> CloudStack does not show the host as disconnected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
