cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Murali Reddy (JIRA)" <>
Subject [jira] [Resolved] (CLOUDSTACK-2285) [GSLB] addNetscalerLoadBalancer with GSLB functionality shouldn't be exposed in basic zone
Date Fri, 31 May 2013 13:49:19 GMT


Murali Reddy resolved CLOUDSTACK-2285.

    Resolution: Won't Fix

This problem is not specific to GSLB. But in general its good to have NetScaler not added
when basic zone does not have EIP/ELB service.

But problem, is adding a network service provider instance (in this case NetScaler) into a
physical network is independent action. When an instance of NetScaler is ready to be added,
only zone and physical network needed to be in the deployment. Zone has no (should no have)
info that its EIP/ELB zone. Unless a basic zoe network is created, its no ppossible to check
if zone has EIP and ELB services enabled. 

While this problem can be fixed if we have flag at zone level (with createZone) but its not
much value.

Event if admin adds netscaler, its not used because there are no networks that need it. So
its harmless.

Closing this as wont't fix.
> [GSLB] addNetscalerLoadBalancer with GSLB functionality shouldn't be exposed in basic
> ------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-2285
>                 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
>         Environment: commit 0e2ffe72aa641f4551cae63fbc36454c5934342f
>            Reporter: venkata swamybabu budumuru
>            Assignee: Murali Reddy
>             Fix For: 4.2.0
>         Attachments: api.log.tgz
> Steps to reproduce :
> 1. Have a basic zone setup with at least one XEN cluster using the offering "DefaultSharedNetworkOfferingWithSGService"
> 2. Try "addNetscalerLoadBalancer" with GSLB enabled
> Observations:
> (i) It gets added successfully.
> command=addNetscalerLoadBalancer&physicalnetworkid=4dbe1d3c-1cee-4f88-aeca-45c4a8a76b4d&username=nsroot&password=nsroot&networkdevicetype=NetscalerVPXLoadBalancer&gslbprovider=true&gslbproviderpublicip=
> mysql> select id,name,networktype from data_center where id=1;
> +----+-------+-------------+
> | id | name  | networktype |
> +----+-------+-------------+
> |  1 | zone1 | Basic       |
> +----+-------+-------------+
> mysql> select * from external_load_balancer_devices where id=2\G
> *************************** 1. row ***************************
>                  id: 2
>                uuid: 8c467bfc-7ac3-410a-92d7-11e5853a5d79
> physical_network_id: 200
>       provider_name: Netscaler
>         device_name: NetscalerVPXLoadBalancer
>            capacity: 50
>        device_state: Enabled
>    allocation_state: Free
>        is_dedicated: 0
>          is_managed: 0
>             host_id: 15
>      parent_host_id: 0
>    is_gslb_provider: 1
>  gslb_site_publicip: NULL
> gslb_site_privateip:
> (ii) There is no need for enabling GSLB functionality in basic zones created with above
network offerings because there is no LB feature enabled in this case.
> May be having a check at the API level and allowing it only based on type of zone will
help in this case but, if we are supporting GSLB for ELB enabled zones then we need to handle
that situation as well.

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