incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajesh Battala (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-443) health monitoring for load balanced instances
Date Sun, 27 Jan 2013 03:53:13 GMT


Rajesh Battala commented on CLOUDSTACK-443:

After rebasing master I has having issues creating LB rule on NetScaler device. 

I had resolved the issue am facing while creating the LB rule on Netscaler device.
The issues
1.  _lbProvider list is not having Netscaler element. I had resolved it by adding it in the
2. After resolving the issue, I was facing  when VRElement is trying to apply the LB rule
even though it cannot provide the service, it returning true. 
Fixing this issue had resolved my issues creating LB rule on NetScaler device.

Now testing the healthcheck monitoring API's on the rebased master.
> health monitoring for load balanced instances
> ---------------------------------------------
>                 Key: CLOUDSTACK-443
>                 URL:
>             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:
> Functional Spec:
> 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:

View raw message