cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-2346) [GSLB] dedicated vs shared GSLB devices and LB devices
Date Mon, 15 Jul 2013 11:00:48 GMT


ASF subversion and git services commented on CLOUDSTACK-2346:

Commit 186247d6bf0a9532ccacd70ef6952177d42838da in branch refs/heads/4.2 from [~murali.reddy]
[;h=186247d ]

CLOUDSTACK-2346: [GSLB] dedicated vs shared GSLB devices and LB devices

Only one NetScaler device can act as GSLB service provider in a zone for
all the tenants and thier networks, so restrict addign NetScaler device
to be shared use when configure as GSLB service provider.

> [GSLB] dedicated vs shared GSLB devices and LB devices
> ------------------------------------------------------
>                 Key: CLOUDSTACK-2346
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.2.0
>            Reporter: venkata swamybabu budumuru
>            Assignee: Murali Reddy
>             Fix For: 4.2.0
> Steps to reproduce :
> 1. Have CloudStack with GSLB code
> 2. Try to addNetscalerLoadBalancer with lbdevicededicated=true & gslbprovider=true
> 3. Try to add another gslbprovider with either lbdevicededicated=true/false
> Observations:-
> (i) It fails with the following error
> "There is a GSLB service provider configured in the zone alredy."
> (ii) Steps (2) and (3) are creating a conflicting behaviours.
> (iii) Step (2) makes the device to be allocated to per account which means rest of the
accounts a new device for GSLB functionality but, due to the observations (i), we will not
be able to add more than one GSLB.
> we need to either clearly document or change the behaviour in cloudstack.

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