You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Jessica Tomechak (JIRA)" <ji...@apache.org> on 2013/02/21 07:02:13 UTC

[jira] [Commented] (CLOUDSTACK-443) health monitoring for load balanced instances

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

Jessica Tomechak commented on CLOUDSTACK-443:
---------------------------------------------

Still in code review and the code freeze for 4.1 has passed. Should retarget this to 4.2?
                
> health monitoring for load balanced instances
> ---------------------------------------------
>
>                 Key: CLOUDSTACK-443
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-443
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.1.0
>            Reporter: Murali Reddy
>            Assignee: Rajesh Battala
>             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.
> Release Planning:
> Dev list discussion: http://markmail.org/message/ukw526difssj53nr
> Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Load+Balancer+Health+checks
> Feature Branch: view reviewboard

--
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