[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964098#comment-15964098
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9782:
--------------------------------------------

Github user koushik-das commented on the issue:

    https://github.com/apache/cloudstack/pull/1960
  
    @abhinandanprateek Initially I also thought that this is about host HA. But 
after reading the FS I had doubts and asked about the definition of "host HA". 
If you refer to the discussion on dev@, it was mentioned that "host HA" would 
trigger VM HA so that they are started on other hosts. This is the same as 
existing VM HA and I don't think we should refer to it as host HA.
    
    @rhtyd I had replied with some specific questions/comments on the 
discussion thread. I didn't see any responses on those.
    
    Basically I would like to see a clear definition of "host HA". When a host 
is HA'd what all should happen? If the definition provided is nothing but VM HA 
then the question comes why a new framework when the existing framework is 
already there. 


> Host HA
> -------
>
>                 Key: CLOUDSTACK-9782
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9782
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For: Future, 4.11.0.0
>
>
> CloudStack lacks a way to reliably fence a host, the idea of the host-ha 
> feature is to provide a general purpose HA framework and implementation 
> specific for hypervisor that can use additional mechanism such as OOBM (ipmi 
> based power management) to reliably investigate, recover and fencing a host. 
> This feature can handle scenarios associated with server crash issues and 
> reliable fencing of hosts and HA of VM.
> FS: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Host+HA



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to