cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Murali Reddy (JIRA)" <>
Subject [jira] [Updated] (CLOUDSTACK-653) High Availability: implement GSLB (Global Server Load Balancing) capability for ELB service
Date Thu, 31 Jan 2013 15:05:14 GMT


Murali Reddy updated CLOUDSTACK-653:

        Fix Version/s:     (was: 4.1.0)
    Affects Version/s:     (was: 4.1.0)
> High Availability: implement GSLB (Global Server Load Balancing) capability for ELB service

> --------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-653
>                 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.2.0
>            Reporter: Murali Reddy
>            Assignee: Murali Reddy
>             Fix For: 4.2.0
> Introduce the ability in CloudStack to orchestrate setting up 'global server load balancing'
where in users can setup workloads in one or more zones and configure the load balancing rules
which ensures that traffic gets distributed across the zones. 
> Other critical requirement of this feature would be to ensure that on zone failure, traffic
gets routed only to active zones.
> As with other network services and their capability, there is no assumption on specific
load balancer/ADC. So its implicit that, we need to have generic configuration, API, internal
network element commands etc independent of network element providing GSLB service.
> In the back end, i.e network element that provides ELB service with GSLB capability,
I would like to  enhance NetScaler integration available in CloudStack, as GSLB service provider.
> Release Planning:
> Dev list discussion:
> Functional Spec:
> Feature branch: gslb

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