We have removed most of the code... We have to remove cartridge json LB
configuration as well,
"loadBalancer": {
"type": "lb",
"property": {
"name": "no.load.balancer",
"value": "true"
}
}
On Sun, Nov 30, 2014 at 9:11 PM, Isuru Hat
On Sat, Nov 29, 2014 at 8:59 PM, Lahiru Sandaruwan wrote:
> Hi all,
>
> It seems now we can handle LB cartridge as a part of group definition, and
> not as a special cartridge. Therefore we can do $subject.
>
+1.
>
> Wdyt?
>
> Thanks.
>
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, A
Thanks for the replies. I will proceed.
Thanks.
On Sat, Nov 29, 2014 at 10:51 PM, Lakmal Warusawithana
wrote:
>
>
> On Sat, Nov 29, 2014 at 10:43 PM, Reka Thirunavukkarasu
> wrote:
>
>> With the grouping, we can achieve service aware LB by keeping the LB per
>> service group. But, how can we a
+1 A good thought! This would simplify the logic, agree with Lakmal on the
default load balancer scenario.
On Sat, Nov 29, 2014 at 10:51 PM, Lakmal Warusawithana
wrote:
>
>
> On Sat, Nov 29, 2014 at 10:43 PM, Reka Thirunavukkarasu
> wrote:
>
>> With the grouping, we can achieve service aware LB
On Sat, Nov 29, 2014 at 10:43 PM, Reka Thirunavukkarasu
wrote:
> With the grouping, we can achieve service aware LB by keeping the LB per
> service group. But, how can we address the default LB issue, since we keep
> the LB for all the subscription earlier? Can we consider having a LB per
> Appli
With the grouping, we can achieve service aware LB by keeping the LB per
service group. But, how can we address the default LB issue, since we keep
the LB for all the subscription earlier? Can we consider having a LB per
Application is default LB case?
Thanks,
Reka
On Sat, Nov 29, 2014 at 8:59 PM
Hi all,
It seems now we can handle LB cartridge as a part of group definition, and
not as a special cartridge. Therefore we can do $subject.
Wdyt?
Thanks.
--
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.midd
