+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 <[email protected]> wrote: > > > On Sat, Nov 29, 2014 at 10:43 PM, Reka Thirunavukkarasu <[email protected]> > 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 >> Application is default LB case? >> >> > +1 for LB define part of dependency in an application. If we want LB for > Full PaaS, we can just deploy LB cartridge to listen all services. I think > we may need to have to pass external LB info into cartridge > > >> Thanks, >> Reka >> >> On Sat, Nov 29, 2014 at 8:59 PM, Lahiru Sandaruwan <[email protected]> >> 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. >>> >>> Wdyt? >>> >>> Thanks. >>> >>> -- >>> -- >>> Lahiru Sandaruwan >>> Committer and PMC member, Apache Stratos, >>> Senior Software Engineer, >>> WSO2 Inc., http://wso2.com >>> lean.enterprise.middleware >>> >>> email: [email protected] blog: http://lahiruwrites.blogspot.com/ >>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >>> >>> >> >> >> -- >> Reka Thirunavukkarasu >> Senior Software Engineer, >> WSO2, Inc.:http://wso2.com, >> Mobile: +94776442007 >> >> >> > > > -- > Lakmal Warusawithana > Vice President, Apache Stratos > Director - Cloud Architecture; WSO2 Inc. > Mobile : +94714289692 > Blog : http://lakmalsview.blogspot.com/ > > -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
