[
https://issues.apache.org/jira/browse/CLOUDSTACK-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490520#comment-13490520
]
Wido den Hollander commented on CLOUDSTACK-443:
-----------------------------------------------
Won't this go out of the scope of CloudStack?
Isn't health monitoring something that the loadbalancer itself should do?
For HTTP those loadbalancers should just do a health check every X seconds to
all the backends and see if they are alive. Why should CloudStack do this?
If you add this to CloudStack then it will become some monitoring tool that is
collecting data from the instances to see if they are 'alive'.
I don't think this is up to CloudStack, the loadbalancers should handle this
themselves.
> health monitoring for load balanced instances
> ---------------------------------------------
>
> Key: CLOUDSTACK-443
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-443
> Project: CloudStack
> Issue Type: New Feature
> Components: Network Controller
> Affects Versions: 4.1.0
> Reporter: Murali Reddy
> Assignee: Murali Reddy
> Fix For: 4.1.0
>
>
> Enhance existing 'load balancer' network service provided by CloudStack, to
> support health monitor the load balanced instances. ADC's supported
> (NetScaler, Big IP, ADX) by CloudStack have native capabilities to monotor
> health of in the instances. Leverage that to load balance the traffic only to
> healthy instances.
> This feature shall provide capabilities to
> - to configure health check policy with load balancer rule
> - delete configured 'health check policy' associated with a load balancer
> rules
> - list/describe instance healths.
--
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
