[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

venkata swamybabu budumuru closed CLOUDSTACK-2346.
--------------------------------------------------


Tried the following two scenarios with latest Code and they are working as 
expected.

(1) Try to add NetScaler for GSLB with dedicated set to true and it failed with 
the following error.

"NetScaler provisioned to be GSLB service provider can only be configured for 
shared usage."

(2) Try to add More than one NetScaler with dedicated=false (i.e. shared mode) 
and it failed with the following error.

"There is a GSLB service provider configured in the zone alredy."
                
> [GSLB] dedicated vs shared GSLB devices and LB devices
> ------------------------------------------------------
>
>                 Key: CLOUDSTACK-2346
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2346
>             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: http://www.atlassian.com/software/jira

Reply via email to