cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ram Chinta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-5431) permit 'http' as service type for GSLB rule
Date Tue, 17 Dec 2013 09:19:07 GMT

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

Ram Chinta updated CLOUDSTACK-5431:
-----------------------------------

    Priority: Critical  (was: Major)

> permit 'http' as service type for GSLB rule
> -------------------------------------------
>
>                 Key: CLOUDSTACK-5431
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5431
>             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
>            Priority: Critical
>             Fix For: 4.3.0
>
>
> For the load balancer rules, LB rule supports TCP/UDP only from API but, when load balancer
config is configured on the lb provider, implicitly protocol is set as HTTP if port is 80.
GSLB rules accept only TCP & UDP as service type. There will be mismatch when GSLB rule
is configured as service type TCP and LB rules participating in GSLB are configured to be
HTTP.
> On NetScaler in such situation configuring GSLB rule fails with " “Failed to created
service: xxx cloudsite2 due to Service type mismatch with existing service/vserver"
> This bug is to allow 'http' as service type for GSLB rule, so that service types of gslb
rule and lb rule can be matched.



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

Mime
View raw message