You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Murali Reddy (JIRA)" <ji...@apache.org> on 2013/12/10 01:40:07 UTC

[jira] [Created] (CLOUDSTACK-5428) support NetScaler to be configured exclusively for GSLB service and not used for LB

Murali Reddy created CLOUDSTACK-5428:
----------------------------------------

             Summary: support NetScaler to be configured exclusively for GSLB service and not used for LB
                 Key: CLOUDSTACK-5428
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5428
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
    Affects Versions: 4.2.0
            Reporter: Murali Reddy
            Assignee: Murali Reddy
             Fix For: 4.3.0


Currently a NetScaler configured in the zone, can be used by guest networks for the lb service. there can be use-cases where a operator would like to dedicate a netscaler exclusively for GSLB service. This bug is to support NetScaler to be configured exclusively for GSLB service and not used for LB.

Fix should add a boolean flag to addNetscalerLoadBalancer api, which will mark added NetScaler for exclusive GSLB service. A netscaler marked as exclusive gslb service provider is not picked for any guest network's lb provider.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)