Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 11 Dec 2013 10:12:09 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12683754.1386642955609.16544.1386756729862@arcas>
In-Reply-To: <JIRA.12683754.1386642955609@arcas>
References: <JIRA.12683754.1386642955609@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-5431) permit 'http' as service type
 for GSLB rule
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-5431?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D13845257#comment-13845257 ]=20

ASF subversion and git services commented on CLOUDSTACK-5431:
-------------------------------------------------------------

Commit 79cb891efc2aeb67a6c928d5723c6c70fb1a1363 in branch refs/heads/4.3 fr=
om [~murali.reddy]
[ https://git-wip-us.apache.org/repos/asf?p=3Dcloudstack.git;h=3D79cb891 ]

CLOUDSTACK-5431: permit 'http' as service type for GSLB rule

Conflicts:
=09api/src/com/cloud/region/ha/GlobalLoadBalancerRule.java
=09api/src/org/apache/cloudstack/api/command/user/region/ha/gslb/CreateGlob=
alLoadBalancerRuleCmd.java


> permit 'http' as service type for GSLB rule
> -------------------------------------------
>
>                 Key: CLOUDSTACK-5431
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-543=
1
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>    Affects Versions: 4.2.0
>            Reporter: Murali Reddy
>            Assignee: Murali Reddy
>             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 prot=
ocol is set as HTTP if port is 80. GSLB rules accept only TCP & UDP as serv=
ice type. There will be mismatch when GSLB rule is configured as service ty=
pe TCP and LB rules participating in GSLB are configured to be HTTP.
> On NetScaler in such situation configuring GSLB rule fails with " =E2=80=
=9CFailed to created service: xxx cloudsite2 due to Service type mismatch w=
ith existing service/vserver"
> This bug is to allow 'http' as service type for GSLB rule, so that servic=
e types of gslb rule and lb rule can be matched.


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