cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "venkata swamybabu budumuru (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-2285) [GSLB] addNetscalerLoadBalancer with GSLB functionality shouldn't be exposed in basic zone
Date Tue, 30 Apr 2013 03:56:16 GMT
venkata swamybabu budumuru created CLOUDSTACK-2285:
------------------------------------------------------

             Summary: [GSLB] addNetscalerLoadBalancer with GSLB functionality shouldn't be
exposed in basic zone
                 Key: CLOUDSTACK-2285
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2285
             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


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=1.1.1.1&gslbproviderprivateip=1.1.1.1&url=https://10.147.54.5?publicinterface=1/1&privateinterface=1/2&numretries=2&lbdevicededicated=false&

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: 1.1.1.1

(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: http://www.atlassian.com/software/jira

Mime
View raw message